CLAUDE.md

1<!-- OMC:START -->
2<!-- OMC:VERSION:4.8.2 -->
3 
4# oh-my-claudecode - Intelligent Multi-Agent Orchestration
5 
6You are running with oh-my-claudecode (OMC), a multi-agent orchestration layer for Claude Code.
7Coordinate specialized agents, tools, and skills so work is completed accurately and efficiently.
8 
9<operating_principles>
10- Delegate specialized work to the most appropriate agent.
11- Prefer evidence over assumptions: verify outcomes before final claims.
12- Choose the lightest-weight path that preserves quality.
13- Consult official docs before implementing with SDKs/frameworks/APIs.
14</operating_principles>
15 
16<delegation_rules>
17Delegate for: multi-file changes, refactors, debugging, reviews, planning, research, verification.
18Work directly for: trivial ops, small clarifications, single commands.
19Route code to `executor` (use `model=opus` for complex work). Uncertain SDK usage → `document-specialist` (repo docs first; Context Hub / `chub` when available, graceful web fallback otherwise).
20</delegation_rules>
21 
22<model_routing>
23`haiku` (quick lookups), `sonnet` (standard), `opus` (architecture, deep analysis).
24Direct writes OK for: `~/.claude/**`, `.omc/**`, `.claude/**`, `CLAUDE.md`, `AGENTS.md`.
25</model_routing>
26 
27<agent_catalog>
28Prefix: `oh-my-claudecode:`. See `agents/*.md` for full prompts.
29 
30explore (haiku), analyst (opus), planner (opus), architect (opus), debugger (sonnet), executor (sonnet), verifier (sonnet), tracer (sonnet), security-reviewer (sonnet), code-reviewer (opus), test-engineer (sonnet), designer (sonnet), writer (haiku), qa-tester (sonnet), scientist (sonnet), document-specialist (sonnet), git-master (sonnet), code-simplifier (opus), critic (opus)
31</agent_catalog>
32 
33<tools>
34External AI: `/team N:executor "task"`, `omc team N:codex|gemini "..."`, `omc ask <claude|codex|gemini>`, `/ccg`
35OMC State: `state_read`, `state_write`, `state_clear`, `state_list_active`, `state_get_status`
36Teams: Claude Code implicit agent team via Agent/Task `name`; OMC tmux/CLI workers via `/team` or `omc team`; task tracking via TodoWrite/TaskList/TaskGet/TaskUpdate when available
37Notepad: `notepad_read`, `notepad_write_priority`, `notepad_write_working`, `notepad_write_manual`
38Project Memory: `project_memory_read`, `project_memory_write`, `project_memory_add_note`, `project_memory_add_directive`
39Code Intel: LSP (`lsp_hover`, `lsp_goto_definition`, `lsp_find_references`, `lsp_diagnostics`, etc.), AST (`ast_grep_search`, `ast_grep_replace`), `python_repl`
40</tools>
41 
42<skills>
43Invoke via `/oh-my-claudecode:<name>`. Trigger patterns auto-detect keywords.
44 
45Workflow: `autopilot`, `ralph`, `ultrawork`, `team`, `ccg`, `ultraqa`, `omc-plan`, `ralplan`, `sciomc`, `external-context`, `deepinit`, `deep-interview`, `ai-slop-cleaner`
46Keyword triggers: "autopilot"→autopilot, "ralph"→ralph, "ulw"→ultrawork, "ccg"→ccg, "ralplan"→ralplan, "deep interview"→deep-interview, "deslop"/"anti-slop"/cleanup+slop-smell→ai-slop-cleaner, "deep-analyze"→analysis mode, "tdd"→TDD mode, "deepsearch"→codebase search, "ultrathink"→deep reasoning, "cancelomc"→cancel. Team orchestration is explicit via `/team`.
47Utilities: `ask-codex`, `ask-gemini`, `cancel`, `note`, `learner`, `omc-setup`, `mcp-setup`, `hud`, `omc-doctor`, `omc-help`, `trace`, `release`, `project-session-manager`, `skill`, `writer-memory`, `ralph-init`, `configure-notifications`, `learn-about-omc` (`trace` is the evidence-driven tracing lane)
48</skills>
49 
50<team_pipeline>
51Stages: `team-plan` → `team-prd` → `team-exec` → `team-verify` → `team-fix` (loop).
52Fix loop bounded by max attempts. `team ralph` links both modes.
53</team_pipeline>
54 
55<verification>
56Verify before claiming completion. Size appropriately: small→haiku, standard→sonnet, large/security→opus.
57If verification fails, keep iterating.
58</verification>
59 
60<execution_protocols>
61Broad requests: explore first, then plan. 2+ independent tasks in parallel. `run_in_background` for builds/tests.
62Keep authoring and review as separate passes: writer pass creates or revises content, reviewer/verifier pass evaluates it later in a separate lane.
63Never self-approve in the same active context; use `code-reviewer` or `verifier` for the approval pass.
64Before concluding: zero pending tasks, tests passing, verifier evidence collected.
65</execution_protocols>
66 
67<commit_protocol>
68Use git trailers to preserve decision context in every commit message.
69Format: conventional commit subject line, optional body, then structured trailers.
70 
71Trailers (include when applicable — skip for trivial commits like typos or formatting):
72- `Constraint:` active constraint that shaped this decision
73- `Rejected:` alternative considered | reason for rejection
74- `Directive:` warning or instruction for future modifiers of this code
75- `Confidence:` high | medium | low
76- `Scope-risk:` narrow | moderate | broad
77- `Not-tested:` edge case or scenario not covered by tests
78 
79Example:
80```
81fix(auth): prevent silent session drops during long-running ops
82 
83Auth service returns inconsistent status codes on token expiry,
84so the interceptor catches all 4xx and triggers inline refresh.
85 
86Constraint: Auth service does not support token introspection
87Constraint: Must not add latency to non-expired-token paths
88Rejected: Extend token TTL to 24h | security policy violation
89Rejected: Background refresh on timer | race condition with concurrent requests
90Confidence: high
91Scope-risk: narrow
92Directive: Error handling is intentionally broad (all 4xx) — do not narrow without verifying upstream behavior
93Not-tested: Auth service cold-start latency >500ms
94```
95</commit_protocol>
96 
97<hooks_and_context>
98Hooks inject `<system-reminder>` tags. Key patterns: `hook success: Success` (proceed), `[MAGIC KEYWORD: ...]` (invoke skill), `The boulder never stops` (ralph/ultrawork active).
99Persistence: `<remember>` (7 days), `<remember priority>` (permanent).
100Kill switches: `DISABLE_OMC`, `OMC_SKIP_HOOKS` (comma-separated).
101</hooks_and_context>
102 
103<cancellation>
104`/oh-my-claudecode:cancel` ends execution modes. Cancel when done+verified or blocked. Don't cancel if work incomplete.
105</cancellation>
106 
107<worktree_paths>
108State: `.omc/state/`, `.omc/state/sessions/{sessionId}/`, `.omc/notepad.md`, `.omc/project-memory.json`, `.omc/plans/`, `.omc/research/`, `.omc/logs/`
109</worktree_paths>
110 
111<contribution_rules>
112**PRs must always target `dev`, never `main`.** `main` is release-only and is only ever merged into by the maintainer via the release workflow. If you open a PR and realize it targets `main`, use `gh pr edit --base dev` to fix it before asking for review.
113 
114**Never commit `dist/` or `bridge/`.** These are build artifacts generated by `npm run build`. They are gitignored. If they appear in your diff, run `git restore dist/ bridge/` before committing. Committing them inflates PR size, creates merge conflicts, and obscures the actual changes under review.
115</contribution_rules>
116 
117## Setup
118 
119Say "setup omc" or run `/oh-my-claudecode:omc-setup`.
120 
121<!-- OMC:END -->
122