EJClaw/groups/global/CLAUDE.md

Global Memory

This file is for mutable memory shared across Claude groups.

Use it for durable facts, preferences, and shared context that may change over time.

Do not store platform-wide operating rules here. Those now live in prompts/claude-platform.md.

Stored credentials

Shared credentials live at /home/claude/.config/ejclaw/secrets.json (chmod 600, owner-only). Read with the Read tool when a session in any channel asks to "저장해둔 계정토큰으로 로그인" or otherwise needs a registered token.

Schema: credentials.<host>.{type, host, token, note, added_at}.

Currently stored:

• git.tkrmagid.kr — Gitea personal access token. Use via Authorization: token <value> header, or embed in HTTPS URL as https://<user>:<token>@git.tkrmagid.kr/.... For git clone/push, prefer the URL form or git -c http.extraHeader="Authorization: token <value>" clone .... Do not paste the raw token into chat replies.
• sudo — local sudo password for the claude user on this host. Use via echo "$PW" | sudo -S <cmd> (read the password from credentials.sudo.password with the Read tool, then pipe). Do not paste the raw password into chat replies.

To add or rotate a credential, edit secrets.json and append a new entry under credentials; update this list with the host and intended use.

Room mode policy

All rooms default to tribunal (paired) mode. Owner runs the work, reviewer/arbiter (claude-code) verifies. New rooms registered via bun setup/index.ts --step register are also tribunal by default.

If the user in a channel says any of these — "클로드 사용하지 말자", "paired 모드 끄자", "리뷰어 끄자", "이 방은 single 로 바꿔줘" — switch that channel back to single mode. Use:

bun -e "import { initDatabase, setExplicitRoomMode } from './src/db.js'; initDatabase(); setExplicitRoomMode('<chatJid>', 'single');"

The reverse phrase ("paired 켜자", "리뷰어 다시 켜자") flips it back to 'tribunal'. Acknowledge the change in chat and confirm the new mode.

Git backups

• 2026-05-27 10:53 KST: EJClaw 정상 동작 상태를 git commit 1509108 (backup current stable ejclaw state)로 백업했다. "이번 요청만 리뷰어 사용" 기능 작업은 이 백업 커밋 이후에 시작한 변경이다.

---

CLAUDE.md

Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.

Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.

1. Think Before Coding

Don't assume. Don't hide confusion. Surface tradeoffs.

Before implementing:

• State your assumptions explicitly. If uncertain, ask.
• If multiple interpretations exist, present them - don't pick silently.
• If a simpler approach exists, say so. Push back when warranted.
• If something is unclear, stop. Name what's confusing. Ask.

2. Simplicity First

Minimum code that solves the problem. Nothing speculative.

• No features beyond what was asked.
• No abstractions for single-use code.
• No "flexibility" or "configurability" that wasn't requested.
• No error handling for impossible scenarios.
• If you write 200 lines and it could be 50, rewrite it.

Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.

3. Surgical Changes

Touch only what you must. Clean up only your own mess.

When editing existing code:

• Don't "improve" adjacent code, comments, or formatting.
• Don't refactor things that aren't broken.
• Match existing style, even if you'd do it differently.
• If you notice unrelated dead code, mention it - don't delete it.

When your changes create orphans:

• Remove imports/variables/functions that YOUR changes made unused.
• Don't remove pre-existing dead code unless asked.

The test: Every changed line should trace directly to the user's request.

4. Goal-Driven Execution

Define success criteria. Loop until verified.

Transform tasks into verifiable goals:

• "Add validation" → "Write tests for invalid inputs, then make them pass"
• "Fix the bug" → "Write a test that reproduces it, then make it pass"
• "Refactor X" → "Ensure tests pass before and after"

For multi-step tasks, state a brief plan:

1. [Step] → verify: [check]
2. [Step] → verify: [check]
3. [Step] → verify: [check]

Strong success criteria let you loop independently. Weak criteria ("make it work") require constant clarification.

---

These guidelines are working if: fewer unnecessary changes in diffs, fewer rewrites due to overcomplication, and clarifying questions come before implementation rather than after mistakes.