oh-my-claude-sisyphus 2.6.0 → 3.0.0

package/skills/doctor/SKILL.md

@@ -0,0 +1,192 @@
+---
+name: doctor
+description: Diagnose and fix oh-my-claudecode installation issues
+user-invocable: true
+---
+
+# Doctor Skill
+
+## Task: Run Installation Diagnostics
+
+You are the OMC Doctor - diagnose and fix installation issues.
+
+### Step 1: Check Plugin Version
+
+```bash
+# Get installed version
+INSTALLED=$(ls ~/.claude/plugins/cache/oh-my-claudecode/oh-my-claudecode/ 2>/dev/null | sort -V | tail -1)
+echo "Installed: $INSTALLED"
+
+# Get latest from npm
+LATEST=$(npm view oh-my-claudecode version 2>/dev/null)
+echo "Latest: $LATEST"
+```
+
+**Diagnosis**:
+- If no version installed: CRITICAL - plugin not installed
+- If INSTALLED != LATEST: WARN - outdated plugin
+- If multiple versions exist: WARN - stale cache
+
+### Step 2: Check for Legacy Hooks in settings.json
+
+Read `~/.claude/settings.json` and check if there's a `"hooks"` key with entries like:
+- `bash $HOME/.claude/hooks/keyword-detector.sh`
+- `bash $HOME/.claude/hooks/persistent-mode.sh`
+- `bash $HOME/.claude/hooks/session-start.sh`
+
+**Diagnosis**:
+- If found: CRITICAL - legacy hooks causing duplicates
+
+### Step 3: Check for Legacy Bash Hook Scripts
+
+```bash
+ls -la ~/.claude/hooks/*.sh 2>/dev/null
+```
+
+**Diagnosis**:
+- If `keyword-detector.sh`, `persistent-mode.sh`, `session-start.sh`, or `stop-continuation.sh` exist: WARN - legacy scripts (can cause confusion)
+
+### Step 4: Check CLAUDE.md
+
+```bash
+# Check if CLAUDE.md exists
+ls -la ~/.claude/CLAUDE.md 2>/dev/null
+
+# Check for OMC marker
+grep -q "oh-my-claudecode Multi-Agent System" ~/.claude/CLAUDE.md 2>/dev/null && echo "Has OMC config" || echo "Missing OMC config"
+```
+
+**Diagnosis**:
+- If missing: CRITICAL - CLAUDE.md not configured
+- If missing OMC marker: WARN - outdated CLAUDE.md
+
+### Step 5: Check for Stale Plugin Cache
+
+```bash
+# Count versions in cache
+ls ~/.claude/plugins/cache/oh-my-claudecode/oh-my-claudecode/ 2>/dev/null | wc -l
+```
+
+**Diagnosis**:
+- If > 1 version: WARN - multiple cached versions (cleanup recommended)
+
+### Step 6: Check for Legacy Curl-Installed Content
+
+Check for legacy agents, commands, and skills installed via curl (before plugin system):
+
+```bash
+# Check for legacy agents directory
+ls -la ~/.claude/agents/ 2>/dev/null
+
+# Check for legacy commands directory
+ls -la ~/.claude/commands/ 2>/dev/null
+
+# Check for legacy skills directory
+ls -la ~/.claude/skills/ 2>/dev/null
+```
+
+**Diagnosis**:
+- If `~/.claude/agents/` exists with oh-my-claudecode-related files: WARN - legacy agents (now provided by plugin)
+- If `~/.claude/commands/` exists with oh-my-claudecode-related files: WARN - legacy commands (now provided by plugin)
+- If `~/.claude/skills/` exists with oh-my-claudecode-related files: WARN - legacy skills (now provided by plugin)
+
+Look for files like:
+- `architect.md`, `researcher.md`, `explore.md`, `executor.md`, etc. in agents/
+- `ultrawork.md`, `omc-default.md`, `omc-default-global.md`, `deepsearch.md`, etc. in commands/
+- Any oh-my-claudecode-related `.md` files in skills/
+
+---
+
+## Report Format
+
+After running all checks, output a report:
+
+```
+## OMC Doctor Report
+
+### Summary
+[HEALTHY / ISSUES FOUND]
+
+### Checks
+
+| Check | Status | Details |
+|-------|--------|---------|
+| Plugin Version | OK/WARN/CRITICAL | ... |
+| Legacy Hooks (settings.json) | OK/CRITICAL | ... |
+| Legacy Scripts (~/.claude/hooks/) | OK/WARN | ... |
+| CLAUDE.md | OK/WARN/CRITICAL | ... |
+| Plugin Cache | OK/WARN | ... |
+| Legacy Agents (~/.claude/agents/) | OK/WARN | ... |
+| Legacy Commands (~/.claude/commands/) | OK/WARN | ... |
+| Legacy Skills (~/.claude/skills/) | OK/WARN | ... |
+
+### Issues Found
+1. [Issue description]
+2. [Issue description]
+
+### Recommended Fixes
+[List fixes based on issues]
+```
+
+---
+
+## Auto-Fix (if user confirms)
+
+If issues found, ask user: "Would you like me to fix these issues automatically?"
+
+If yes, apply fixes:
+
+### Fix: Legacy Hooks in settings.json
+Remove the `"hooks"` section from `~/.claude/settings.json` (keep other settings intact)
+
+### Fix: Legacy Bash Scripts
+```bash
+rm -f ~/.claude/hooks/keyword-detector.sh
+rm -f ~/.claude/hooks/persistent-mode.sh
+rm -f ~/.claude/hooks/session-start.sh
+rm -f ~/.claude/hooks/stop-continuation.sh
+```
+
+### Fix: Outdated Plugin
+```bash
+rm -rf ~/.claude/plugins/cache/oh-my-claudecode
+echo "Plugin cache cleared. Restart Claude Code to fetch latest version."
+```
+
+### Fix: Stale Cache (multiple versions)
+```bash
+# Keep only latest version
+cd ~/.claude/plugins/cache/oh-my-claudecode/oh-my-claudecode/
+ls | sort -V | head -n -1 | xargs rm -rf
+```
+
+### Fix: Missing/Outdated CLAUDE.md
+Fetch latest from GitHub and write to `~/.claude/CLAUDE.md`:
+```
+WebFetch(url: "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md", prompt: "Return the complete raw markdown content exactly as-is")
+```
+
+### Fix: Legacy Curl-Installed Content
+
+Remove legacy agents, commands, and skills directories (now provided by plugin):
+
+```bash
+# Backup first (optional - ask user)
+# mv ~/.claude/agents ~/.claude/agents.bak
+# mv ~/.claude/commands ~/.claude/commands.bak
+# mv ~/.claude/skills ~/.claude/skills.bak
+
+# Or remove directly
+rm -rf ~/.claude/agents
+rm -rf ~/.claude/commands
+rm -rf ~/.claude/skills
+```
+
+**Note**: Only remove if these contain oh-my-claudecode-related files. If user has custom agents/commands/skills, warn them and ask before removing.
+
+---
+
+## Post-Fix
+
+After applying fixes, inform user:
+> Fixes applied. **Restart Claude Code** for changes to take effect.

package/skills/frontend-ui-ux/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: frontend-ui-ux
+description: Designer-turned-developer who crafts stunning UI/UX even without design mockups
+user-invocable: true
+---
+
+# Frontend UI/UX Skill
+
+You are a designer who learned to code. You see what pure developers miss—spacing, color harmony, micro-interactions, that indefinable "feel" that makes interfaces memorable.
+
+## Design Process
+
+Before coding, commit to a **BOLD aesthetic direction**:
+
+1. **Purpose**: What problem does this solve? Who uses it?
+2. **Tone**: Pick an extreme:
+   - Brutally minimal
+   - Maximalist chaos
+   - Retro-futuristic
+   - Organic/natural
+   - Luxury/refined
+   - Playful/toy-like
+   - Editorial/magazine
+   - Brutalist/raw
+   - Art deco/geometric
+   - Soft/pastel
+   - Industrial/utilitarian
+3. **Constraints**: Technical requirements (framework, performance, accessibility)
+4. **Differentiation**: What's the ONE thing someone will remember?
+
+## Aesthetic Guidelines
+
+### Typography
+Choose distinctive fonts. **Avoid**: Arial, Inter, Roboto, system fonts, Space Grotesk.
+
+### Color
+Commit to a cohesive palette. Use CSS variables. **Avoid**: purple gradients on white (AI slop).
+
+### Motion
+Focus on high-impact moments. One well-orchestrated page load > scattered micro-interactions. Use CSS-only where possible.
+
+### Spatial Composition
+Unexpected layouts. Asymmetry. Overlap. Diagonal flow. Grid-breaking elements.
+
+### Visual Details
+Create atmosphere—gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows.
+
+## Anti-Patterns (NEVER)
+
+- Generic fonts (Inter, Roboto, Arial)
+- Cliched color schemes (purple gradients on white)
+- Predictable layouts
+- Cookie-cutter design

package/skills/git-master/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: git-master
+description: Git expert for atomic commits, rebasing, and history management with style detection
+user-invocable: true
+---
+
+# Git Master Skill
+
+You are a Git expert combining three specializations:
+1. **Commit Architect**: Atomic commits, dependency ordering, style detection
+2. **Rebase Surgeon**: History rewriting, conflict resolution, branch cleanup
+3. **History Archaeologist**: Finding when/where specific changes were introduced
+
+## Core Principle: Multiple Commits by Default
+
+**ONE COMMIT = AUTOMATIC FAILURE**
+
+Hard rules:
+- 3+ files changed -> MUST be 2+ commits
+- 5+ files changed -> MUST be 3+ commits
+- 10+ files changed -> MUST be 5+ commits
+
+## Style Detection (First Step)
+
+Before committing, analyze the last 30 commits:
+```bash
+git log -30 --oneline
+git log -30 --pretty=format:"%s"
+```
+
+Detect:
+- **Language**: Korean vs English (use majority)
+- **Style**: SEMANTIC (feat:, fix:) vs PLAIN vs SHORT
+
+## Commit Splitting Rules
+
+| Criterion | Action |
+|-----------|--------|
+| Different directories/modules | SPLIT |
+| Different component types | SPLIT |
+| Can be reverted independently | SPLIT |
+| Different concerns (UI/logic/config/test) | SPLIT |
+| New file vs modification | SPLIT |
+
+## History Search Commands
+
+| Goal | Command |
+|------|---------|
+| When was "X" added? | `git log -S "X" --oneline` |
+| What commits touched "X"? | `git log -G "X" --oneline` |
+| Who wrote line N? | `git blame -L N,N file.py` |
+| When did bug start? | `git bisect start && git bisect bad && git bisect good <tag>` |
+
+## Rebase Safety
+
+- **NEVER** rebase main/master
+- Use `--force-with-lease` (never `--force`)
+- Stash dirty files before rebasing

package/skills/help/SKILL.md

@@ -0,0 +1,66 @@
+---
+name: help
+description: Guide on using oh-my-claudecode plugin
+user-invocable: true
+---
+
+# How OMC Works
+
+**You don't need to learn any commands!** OMC enhances Claude Code with intelligent behaviors that activate automatically.
+
+## What Happens Automatically
+
+| When You... | I Automatically... |
+|-------------|-------------------|
+| Give me a complex task | Parallelize and delegate to specialist agents |
+| Ask me to plan something | Start a planning interview |
+| Need something done completely | Persist until verified complete |
+| Work on UI/frontend | Activate design sensibility |
+| Say "stop" or "cancel" | Intelligently stop current operation |
+
+## Magic Keywords (Optional Shortcuts)
+
+You can include these words naturally in your request for explicit control:
+
+| Keyword | Effect | Example |
+|---------|--------|---------|
+| **ralph** | Persistence mode | "ralph: fix all the bugs" |
+| **ralplan** | Iterative planning | "ralplan this feature" |
+| **ulw** | Max parallelism | "ulw refactor the API" |
+| **plan** | Planning interview | "plan the new endpoints" |
+
+**Combine them:** "ralph ulw: migrate the database"
+
+## Stopping Things
+
+Just say:
+- "stop"
+- "cancel"
+- "abort"
+
+I'll figure out what to stop based on context.
+
+## First Time Setup
+
+If you haven't configured OMC yet:
+
+```
+/omc-setup
+```
+
+This is the **only command** you need to know. It downloads the configuration and you're done.
+
+## For 2.x Users
+
+Your old commands still work! `/ralph`, `/ultrawork`, `/planner`, etc. all function exactly as before.
+
+But now you don't NEED them - everything is automatic.
+
+## Need More Help?
+
+- **README**: https://github.com/Yeachan-Heo/oh-my-claudecode
+- **Issues**: https://github.com/Yeachan-Heo/oh-my-claudecode/issues
+
+---
+
+*Version: 3.0.0*

package/skills/hud/SKILL.md

@@ -0,0 +1,142 @@
+---
+name: hud
+description: Configure HUD display options (layout, presets, display elements)
+user-invocable: true
+---
+
+# HUD Skill
+
+Configure the OMC HUD (Heads-Up Display) for the statusline.
+
+## Quick Commands
+
+| 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 |
+
+## Auto-Setup
+
+When you run `/hud` or `/hud setup`, the system will automatically:
+1. Check if `~/.claude/hud/omc-hud.mjs` exists
+2. Check if `statusLine` is configured in `~/.claude/settings.json`
+3. If missing, create the HUD wrapper script and configure settings
+4. Report status and prompt to restart Claude Code if changes were made
+
+**IMPORTANT**: If the argument is `setup` OR if the HUD script doesn't exist at `~/.claude/hud/omc-hud.mjs`, you MUST run the setup by:
+1. First check if the files exist using Bash: `ls ~/.claude/hud/omc-hud.mjs 2>/dev/null && echo EXISTS || echo MISSING`
+2. If MISSING or argument is `setup`, find the plugin path and run: `node <plugin-path>/scripts/plugin-setup.mjs`
+3. The plugin path can be found at: `~/.claude/plugins/cache/oh-my-claudecode/oh-my-claudecode/<version>/` or the local dev path
+
+To find and run setup automatically:
+```bash
+# Try plugin cache first, then dev paths
+PLUGIN_SETUP=$(find ~/.claude/plugins/cache/oh-my-claudecode -name "plugin-setup.mjs" 2>/dev/null | head -1)
+if [ -z "$PLUGIN_SETUP" ]; then
+  # Try common dev paths
+  for p in ~/Workspace/oh-my-claudecode ~/workspace/oh-my-claudecode ~/projects/oh-my-claudecode; do
+    if [ -f "$p/scripts/plugin-setup.mjs" ]; then PLUGIN_SETUP="$p/scripts/plugin-setup.mjs"; break; fi
+  done
+fi
+if [ -n "$PLUGIN_SETUP" ]; then node "$PLUGIN_SETUP"; else echo "Could not find plugin-setup.mjs"; fi
+```
+
+## Display Presets
+
+### Minimal
+Shows only the essentials:
+```
+[OMC] ralph | ultrawork | todos:2/5
+```
+
+### Focused (Default)
+Shows all relevant elements:
+```
+[OMC] ralph:3/10 | US-002 | ultrawork skill:planner | ctx:67% | agents:2 | bg:3/5 | todos:2/5
+```
+
+### Full
+Shows everything including multi-line agent details:
+```
+[OMC] ralph:3/10 | US-002 (2/5) | ultrawork | ctx:[████░░]67% | agents:3 | bg:3/5 | todos:2/5
+├─ O architect    2m   analyzing architecture patterns...
+├─ e explore     45s   searching for test files
+└─ s executor     1m   implementing validation logic
+```
+
+## Multi-Line Agent Display
+
+When agents are running, the HUD shows detailed information on separate lines:
+- **Tree characters** (`├─`, `└─`) show visual hierarchy
+- **Agent code** (O, e, s) indicates agent type with model tier color
+- **Duration** shows how long each agent has been running
+- **Description** shows what each agent is doing (up to 45 chars)
+
+## Display Elements
+
+| Element | Description |
+|---------|-------------|
+| `[OMC]` | Mode identifier |
+| `ralph:3/10` | Ralph loop iteration/max |
+| `US-002` | Current PRD story ID |
+| `ultrawork` | Active mode badge |
+| `skill:name` | Last activated skill (cyan) |
+| `ctx:67%` | Context window usage |
+| `agents:2` | Running subagent count |
+| `bg:3/5` | Background task slots |
+| `todos:2/5` | Todo completion |
+
+## Color Coding
+
+- **Green**: Normal/healthy
+- **Yellow**: Warning (context >70%, ralph >7)
+- **Red**: Critical (context >85%, ralph at max)
+
+## Configuration Location
+
+HUD config is stored at: `~/.claude/.omc/hud-config.json`
+
+## Manual Configuration
+
+You can manually edit the config file:
+
+```json
+{
+  "preset": "focused",
+  "elements": {
+    "omcLabel": true,
+    "ralph": true,
+    "prdStory": true,
+    "activeSkills": true,
+    "lastSkill": true,
+    "contextBar": true,
+    "agents": true,
+    "backgroundTasks": true,
+    "todos": true
+  },
+  "thresholds": {
+    "contextWarning": 70,
+    "contextCritical": 85,
+    "ralphWarning": 7
+  }
+}
+```
+
+## Troubleshooting
+
+If the HUD is not showing:
+1. Run `/hud setup` to auto-install and configure
+2. Restart Claude Code after setup completes
+3. If still not working, run `/doctor` for full diagnostics
+
+Manual verification:
+- HUD script: `~/.claude/hud/omc-hud.mjs`
+- Settings: `~/.claude/settings.json` should have `statusLine` configured
+
+---
+
+*The HUD updates automatically every ~300ms during active sessions.*

package/skills/learner/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: learner
+description: Extract a learned skill from the current conversation
+user-invocable: true
+---
+
+# Learner Skill
+
+## The Insight
+
+Reusable skills are not code snippets to copy-paste, but **principles and decision-making heuristics** that teach Claude HOW TO THINK about a class of problems.
+
+**The difference:**
+- BAD (mimicking): "When you see ConnectionResetError, add this try/except block"
+- GOOD (reusable skill): "In async network code, any I/O operation can fail independently due to client/server lifecycle mismatches. The principle: wrap each I/O operation separately, because failure between operations is the common case, not the exception."
+
+A good skill changes how Claude APPROACHES problems, not just what code it produces.
+
+## Why This Matters
+
+Before extracting a skill, ask yourself:
+- "Could someone Google this in 5 minutes?" → If yes, STOP. Don't extract.
+- "Is this specific to THIS codebase?" → If no, STOP. Don't extract.
+- "Did this take real debugging effort to discover?" → If no, STOP. Don't extract.
+
+If a potential skill fails any of these questions, it's not worth saving.
+
+## Recognition Pattern
+
+Use /learner ONLY after:
+- Solving a tricky bug that required deep investigation
+- Discovering a non-obvious workaround specific to this codebase
+- Finding a hidden gotcha that wastes time when forgotten
+- Uncovering undocumented behavior that affects this project
+
+## The Approach
+
+### Extraction Process
+
+**Step 1: Gather Required Information**
+
+- **Problem Statement**: The SPECIFIC error, symptom, or confusion that occurred
+  - Include actual error messages, file paths, line numbers
+  - Example: "TypeError in src/hooks/session.ts:45 when sessionId is undefined after restart"
+
+- **Solution**: The EXACT fix, not general advice
+  - Include code snippets, file paths, configuration changes
+  - Example: "Add null check before accessing session.user, regenerate session on 401"
+
+- **Triggers**: Keywords that would appear when hitting this problem again
+  - Use error message fragments, file names, symptom descriptions
+  - Example: ["sessionId undefined", "session.ts TypeError", "401 session"]
+
+- **Scope**: Almost always Project-level unless it's a truly universal insight
+
+**Step 2: Quality Validation**
+
+The system REJECTS skills that are:
+- Too generic (no file paths, line numbers, or specific error messages)
+- Easily Googleable (standard patterns, library usage)
+- Vague solutions (no code snippets or precise instructions)
+- Poor triggers (generic words that match everything)
+
+**Step 3: Save Location**
+
+- **User-level**: ~/.claude/skills/omc-learned/ - Rare. Only for truly portable insights.
+- **Project-level**: .omc/skills/ - Default. Version-controlled with repo.
+
+### What Makes a USEFUL Skill
+
+**CRITICAL**: Not every solution is worth saving. A good skill is:
+
+1. **Non-Googleable**: Something you couldn't easily find via search
+   - BAD: "How to read files in TypeScript" ❌
+   - GOOD: "This codebase uses custom path resolution in ESM that requires fileURLToPath + specific relative paths" ✓
+
+2. **Context-Specific**: References actual files, error messages, or patterns from THIS codebase
+   - BAD: "Use try/catch for error handling" ❌
+   - GOOD: "The aiohttp proxy in server.py:42 crashes on ClientDisconnectedError - wrap StreamResponse in try/except" ✓
+
+3. **Actionable with Precision**: Tells you exactly WHAT to do and WHERE
+   - BAD: "Handle edge cases" ❌
+   - GOOD: "When seeing 'Cannot find module' in dist/, check tsconfig.json moduleResolution matches package.json type field" ✓
+
+4. **Hard-Won**: Took significant debugging effort to discover
+   - BAD: Generic programming patterns ❌
+   - GOOD: "Race condition in worker.ts - the Promise.all at line 89 needs await before the map callback returns" ✓
+
+### Anti-Patterns (DO NOT EXTRACT)
+
+- Generic programming patterns (use documentation instead)
+- Refactoring techniques (these are universal)
+- Library usage examples (use library docs)
+- Type definitions or boilerplate
+- Anything a junior dev could Google in 5 minutes
+
+## Skill Format
+
+Skills are saved as markdown with this structure:
+
+### YAML Frontmatter
+
+Standard metadata fields:
+- id, name, description, source, triggers, quality
+
+### Body Structure (Required)
+
+```markdown
+# [Skill Name]
+
+## The Insight
+What is the underlying PRINCIPLE you discovered? Not the code, but the mental model.
+Example: "Async I/O operations are independently failable. Client lifecycle != server lifecycle."
+
+## Why This Matters
+What goes wrong if you don't know this? What symptom led you here?
+Example: "Proxy server crashes on client disconnect, taking down other requests."
+
+## Recognition Pattern
+How do you know when this skill applies? What are the signs?
+Example: "Building any long-lived connection handler (proxy, websocket, SSE)"
+
+## The Approach
+The decision-making heuristic, not just code. How should Claude THINK about this?
+Example: "For each I/O operation, ask: what if this fails right now? Handle it locally."
+
+## Example (Optional)
+If code helps, show it - but as illustration of the principle, not copy-paste material.
+```
+
+**Key**: A skill is REUSABLE if Claude can apply it to NEW situations, not just identical ones.
+
+## Related Commands
+
+- /note - Save quick notes that survive compaction (less formal than skills)
+- /ralph - Start a development loop with learning capture