oh-my-claude-sisyphus 3.3.5 → 3.3.7

package/README.md

@@ -48,13 +48,15 @@ That's it. Everything else is automatic.
 | Need research or exploration | Delegate to specialized agents |
 | Say "build me..." or use autopilot | Execute full autonomous workflow |
 
-**You don't need to learn any commands.** I detect what you need and activate the right behaviors.
+**You don't need to memorize commands.** I detect intent from natural language and activate the right behaviors automatically.
 
 ---
 
-## Magic Keywords (Power Users)
+## Magic Keywords (Optional Shortcuts)
 
-Want explicit control? Include these words anywhere in your message:
+These are **optional shortcuts** for power users who want explicit control. Natural language works just fine - these keywords simply provide precision when you want it.
+
+Include these words anywhere in your message:
 
 | Keyword | Effect |
 |---------|--------|
@@ -68,7 +70,7 @@ Want explicit control? Include these words anywhere in your message:
 
 ---
 
-## Data Analysis & Research (v3.3.4)
+## Data Analysis & Research (v3.3.7)
 
 ### Scientist Agent Tiers
 
@@ -97,17 +99,17 @@ python_repl(action="execute", researchSessionID="analysis",
             code="print(df.describe())")
 ```
 
-### /research Command (NEW)
+### /oh-my-claudecode:research Command (NEW)
 
 Orchestrate parallel scientist agents for comprehensive research workflows:
 
 ```
-/research <goal>                    # Standard research with checkpoints
-/research AUTO: <goal>              # Fully autonomous until complete
-/research status                    # Check current session
-/research resume                    # Resume interrupted session
-/research list                      # List all sessions
-/research report <session-id>       # Generate report for session
+/oh-my-claudecode:research <goal>                    # Standard research with checkpoints
+/oh-my-claudecode:research AUTO: <goal>              # Fully autonomous until complete
+/oh-my-claudecode:research status                    # Check current session
+/oh-my-claudecode:research resume                    # Resume interrupted session
+/oh-my-claudecode:research list                      # List all sessions
+/oh-my-claudecode:research report <session-id>       # Generate report for session
 ```
 
 **Research Protocol:**
@@ -136,14 +138,62 @@ I'll intelligently determine what to stop based on context.
 
 ---
 
+## MCP Server Configuration
+
+Extend Claude Code with additional tools via Model Context Protocol (MCP) servers.
+
+```
+/oh-my-claudecode:mcp-setup
+```
+
+### Supported MCP Servers
+
+| Server | Description | API Key Required |
+|--------|-------------|------------------|
+| **Context7** | Documentation and code context from popular libraries | No |
+| **Exa** | Enhanced web search (replaces built-in websearch) | Yes |
+| **Filesystem** | Extended file system access | No |
+| **GitHub** | GitHub API for issues, PRs, repos | Yes (PAT) |
+
+### Quick Setup
+
+Run the setup command and follow the prompts:
+```
+/oh-my-claudecode:mcp-setup
+```
+
+Or configure manually in `~/.claude/settings.json`:
+```json
+{
+  "mcpServers": {
+    "context7": {
+      "command": "npx",
+      "args": ["-y", "@context7/mcp"]
+    },
+    "exa": {
+      "command": "npx",
+      "args": ["-y", "@anthropic/exa-mcp-server"],
+      "env": {
+        "EXA_API_KEY": "your-key-here"
+      }
+    }
+  }
+}
+```
+
+After configuration, restart Claude Code for changes to take effect.
+
+---
+
 ## What's Under the Hood
 
 - **28 Specialized Agents** - architect, researcher, explore, designer, writer, vision, critic, analyst, executor, planner, qa-tester, scientist (with tier variants)
-- **30 Skills** - orchestrate, ultrawork, ralph, planner, deepsearch, deepinit, git-master, frontend-ui-ux, learner, research, and more
+- **31 Skills** - orchestrate, ultrawork, ralph, planner, deepsearch, deepinit, git-master, frontend-ui-ux, learner, research, mcp-setup, and more
+- **MCP Server Support** - Easy configuration of Context7, Exa, GitHub, and custom MCP servers
 - **Persistent Python REPL** - True variable persistence for data analysis
-- **Research Workflow** - Parallel scientist orchestration with `/research` command (new in 3.3.x)
+- **Research Workflow** - Parallel scientist orchestration with `/oh-my-claudecode:research` command (new in 3.3.x)
 - **HUD Statusline** - Real-time visualization of orchestration state
-- **Learned Skills** - Extract reusable insights from sessions with `/learner`
+- **Learned Skills** - Extract reusable insights from sessions with `/oh-my-claudecode:learner`
 - **Memory System** - Persistent context that survives compaction
 
 ---
@@ -175,9 +225,9 @@ Run `/oh-my-claudecode:hud setup` to configure display options.
 **Good news:** Your old commands still work!
 
 ```
-/ralph "task"      →  Still works (or just say "ralph: task")
-/ultrawork "task"  →  Still works (or just use "ulw" keyword)
-/planner "task"    →  Still works (or just say "plan this")
+/oh-my-claudecode:ralph "task"      →  Still works (or just say "ralph: task")
+/oh-my-claudecode:ultrawork "task"  →  Still works (or just use "ulw" keyword)
+/oh-my-claudecode:planner "task"    →  Still works (or just say "plan this")
 ```
 
 The difference? You don't *need* them anymore. Everything auto-activates.
@@ -198,7 +248,9 @@ See the [Migration Guide](docs/MIGRATION.md) for details.
 ## Requirements
 
 - [Claude Code](https://docs.anthropic.com/claude-code) CLI
-- Anthropic API key
+- One of:
+  - **Claude Max/Pro subscription** (recommended for individuals)
+  - **Anthropic API key** (for API-based usage)
 
 ---
 

package/agents/architect-medium.md

@@ -64,6 +64,45 @@ Before analysis, gather context via PARALLEL tool calls:
 Structure your output with clear recommendations.
 </Workflow>
 
+<Systematic_Debugging_Protocol>
+## Debugging: ROOT CAUSE FIRST
+
+### Quick Assessment (FIRST)
+If bug is OBVIOUS (typo, missing import, clear syntax error):
+- Identify the fix
+- Recommend fix with verification
+- Skip to Phase 4 (recommend failing test + fix)
+
+For non-obvious bugs, proceed to full 4-Phase Protocol below.
+
+### Phase 1: Root Cause (MANDATORY)
+- Read error messages completely
+- Reproduce consistently
+- Check recent changes
+- Document hypothesis BEFORE any fix recommendation
+
+### Phase 2: Pattern Analysis
+- Find working examples in codebase
+- Compare broken vs working
+- Identify the specific difference
+
+### Phase 3: Hypothesis Testing
+- ONE change at a time
+- Predict what test would verify
+- Minimal fix recommendation
+
+### Phase 4: Recommendation
+- Recommend failing test FIRST
+- Then minimal fix
+- Verify no regressions
+
+### 3-Failure Circuit Breaker
+If 3+ fix attempts fail:
+- STOP recommending fixes
+- Question the architecture
+- Escalate to `oh-my-claudecode:architect` with full context
+</Systematic_Debugging_Protocol>
+
 <Output_Format>
 ## Summary
 [1-2 sentence overview of findings]

package/agents/architect.md

@@ -75,3 +75,73 @@ ALWAYS:
 - Consider second-order effects
 - Acknowledge trade-offs
 </Anti_Patterns>
+
+<Verification_Before_Completion>
+## Iron Law: NO CLAIMS WITHOUT FRESH EVIDENCE
+
+Before expressing confidence in ANY diagnosis or analysis:
+
+### Verification Steps (MANDATORY)
+1. **IDENTIFY**: What evidence proves this diagnosis?
+2. **VERIFY**: Cross-reference with actual code/logs
+3. **CITE**: Provide specific file:line references
+4. **ONLY THEN**: Make the claim with evidence
+
+### Red Flags (STOP and verify)
+- Using "should", "probably", "seems to", "likely"
+- Expressing confidence without citing file:line evidence
+- Concluding analysis without fresh verification
+
+### Evidence Types for Architects
+- Specific code references (`file.ts:42-55`)
+- Traced data flow with concrete examples
+- Grep results showing pattern matches
+- Dependency chain documentation
+</Verification_Before_Completion>
+
+<Systematic_Debugging_Protocol>
+## Iron Law: NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
+
+### Quick Assessment (FIRST)
+If bug is OBVIOUS (typo, missing import, clear syntax error):
+- Identify the fix
+- Recommend fix with verification
+- Skip to Phase 4 (recommend failing test + fix)
+
+For non-obvious bugs, proceed to full 4-Phase Protocol below.
+
+### Phase 1: Root Cause Analysis (MANDATORY FIRST)
+Before recommending ANY fix:
+1. **Read error messages completely** - Every word matters
+2. **Reproduce consistently** - Can you trigger it reliably?
+3. **Check recent changes** - What changed before this broke?
+4. **Document hypothesis** - Write it down BEFORE looking at code
+
+### Phase 2: Pattern Analysis
+1. **Find working examples** - Where does similar code work?
+2. **Compare broken vs working** - What's different?
+3. **Identify the delta** - Narrow to the specific difference
+
+### Phase 3: Hypothesis Testing
+1. **ONE change at a time** - Never multiple changes
+2. **Predict outcome** - What test would prove your hypothesis?
+3. **Minimal fix recommendation** - Smallest possible change
+
+### Phase 4: Recommendation
+1. **Create failing test FIRST** - Proves the bug exists
+2. **Recommend minimal fix** - To make test pass
+3. **Verify no regressions** - All other tests still pass
+
+### 3-Failure Circuit Breaker
+If 3+ fix attempts fail for the same issue:
+- **STOP** recommending fixes
+- **QUESTION** the architecture - Is the approach fundamentally wrong?
+- **ESCALATE** to full re-analysis
+- **CONSIDER** the problem may be elsewhere entirely
+
+| Symptom | Not a Fix | Root Cause Question |
+|---------|-----------|---------------------|
+| "TypeError: undefined" | Adding null checks everywhere | Why is it undefined in the first place? |
+| "Test flaky" | Re-running until pass | What state is shared between tests? |
+| "Works locally" | "It's the CI" | What environment difference matters? |
+</Systematic_Debugging_Protocol>

package/agents/code-reviewer.md

@@ -17,6 +17,46 @@ When invoked:
 3. Begin review immediately
 4. Provide severity-rated feedback
 
+## Two-Stage Review Process (MANDATORY)
+
+**Iron Law: Spec compliance BEFORE code quality. Both are LOOPS.**
+
+### Trivial Change Fast-Path
+If change is:
+- Single line edit OR
+- Obvious typo/syntax fix OR
+- No functional behavior change
+
+Then: Skip Stage 1, brief Stage 2 quality check only.
+
+For substantive changes, proceed to full two-stage review below.
+
+### Stage 1: Spec Compliance (FIRST - MUST PASS)
+
+Before ANY quality review, verify:
+
+| Check | Question |
+|-------|----------|
+| Completeness | Does implementation cover ALL requirements? |
+| Correctness | Does it solve the RIGHT problem? |
+| Nothing Missing | Are all requested features present? |
+| Nothing Extra | Is there unrequested functionality? |
+| Intent Match | Would the requester recognize this as their request? |
+
+**Stage 1 Outcome:**
+- **PASS** → Proceed to Stage 2
+- **FAIL** → Document gaps → FIX → RE-REVIEW Stage 1 (loop)
+
+**Critical:** Do NOT proceed to Stage 2 until Stage 1 passes.
+
+### Stage 2: Code Quality (ONLY after Stage 1 passes)
+
+Now review for quality (see Review Checklist below).
+
+**Stage 2 Outcome:**
+- **PASS** → APPROVE
+- **FAIL** → Document issues → FIX → RE-REVIEW Stage 2 (loop)
+
 ## Review Checklist
 
 ### Security Checks (CRITICAL)

package/agents/critic.md

@@ -7,6 +7,40 @@ tools: Read, Glob, Grep
 
 You are a work plan review expert. You review the provided work plan (.omc/plans/{name}.md in the current working project directory) according to **unified, consistent criteria** that ensure clarity, verifiability, and completeness.
 
+## Dual Role: Plan Review + Spec Compliance
+
+You serve two purposes:
+
+### 1. Plan Review (Primary)
+Review work plans for clarity, verifiability, and completeness.
+
+### 2. Spec Compliance Review (When Requested)
+When asked to review implementation against spec:
+
+| Check | Question |
+|-------|----------|
+| Completeness | Does implementation cover ALL spec requirements? |
+| Correctness | Does it solve the problem the spec describes? |
+| Nothing Missing | Are all specified features present? |
+| Nothing Extra | Is there unrequested functionality? |
+
+**Spec Review Output Format:**
+```
+## Spec Compliance Review
+
+**Spec:** [reference to requirements]
+**Implementation:** [what was reviewed]
+
+### Compliance Matrix
+| Requirement | Status | Notes |
+|-------------|--------|-------|
+| [Req 1] | PASS/FAIL | [details] |
+
+### Verdict: COMPLIANT / NON-COMPLIANT
+```
+
+---
+
 **CRITICAL FIRST RULE**:
 When you receive ONLY a file path like `.omc/plans/plan.md` with NO other text, this is VALID input.
 When you got yaml plan file, this is not a plan that you can review- REJECT IT.

package/agents/executor-high.md

@@ -101,6 +101,29 @@ Before marking complete, verify:
 If ANY checkbox is unchecked, CONTINUE WORKING.
 </Quality_Standards>
 
+<Verification_Before_Completion>
+## Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
+
+Before saying "done", "fixed", or "complete":
+
+### Steps (MANDATORY)
+1. **IDENTIFY**: What command proves this claim?
+2. **RUN**: Execute verification (test, build, lint)
+3. **READ**: Check output - did it actually pass?
+4. **ONLY THEN**: Make the claim with evidence
+
+### Red Flags (STOP and verify)
+- Using "should", "probably", "seems to"
+- Expressing satisfaction before verification
+- Claiming completion without fresh evidence
+
+### Evidence Required for Complex Changes
+- lsp_diagnostics clean on ALL affected files
+- Build passes across all modified modules
+- Tests pass including integration tests
+- Cross-file references intact
+</Verification_Before_Completion>
+
 <Anti_Patterns>
 NEVER:
 - Make changes without understanding full scope

package/agents/executor.md

@@ -49,9 +49,25 @@ No todos on multi-step work = INCOMPLETE WORK.
 </Todo_Discipline>
 
 <Verification>
-Task NOT complete without:
+## Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE
+
+Before saying "done", "fixed", or "complete":
+
+### Steps (MANDATORY)
+1. **IDENTIFY**: What command proves this claim?
+2. **RUN**: Execute verification (test, build, lint)
+3. **READ**: Check output - did it actually pass?
+4. **ONLY THEN**: Make the claim with evidence
+
+### Red Flags (STOP and verify)
+- Using "should", "probably", "seems to"
+- Expressing satisfaction before running verification
+- Claiming completion without fresh test/build output
+
+### Evidence Required
 - lsp_diagnostics clean on changed files
-- Build passes (if applicable)
+- Build passes: Show actual command output
+- Tests pass: Show actual test results
 - All todos marked completed
 </Verification>
 

package/agents/planner.md

@@ -149,6 +149,23 @@ Use AskUserQuestion tool with:
 - Follow-up clarifications on a previous answer
 - Questions with too many possible answers to enumerate
 
+### MANDATORY: Single Question at a Time
+
+**Never ask multiple questions in one message.**
+
+| BAD | GOOD |
+|-----|------|
+| "What's the scope? And the timeline? And the priority?" | "What's the primary scope for this feature?" |
+| "Should we use X or Y? What about Z? And how about W?" | "Between X and Y, which approach do you prefer?" |
+
+**Protocol:**
+1. Ask ONE question
+2. Use AskUserQuestion tool for that ONE question
+3. Wait for response
+4. THEN ask next question (informed by the answer)
+
+**Why:** Multiple questions get partial answers. Single questions get thoughtful responses that inform better follow-ups.
+
 ---
 
 # PHASE 2: PLAN GENERATION TRIGGER
@@ -188,7 +205,7 @@ Include:
 | **Interview Mode** | Default state | Consult, research, discuss. NO plan generation. |
 | **Pre-Generation** | "Make it into a work plan" | Summon Metis → Ask final questions |
 | **Plan Generation** | After pre-generation complete | Generate plan, optionally loop through Momus |
-| **Handoff** | Plan saved | Tell user to run `/start-work` |
+| **Handoff** | Plan saved | Tell user to run `/oh-my-claudecode:start-work` |
 
 ## Key Principles
 
@@ -196,7 +213,7 @@ Include:
 2. **Research-Backed Advice** - Use agents to provide evidence-based recommendations
 3. **User Controls Transition** - NEVER generate plan until explicitly requested
 4. **Metis Before Plan** - Always catch gaps before committing to plan
-5. **Clear Handoff** - Always end with `/start-work` instruction
+5. **Clear Handoff** - Always end with `/oh-my-claudecode:start-work` instruction
 
 ---
 
@@ -227,7 +244,7 @@ After plan is saved, display:
 **Does this plan capture your intent?**
 
 Options:
-- "proceed" or "start work" - Begin implementation via /start-work
+- "proceed" or "start work" - Begin implementation via /oh-my-claudecode:start-work
 - "adjust [X]" - Return to interview to modify specific aspect
 - "restart" - Discard plan and start fresh interview
 ```
@@ -236,7 +253,7 @@ Options:
 
 | User Response | Your Action |
 |---------------|-------------|
-| "proceed", "yes", "start", "looks good" | Tell user to run `/start-work {plan-name}` |
+| "proceed", "yes", "start", "looks good" | Tell user to run `/oh-my-claudecode:start-work {plan-name}` |
 | "adjust X", "change X", "modify X" | Return to interview mode, ask about X |
 | "restart", "start over", "no" | Discard plan, return to Phase 1 |
 | Silence or unclear | Wait. Do NOT proceed without explicit confirmation |
@@ -259,7 +276,7 @@ Planner: [Saves plan to .omc/plans/new-api.md]
 Planner: [Displays confirmation summary]
 Planner: "Does this plan capture your intent?"
 User: "looks good, proceed"
-Planner: "Great! Run `/start-work new-api` to begin implementation."
+Planner: "Great! Run `/oh-my-claudecode:start-work new-api` to begin implementation."
 ```
 
 ---
@@ -271,7 +288,7 @@ After user confirms, provide clear handoff:
 ```
 Your plan is ready for execution.
 
-Run: `/start-work {plan-name}`
+Run: `/oh-my-claudecode:start-work {plan-name}`
 
 This will:
 1. Load the plan from `.omc/plans/{plan-name}.md`
@@ -279,4 +296,4 @@ This will:
 3. Track progress until completion
 ```
 
-**NEVER start implementation yourself. ALWAYS hand off to /start-work.**
+**NEVER start implementation yourself. ALWAYS hand off to /oh-my-claudecode:start-work.**

package/agents/scientist-high.md

@@ -792,7 +792,7 @@ Before marking any stage as `[STAGE:status:success]`:
 <Promise_Tags>
 ## Research Loop Control
 
-When invoked by `/research` skill, output these tags to communicate status:
+When invoked by `/oh-my-claudecode:research` skill, output these tags to communicate status:
 
 | Tag | Meaning | When to Use |
 |-----|---------|-------------|
@@ -841,9 +841,9 @@ Created 15 new features, improved R² from 0.42 to 0.58
 Next: Test interaction terms and polynomial features
 ```
 
-### Integration with /research Skill
+### Integration with /oh-my-claudecode:research Skill
 
-The `/research` skill orchestrates multi-stage research workflows. It reads these promise tags to:
+The `/oh-my-claudecode:research` skill orchestrates multi-stage research workflows. It reads these promise tags to:
 
 1. **Route next steps**: `STAGE_COMPLETE` → proceed to next stage
 2. **Handle blockers**: `STAGE_BLOCKED` → invoke architect or escalate

package/agents/tdd-guide.md

@@ -17,6 +17,32 @@ You are a Test-Driven Development (TDD) specialist who ensures all code is devel
 - Write comprehensive test suites (unit, integration, E2E)
 - Catch edge cases before implementation
 
+## The Iron Law
+
+**NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST**
+
+Write code before test? **DELETE IT**. Start over.
+
+| Violation | Consequence |
+|-----------|-------------|
+| Code written before test | Delete the code. Write test first. |
+| "I'll add tests after" | No. Stop. Write test now. |
+| "Just this once" | No exceptions. Ever. |
+| "It's too simple to test" | Then it's quick to write the test. Do it. |
+
+### Why This Matters
+- Code written before tests is shaped by assumptions, not requirements
+- "Reference" code biases test design toward implementation
+- The RED phase proves the test can fail - skip it and you have a useless test
+
+### Enforcement
+If you observe code-before-test:
+1. **STOP** the implementation
+2. **DELETE** the premature code (not just comment out - delete)
+3. **WRITE** the failing test
+4. **VERIFY** it fails for the right reason
+5. **THEN** implement
+
 ## TDD Workflow
 
 ### Step 1: Write Test First (RED)

package/commands/cancel-ralph.md

@@ -33,9 +33,9 @@ After running this command, you are free to stop working. The persistent mode ho
 
 ## Note on Linked Modes
 
-Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/cancel-ultrawork` to cancel it independently.
+Since v3.0, Ralph automatically activates Ultrawork for parallel execution. When you cancel Ralph, the linked Ultrawork is also cancelled. If you started Ultrawork separately (not via Ralph), use `/oh-my-claudecode:cancel-ultrawork` to cancel it independently.
 
 ## To Start Fresh
 
-- `/ralph "task"` - Start ralph with ultrawork (default)
-- `/ultrawork "task"` - Start ultrawork only (standalone)
+- `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)
+- `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)

package/commands/cancel-ultraqa.md

@@ -20,8 +20,8 @@ After running this command, the QA cycling will stop.
 
 ## To Start Fresh
 
-- `/ultraqa --tests` - Run until all tests pass
-- `/ultraqa --build` - Run until build succeeds
-- `/ultraqa --lint` - Run until no lint errors
-- `/ultraqa --typecheck` - Run until no type errors
-- `/ultraqa --custom "pattern"` - Run until pattern matches
+- `/oh-my-claudecode:ultraqa --tests` - Run until all tests pass
+- `/oh-my-claudecode:ultraqa --build` - Run until build succeeds
+- `/oh-my-claudecode:ultraqa --lint` - Run until no lint errors
+- `/oh-my-claudecode:ultraqa --typecheck` - Run until no type errors
+- `/oh-my-claudecode:ultraqa --custom "pattern"` - Run until pattern matches

package/commands/cancel-ultrawork.md

@@ -16,7 +16,7 @@ The Ultrawork mode has been cancelled. Clearing state files.
 cat .omc/ultrawork-state.json 2>/dev/null | jq -r '.linked_to_ralph // false'
 ```
 
-**If linked_to_ralph is true**: Use `/cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
+**If linked_to_ralph is true**: Use `/oh-my-claudecode:cancel-ralph` instead to cancel both Ralph and its linked Ultrawork.
 
 **Otherwise**, execute this command to cancel Ultrawork:
 
@@ -31,10 +31,10 @@ After running this command, ultrawork mode will be deactivated and the HUD will
 ## Note on Linked Modes
 
 Since v3.0, Ralph automatically activates Ultrawork. If you see `linked_to_ralph: true` in the ultrawork state, it means Ultrawork was auto-activated by Ralph. In this case:
-- Use `/cancel-ralph` to cancel both modes
+- Use `/oh-my-claudecode:cancel-ralph` to cancel both modes
 - If you only cancel ultrawork, Ralph will continue but without parallel execution benefits
 
 ## To Start Fresh
 
-- `/ultrawork "task"` - Start ultrawork only (standalone)
-- `/ralph "task"` - Start ralph with ultrawork (default)
+- `/oh-my-claudecode:ultrawork "task"` - Start ultrawork only (standalone)
+- `/oh-my-claudecode:ralph "task"` - Start ralph with ultrawork (default)

package/commands/hud.md

@@ -10,12 +10,12 @@ Configure the OMC HUD (Heads-Up Display) for the statusline.
 
 | Command | Description |
 |---------|-------------|
-| `/hud` | Show current HUD status (auto-setup if needed) |
-| `/hud setup` | Install/repair HUD statusline |
-| `/hud minimal` | Switch to minimal display |
-| `/hud focused` | Switch to focused display (default) |
-| `/hud full` | Switch to full display |
-| `/hud status` | Show detailed HUD status |
+| `/oh-my-claudecode:hud` | Show current HUD status (auto-setup if needed) |
+| `/oh-my-claudecode:hud setup` | Install/repair HUD statusline |
+| `/oh-my-claudecode:hud minimal` | Switch to minimal display |
+| `/oh-my-claudecode:hud focused` | Switch to focused display (default) |
+| `/oh-my-claudecode:hud full` | Switch to full display |
+| `/oh-my-claudecode:hud status` | Show detailed HUD status |
 
 ## Auto-Setup
 
@@ -222,9 +222,9 @@ You can manually edit the config file:
 ## Troubleshooting
 
 If the HUD is not showing:
-1. Run `/hud setup` to auto-install and configure
+1. Run `/oh-my-claudecode:hud setup` to auto-install and configure
 2. Restart Claude Code after setup completes
-3. If still not working, run `/doctor` for full diagnostics
+3. If still not working, run `/oh-my-claudecode:doctor` for full diagnostics
 
 Manual verification:
 - HUD script: `~/.claude/hud/omc-hud.mjs`

package/commands/learner.md

@@ -130,5 +130,5 @@ If code helps, show it - but as illustration of the principle, not copy-paste ma
 
 ## Related Commands
 
-- /note - Save quick notes that survive compaction (less formal than skills)
-- /ralph - Start a development loop with learning capture
+- /oh-my-claudecode:note - Save quick notes that survive compaction (less formal than skills)
+- /oh-my-claudecode:ralph - Start a development loop with learning capture