oh-my-claude-sisyphus 2.6.1 → 3.0.0

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

package/skills/note/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: note
+description: Save notes to notepad.md for compaction resilience
+user-invocable: true
+---
+
+# Note Skill
+
+Save important context to `.omc/notepad.md` that survives conversation compaction.
+
+## Usage
+
+| Command | Action |
+|---------|--------|
+| `/note <content>` | Add to Working Memory with timestamp |
+| `/note --priority <content>` | Add to Priority Context (always loaded) |
+| `/note --manual <content>` | Add to MANUAL section (never pruned) |
+| `/note --show` | Display current notepad contents |
+| `/note --prune` | Remove entries older than 7 days |
+| `/note --clear` | Clear Working Memory (keep Priority + MANUAL) |
+
+## Sections
+
+### Priority Context (500 char limit)
+- **Always** injected on session start
+- Use for critical facts: "Project uses pnpm", "API in src/api/client.ts"
+- Keep it SHORT - this eats into your context budget
+
+### Working Memory
+- Timestamped session notes
+- Auto-pruned after 7 days
+- Good for: debugging breadcrumbs, temporary findings
+
+### MANUAL
+- Never auto-pruned
+- User-controlled permanent notes
+- Good for: team contacts, deployment info
+
+## Examples
+
+```
+/note Found auth bug in UserContext - missing useEffect dependency
+/note --priority Project uses TypeScript strict mode, all files in src/
+/note --manual Contact: api-team@company.com for backend questions
+/note --show
+/note --prune
+```
+
+## Behavior
+
+1. Creates `.omc/notepad.md` if it doesn't exist
+2. Parses the argument to determine section
+3. Appends content with timestamp (for Working Memory)
+4. Warns if Priority Context exceeds 500 chars
+5. Confirms what was saved
+
+## Integration
+
+Notepad content is automatically loaded on session start:
+- Priority Context: ALWAYS loaded
+- Working Memory: Loaded if recent entries exist
+
+This helps survive conversation compaction without losing critical context.

package/skills/omc-default/SKILL.md

@@ -0,0 +1,78 @@
+---
+name: omc-default
+description: Configure OMC in local project (.claude/CLAUDE.md)
+user-invocable: true
+---
+
+# OMC Default (Project-Scoped)
+
+## Task: Configure OMC Default Mode (Project-Scoped)
+
+**CRITICAL**: This skill ALWAYS downloads fresh CLAUDE.md from GitHub to your local project. DO NOT use the Write tool - use bash curl exclusively.
+
+### Step 1: Create Local .claude Directory
+
+Ensure the local project has a .claude directory:
+
+```bash
+# Create .claude directory in current project
+mkdir -p .claude && echo "✅ .claude directory created" || echo "❌ Failed to create .claude directory"
+```
+
+### Step 2: Download Fresh CLAUDE.md (MANDATORY)
+
+Execute this bash command to download fresh CLAUDE.md to local project config:
+
+```bash
+# Download fresh CLAUDE.md to project-local .claude/
+curl -fsSL "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md" -o .claude/CLAUDE.md && \
+echo "✅ CLAUDE.md downloaded successfully to .claude/CLAUDE.md" || \
+echo "❌ Failed to download CLAUDE.md"
+```
+
+**Note**: The downloaded CLAUDE.md includes Context Persistence instructions with `<remember>` tags for surviving conversation compaction.
+
+**MANDATORY**: Always run this command. Do NOT skip. Do NOT use Write tool.
+
+**FALLBACK** if curl fails:
+Tell user to manually download from:
+https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md
+
+### Step 3: Verify Plugin Installation
+
+The oh-my-claudecode plugin provides all hooks automatically via the plugin system. Verify the plugin is enabled:
+
+```bash
+grep -q "oh-my-claudecode" ~/.claude/settings.json && echo "Plugin enabled" || echo "Plugin NOT enabled"
+```
+
+If plugin is not enabled, instruct user:
+> Run: `claude /install-plugin oh-my-claudecode` to enable the plugin.
+
+### Step 4: Confirm Success
+
+After completing all steps, report:
+
+✅ **OMC Project Configuration Complete**
+- CLAUDE.md: Updated with latest configuration from GitHub at ./.claude/CLAUDE.md
+- Scope: **PROJECT** - applies only to this project
+- Hooks: Provided by plugin (no manual installation needed)
+- Agents: 19+ available (base + tiered variants)
+- Model routing: Haiku/Sonnet/Opus based on task complexity
+
+**Note**: This configuration is project-specific and won't affect other projects or global settings.
+
+---
+
+## Keeping Up to Date
+
+After installing oh-my-claudecode updates (via npm or plugin update), run `/omc-default` again in your project to get the latest CLAUDE.md configuration. This ensures you have the newest features and agent configurations.
+
+---
+
+## Global vs Project Configuration
+
+- **`/omc-default`** (this command): Creates `./.claude/CLAUDE.md` in your current project
+- **`/omc-default-global`**: Creates `~/.claude/CLAUDE.md` for all projects
+
+Project-scoped configuration takes precedence over global configuration.

package/skills/omc-default-global/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: omc-default-global
+description: Configure OMC globally in ~/.claude/CLAUDE.md
+user-invocable: true
+---
+
+# OMC Default Global
+
+## Task: Configure OMC Default Mode (Global)
+
+**CRITICAL**: This skill ALWAYS downloads fresh CLAUDE.md from GitHub to your global config. DO NOT use the Write tool - use bash curl exclusively.
+
+### Step 1: Download Fresh CLAUDE.md (MANDATORY)
+
+Execute this bash command to erase and download fresh CLAUDE.md to global config:
+
+```bash
+# Remove existing CLAUDE.md and download fresh from GitHub
+rm -f ~/.claude/CLAUDE.md && \
+curl -fsSL "https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md" -o ~/.claude/CLAUDE.md && \
+echo "✅ CLAUDE.md downloaded successfully to ~/.claude/CLAUDE.md" || \
+echo "❌ Failed to download CLAUDE.md"
+```
+
+**MANDATORY**: Always run this command. Do NOT skip. Do NOT use Write tool.
+
+**FALLBACK** if curl fails:
+Tell user to manually download from:
+https://raw.githubusercontent.com/Yeachan-Heo/oh-my-claudecode/main/docs/CLAUDE.md
+
+### Step 2: Clean Up Legacy Hooks (if present)
+
+Check if old manual hooks exist and remove them to prevent duplicates:
+
+```bash
+# Remove legacy bash hook scripts (now handled by plugin system)
+rm -f ~/.claude/hooks/keyword-detector.sh
+rm -f ~/.claude/hooks/stop-continuation.sh
+rm -f ~/.claude/hooks/persistent-mode.sh
+rm -f ~/.claude/hooks/session-start.sh
+```
+
+Check `~/.claude/settings.json` for manual hook entries. If the "hooks" key exists with UserPromptSubmit, Stop, or SessionStart entries pointing to bash scripts, inform the user:
+
+> **Note**: Found legacy hooks in settings.json. These should be removed since the plugin now provides hooks automatically. Remove the "hooks" section from ~/.claude/settings.json to prevent duplicate hook execution.
+
+### Step 3: Verify Plugin Installation
+
+The oh-my-claudecode plugin provides all hooks automatically via the plugin system. Verify the plugin is enabled:
+
+```bash
+grep -q "oh-my-claudecode" ~/.claude/settings.json && echo "Plugin enabled" || echo "Plugin NOT enabled"
+```
+
+If plugin is not enabled, instruct user:
+> Run: `claude /install-plugin oh-my-claudecode` to enable the plugin.
+
+### Step 4: Confirm Success
+
+After completing all steps, report:
+
+✅ **OMC Global Configuration Complete**
+- CLAUDE.md: Updated with latest configuration from GitHub at ~/.claude/CLAUDE.md
+- Scope: **GLOBAL** - applies to all Claude Code sessions
+- Hooks: Provided by plugin (no manual installation needed)
+- Agents: 19+ available (base + tiered variants)
+- Model routing: Haiku/Sonnet/Opus based on task complexity
+
+**Note**: Hooks are now managed by the plugin system automatically. No manual hook installation required.
+
+---
+
+## Keeping Up to Date
+
+After installing oh-my-claudecode updates (via npm or plugin update), run `/omc-default-global` again to get the latest CLAUDE.md configuration. This ensures you have the newest features and agent configurations.