oh-my-customcode 0.12.1 → 0.12.2

package/templates/.codex/rules/MUST-parallel-execution.md

@@ -1,97 +0,0 @@
-# [MUST] Parallel Execution Rules
-
-> **Priority**: MUST - ENFORCED | **ID**: R009
-
-## Core Rule
-
-**2+ independent tasks MUST execute in parallel.** Sequential execution of parallelizable tasks is a rule violation.
-
-## Detection Criteria
-
-Independent (MUST parallelize):
-- No shared mutable state between tasks
-- No sequential dependencies
-- Each completes independently
-
-Examples: creating multiple agents, reviewing multiple files, batch operations on different resources.
-
-## Self-Check
-
-Before writing/editing multiple files:
-1. Are files independent? → YES: spawn parallel Task agents
-2. Using Write/Edit sequentially for 2+ files? → STOP, parallelize
-3. Specialized agent available? → Use it (not general-purpose)
-
-### Common Violations to Avoid
-
-```
-❌ WRONG: Writing files one by one
-   Write(file1.kt) → Write(file2.kt) → Write(file3.kt) → Write(file4.kt)
-
-✓ CORRECT: Spawn parallel agents
-   Task(agent1 → file1.kt)  ┐
-   Task(agent2 → file2.kt)  ├─ All in single message
-   Task(agent3 → file3.kt)  │
-   Task(agent4 → file4.kt)  ┘
-
-❌ WRONG: Project scaffolding sequentially
-   Write(package.json) → Write(tsconfig.json) → Write(src/index.ts) → ...
-
-✓ CORRECT: Parallel scaffolding
-   Task(agent1 → "Create package.json, tsconfig.json")  ┐
-   Task(agent2 → "Create src/cli.ts, src/index.ts")     ├─ Parallel
-   Task(agent3 → "Create src/analyzer/*.ts")            │
-   Task(agent4 → "Create src/converter/*.ts")           ┘
-
-❌ WRONG: Secretary doing all the work
-   Secretary writes domain/, usecase/, infrastructure/ sequentially
-
-✓ CORRECT: Delegate to specialists
-   Task(lang-kotlin-expert → domain layer)
-   Task(be-springboot-expert → infrastructure layer)
-   Task(lang-kotlin-expert → usecase layer)
-
-❌ WRONG: Single Task delegating to multiple agents
-   Task(dev-lead → "coordinate lang-kotlin-expert and be-springboot-expert")
-
-   This creates a SEQUENTIAL bottleneck inside the Task!
-
-✓ CORRECT: Multiple Tasks in parallel, one per agent
-   Task(lang-kotlin-expert → usecase commands)    ┐
-   Task(lang-kotlin-expert → usecase queries)     ├─ All spawned together
-   Task(be-springboot-expert → persistence)       │
-   Task(be-springboot-expert → security)          ┘
-```
-
-## Execution Rules
-
-| Rule | Detail |
-|------|--------|
-| Max instances | 4 concurrent |
-| Not parallelizable | Orchestrator (must stay singleton) |
-| Instance independence | Isolated context, no shared state |
-| Large tasks (>3 min) | MUST split into parallel sub-tasks |
-
-## Task Tool Requirements
-
-- Use specific `subagent_type` (not "general-purpose" when specialist exists)
-- Use `model` parameter for cost optimization (fast for search, balanced for code, reasoning for reasoning)
-- Each independent unit = separate Task tool call in the SAME message
-
-## Display Format
-
-```
-[Instance 1] Task(mgr-creator):balanced → Create Go agent
-[Instance 2] Task(lang-python-expert):balanced → Review Python code
-[Instance 3] Task(Explore):fast → Search codebase
-```
-
-Must use `Task({subagent_type}):{model}` format. Custom names not allowed.
-
-## Result Aggregation
-
-```
-[Summary] {succeeded}/{total} tasks completed
-  ✓ agent-1: success
-  ✗ agent-2: failed (reason)
-```

package/templates/.codex/rules/MUST-permissions.md

@@ -1,30 +0,0 @@
-# [MUST] Permission Rules
-
-> **Priority**: MUST | **ID**: R002
-
-## Tool Permission Tiers
-
-| Tier | Tools | Policy |
-|------|-------|--------|
-| 1: Always | Read, Glob, Grep | Free use |
-| 2: Default | Write, Edit | State changes explicitly, notify before modifying important files |
-| 3: Approval | Bash, WebFetch, WebSearch | Request user approval on first use |
-| 4: Explicit | Task | Only when user explicitly requests |
-
-## File Access
-
-| Operation | Allowed | Prohibited |
-|-----------|---------|-----------|
-| Read | All source, configs, docs | - |
-| Write | Source code, new files in project | .env, .git/config, paths outside project |
-| Delete | Temp files created by agent | Existing files (without request), entire directories |
-
-## Permission Request Format
-
-```
-[Permission Request]
-Action: {action} | Required: {tool} | Reason: {why} | Risk: Low/Medium/High
-Approve?
-```
-
-On insufficient permission: do not attempt, notify user, suggest alternative.

package/templates/.codex/rules/MUST-safety.md

@@ -1,23 +0,0 @@
-# [MUST] Safety Rules
-
-> **Priority**: MUST | **ID**: R001
-
-## Prohibited Actions
-
-| Category | Prohibited |
-|----------|-----------|
-| Data | Expose API keys/secrets/passwords, collect PII without consent, log auth tokens |
-| File System | Modify system files (/etc, /usr, /bin), delete outside project, modify .env/.git/config without approval |
-| Commands | `rm -rf /` or broad deletes, shutdown/restart, sudo/su, network config changes |
-| External | Access URLs without approval, send user data externally, download/execute unknown scripts |
-
-## Required Before Destructive Operations
-
-Verify target, assess impact scope, check recoverability, get user approval.
-
-## On Violation
-
-1. Stop all operations
-2. Preserve current state
-3. Report: what was detected, why it's risky, what action was taken
-4. Wait for instructions

package/templates/.codex/rules/MUST-sync-verification.md

@@ -1,125 +0,0 @@
-# [MUST] Sync Verification Rules
-
-> **Priority**: MUST - ENFORCED | **ID**: R016
-
-## Core Rule
-
-After modifying agents, skills, or guides: run full verification before committing AND pushing. Never ask to commit/push before `mgr-sauron:watch` passes.
-
-Every `git push` requires: `mgr-sauron:watch` → all pass → `git push`
-
-## Verification Phases
-
-### Phase 1: Manager Verification (5 rounds)
-
-| Round | Actions |
-|-------|---------|
-| 1-2 | mgr-supplier:audit, mgr-sync-checker:check, fix issues |
-| 3-4 | Re-verify + mgr-updater:docs, fix remaining |
-| 5 | Final: all counts match, frontmatter valid, skill refs exist, memory scopes valid, routing patterns updated |
-
-Also run: mgr-claude-code-bible:verify (official spec compliance)
-
-### Phase 2: Deep Review (3 rounds)
-
-| Round | Focus |
-|-------|-------|
-| 1 | Workflow alignment: routing skills have complete agent mappings |
-| 2 | References: no orphans, no circular refs, valid skill/memory refs |
-| 3 | Philosophy: R006 separation, R009 parallel, R010 delegation, R007/R008 identification |
-
-### Phase 3: Fix all discovered issues
-
-### Phase 4: Commit via mgr-gitnerd
-
-### Phase 5: Push via mgr-gitnerd (only after sauron passes)
-
-## Self-Check Before Commit and Push
-
-```
-╔══════════════════════════════════════════════════════════════════╗
-║  BEFORE COMMITTING, ASK YOURSELF:                                ║
-║                                                                   ║
-║  1. Did I complete all 5 rounds of manager verification?         ║
-║  2. Did I complete all 3 rounds of deep review?                  ║
-║  3. Did I fix ALL discovered issues?                             ║
-║  4. Are all counts matching across all sources?                  ║
-║  5. Am I delegating to mgr-gitnerd for the commit?               ║
-║                                                                   ║
-║  If NO to ANY → DO NOT COMMIT                                    ║
-╚══════════════════════════════════════════════════════════════════╝
-
-╔══════════════════════════════════════════════════════════════════╗
-║  BEFORE PUSHING, ASK YOURSELF:                                   ║
-║                                                                   ║
-║  1. Did mgr-sauron:watch complete successfully?                  ║
-║  2. Were ALL issues from sauron verification fixed?              ║
-║  3. Am I delegating to mgr-gitnerd for the push?                 ║
-║                                                                   ║
-║  If NO to ANY → DO NOT PUSH                                      ║
-║                                                                   ║
-║  SAURON VERIFICATION IS MANDATORY FOR ALL PUSHES.                ║
-╚══════════════════════════════════════════════════════════════════╝
-```
-
-## When Required
-
-Any change to: agents, agent frontmatter, skills, guides, routing patterns, rules.
-
-## Quick Verification Commands
-
-```bash
-# Agent count check
-ls .codex/agents/*.md | wc -l
-
-# Skill count check
-find .codex/skills -name "SKILL.md" | wc -l
-
-# Frontmatter validation (check for missing YAML headers)
-for f in .codex/agents/*.md; do head -1 "$f" | grep -q "^---" || echo "MISSING FRONTMATTER: $f"; done
-
-# Check for agents with invalid skill references
-for f in .codex/agents/*.md; do
-  grep "^skills:" -A 10 "$f" | grep "  - " | sed 's/.*- //' | while read skill; do
-    [ -f ".codex/skills/$skill/SKILL.md" ] || echo "INVALID SKILL REF in $f: $skill"
-  done
-done
-
-# Routing skill pattern coverage
-grep -c "agent_patterns:" .codex/skills/secretary-routing/SKILL.md
-grep -c "agent_patterns:" .codex/skills/dev-lead-routing/SKILL.md
-grep -c "agent_patterns:" .codex/skills/qa-lead-routing/SKILL.md
-
-# Memory field validation
-for f in .codex/agents/*.md; do
-  mem=$(grep "^memory:" "$f" | awk '{print $2}')
-  if [ -n "$mem" ] && [ "$mem" != "project" ] && [ "$mem" != "user" ] && [ "$mem" != "local" ]; then
-    echo "INVALID MEMORY SCOPE in $f: $mem"
-  fi
-done
-
-# Hook count check
-ls .codex/hooks/*.json 2>/dev/null | wc -l
-
-# Context count check
-ls .codex/contexts/*.md 2>/dev/null | wc -l
-
-# Guide count check
-find guides -mindepth 1 -maxdepth 1 -type d | wc -l
-
-# Agent name accuracy (compare AGENTS.md table with actual files)
-# Extract agent names from files
-ls .codex/agents/*.md | xargs -I{} basename {} .md | sort > /tmp/actual-agents.txt
-
-# Slash command skill existence
-for cmd in $(grep "^| \`/" AGENTS.md | sed 's/.*`\///' | sed 's/`.*//' | sed 's/ .*//')
-do
-  [ -d ".codex/skills/$cmd" ] || echo "MISSING SKILL: $cmd"
-done
-
-# Routing skill completeness check
-ls -d .codex/skills/*-routing 2>/dev/null | xargs -I{} basename {} | sort
-
-# Verify routing skill names in AGENTS.md
-grep -oP '(secretary|dev-lead|de-lead|qa-lead)-routing' AGENTS.md | sort -u
-```

package/templates/.codex/rules/MUST-tool-identification.md

@@ -1,82 +0,0 @@
-# [MUST] Tool Usage Identification Rules
-
-> **Priority**: MUST - ENFORCED | **ID**: R008
-
-## Core Rule
-
-Every tool call MUST be prefixed with agent and model identification:
-
-```
-[agent-name][model] → Tool: <tool-name>
-[agent-name][model] → Target: <file/path/url>
-```
-
-For parallel calls: list ALL identifications BEFORE the tool calls.
-
-### Common Violations to Avoid
-
-```
-❌ WRONG: Calling tools without identification
-   "먼저 JD 내용을 확인하겠습니다."
-   <tool_call>WebFetch(...)</tool_call>
-
-❌ WRONG: Missing model in identification
-   [secretary] → Tool: WebFetch
-   [secretary] → Fetching: https://example.com/jd.md
-
-✓ CORRECT: Always identify with agent AND model
-   "먼저 JD 내용을 확인하겠습니다."
-   [secretary][reasoning] → Tool: WebFetch
-   [secretary][reasoning] → Fetching: https://example.com/jd.md
-   <tool_call>WebFetch(...)</tool_call>
-
-❌ WRONG: Parallel calls without listing all identifications
-   <tool_call>WebFetch(url1)</tool_call>
-   <tool_call>WebFetch(url2)</tool_call>
-   <tool_call>Bash(cmd)</tool_call>
-
-✓ CORRECT: List all identifications with models, then call
-   [secretary][reasoning] → Tool: WebFetch
-   [secretary][reasoning] → Fetching: url1
-   [secretary][reasoning] → Tool: WebFetch
-   [secretary][reasoning] → Fetching: url2
-   [secretary][reasoning] → Tool: Bash
-   [secretary][reasoning] → Running: cmd
-   <tool_call>WebFetch(url1)</tool_call>
-   <tool_call>WebFetch(url2)</tool_call>
-   <tool_call>Bash(cmd)</tool_call>
-```
-
-## Models
-
-| Model | Use |
-|-------|-----|
-| `reasoning` | Complex reasoning, architecture |
-| `balanced` | General tasks, code generation (default) |
-| `fast` | Fast simple tasks, file search |
-
-## Tool Categories
-
-| Category | Tools | Verb |
-|----------|-------|------|
-| File Read | Read, Glob, Grep | Reading / Searching |
-| File Write | Write, Edit | Writing / Editing |
-| Network | WebFetch | Fetching |
-| Execution | Bash, Task | Running / Spawning |
-
-## Task Tool Format
-
-```
-Task(subagent_type):model → description
-```
-
-`subagent_type` MUST match actual Task tool parameter. Custom names not allowed.
-
-## Example
-
-```
-[mgr-creator][balanced] → Write: .codex/agents/new-agent.md
-[secretary][reasoning] → Spawning:
-  [1] Task(lang-golang-expert):balanced → Go code review
-  [2] Task(lang-python-expert):balanced → Python code review
-```

package/templates/.codex/rules/SHOULD-agent-teams.md

@@ -1,39 +0,0 @@
-# [SHOULD] Agent Teams Rules
-
-> **Priority**: SHOULD | **ID**: R017 | **Condition**: Agent Teams enabled locally
-
-## Detection
-
-Available when `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` or TeamCreate/SendMessage tools present.
-
-## Decision Matrix
-
-| Scenario | Preferred |
-|----------|-----------|
-| Simple independent subtasks | Task Tool |
-| Multi-step with shared state | Agent Teams |
-| Research requiring discussion | Agent Teams |
-| Cost-sensitive batch ops | Task Tool |
-| Complex debugging across modules | Agent Teams |
-| Code review + fix cycle | Agent Teams |
-| Single file operations | Task Tool |
-
-**Self-check before Task tool:** Is Agent Teams available? Does task need 3+ agents, shared state, or inter-agent communication? If yes, use Agent Teams.
-
-## Team Patterns
-
-- **Research**: researcher-1 + researcher-2 + synthesizer
-- **Development**: implementer + reviewer + tester
-- **Debug**: investigator-1 + investigator-2 + fixer
-
-## Lifecycle
-
-TeamCreate → TaskCreate → Task(spawn) → SendMessage(coordinate) → TaskUpdate → shutdown → cleanup
-
-## Fallback
-
-When Agent Teams unavailable: use Task tool with R009/R010 rules. Both approaches produce results; Agent Teams adds coordination richness.
-
-## Cost
-
-Agent Teams uses more tokens (full context per member + message passing). Use Task tool if task < 3 min or no inter-agent communication needed.

package/templates/.codex/rules/SHOULD-ecomode.md

@@ -1,37 +0,0 @@
-# [SHOULD] Ecomode Rules
-
-> **Priority**: SHOULD | **ID**: R013
-
-## Activation
-
-Auto-activates when: 4+ parallel tasks, batch operations, 80%+ context usage, or explicit "ecomode on".
-
-## Behaviors
-
-**Compact Output**: Agents return `status + summary (1-2 sentences) + key_data only`. Skip intermediate steps, verbose explanations, repeated context, full file contents.
-
-**Aggregation Format**:
-```
-[Batch Complete] {n}/{total}
-├── {agent}: ✓/✗/⚠ {summary}
-```
-
-**Compression**: File lists -> count only (unless < 5), error traces -> first/last 3 lines, code -> path:line ref only.
-
-## Config
-
-```yaml
-ecomode:
-  threshold: 4
-  result_format: summary
-  max_result_length: 200
-```
-
-## Example
-
-Normal: Full agent header + step-by-step analysis + detailed results.
-Ecomode: `[lang-golang-expert] ✓ src/main.go reviewed: 1 naming issue (handle_error -> handleError)`
-
-## Override
-
-Disable with: "ecomode off", "verbose mode", or "show full details".

package/templates/.codex/rules/SHOULD-error-handling.md

@@ -1,33 +0,0 @@
-# [SHOULD] Error Handling Rules
-
-> **Priority**: SHOULD | **ID**: R004
-
-## Error Classification
-
-| Level | Symptom | Response |
-|-------|---------|----------|
-| Warning | Task completes but needs attention | Output warning, continue |
-| Error | Current task fails, others possible | Stop task, report cause, suggest alternative |
-| Critical | Cannot proceed at all | Stop all, preserve state, report immediately |
-
-## Error Report Format
-
-```
-[Error] {type} — Location: {file:line} — Cause: {cause} — Impact: {effect}
-Attempted: 1. {try1} -> Failed  2. {try2} -> Failed
-Recommended: {action1}, {action2}
-```
-
-## Recovery
-
-| Type | Strategy |
-|------|----------|
-| Retryable | Retry up to 3x with backoff (1s, 2s, 4s), then report |
-| Non-recoverable | Save state, rollback if possible, detailed report, wait for user |
-
-## Validation
-
-| When | Checks |
-|------|--------|
-| Before action | Target exists, permissions available, dependencies met |
-| After action | Expected = actual, file integrity, no side effects |

package/templates/.codex/rules/SHOULD-hud-statusline.md

@@ -1,32 +0,0 @@
-# [SHOULD] HUD Statusline Rules
-
-> **Priority**: SHOULD | **ID**: R012
-
-## Format
-
-```
-─── [Agent] {name} | [Progress] {n}/{total} | [Parallel] {count} ───
-```
-
-## When to Display
-
-Multi-step tasks, parallel execution, long-running operations. Skip for single brief operations.
-
-## Hook Implementation
-
-Implemented in `.codex/hooks/hooks.json` (PreToolUse → Task matcher):
-
-```
-─── [Spawn] {subagent_type}:{model} | {description} ───
-─── [Resume] {subagent_type}:{model} | {description} ───
-```
-
-## Display with Parallel
-
-```
-─── [Agent] secretary | [Parallel] 4 ───
-  [1] Task(mgr-creator):balanced → Create agent
-  [2] Task(lang-golang-expert):fast → Code review
-```
-
-Integrates with R007 (Agent ID), R008 (Tool ID), R009 (Parallel).

package/templates/.codex/rules/SHOULD-interaction.md

@@ -1,34 +0,0 @@
-# [SHOULD] Interaction Rules
-
-> **Priority**: SHOULD | **ID**: R003
-
-## Response Principles
-
-| Principle | Do | Don't |
-|-----------|-----|-------|
-| Brevity | Key info first, answer only what's asked | Over-explanation, repetitive confirmation |
-| Clarity | Specific expressions, executable code | Abstract descriptions, "maybe"/"probably" |
-| Transparency | State actions, report changes, acknowledge uncertainty | Hide actions, present guesses as facts |
-
-## Status Format
-
-```
-[Start] {task name}
-[Progress] {current step} ({n}/{total})
-[Done] {task name} — Result: {summary}
-[Failed] {task name} — Cause: {reason} — Alternative: {solutions}
-```
-
-## Request Handling
-
-| Type | Action |
-|------|--------|
-| Clear | Execute immediately |
-| Ambiguous | `[Confirm] Understood "{request}" as {interpretation}. Proceed?` |
-| Risky | `[Warning] This action has {risk}. Continue? Yes: {action} / No: Cancel` |
-
-## Multiple Tasks
-
-- Dependent: Sequential
-- Independent: Parallel allowed
-- Report: `[Task 1/3] Done` / `[Task 2/3] In progress...` / `[Task 3/3] Pending`

package/templates/.codex/rules/SHOULD-memory-integration.md

@@ -1,39 +0,0 @@
-# [SHOULD] Memory Integration Rules
-
-> **Priority**: SHOULD | **ID**: R011
-
-## Architecture
-
-**Primary**: Native auto memory (`memory` field in agent frontmatter). No external dependencies.
-**Supplementary**: claude-mem MCP (optional, for cross-session search and temporal queries).
-
-Rule: If native auto memory can handle it, do NOT use claude-mem.
-
-## Native Auto Memory
-
-Agent frontmatter `memory: project|user|local` enables persistent memory:
-- System creates memory directory, loads first 200 lines of MEMORY.md into prompt
-- Read/Write/Edit tools auto-enabled for memory directory
-
-| Scope | Location | Git Tracked |
-|-------|----------|-------------|
-| `user` | `~/.codex/agent-memory/<name>/` | No |
-| `project` | `.codex/agent-memory/<name>/` | Yes |
-| `local` | `.codex/agent-memory-local/<name>/` | No |
-
-## When to Use claude-mem
-
-| Scenario | Native | claude-mem |
-|----------|--------|------------|
-| Agent learns project patterns | Yes | |
-| Search across sessions | | Yes |
-| Temporal queries | | Yes |
-| Cross-agent sharing | | Yes |
-
-## Best Practices
-
-- Consult memory before starting work
-- Update after discovering patterns
-- Keep MEMORY.md under 200 lines
-- Do not store sensitive data or duplicate AGENTS.md content
-- Memory write failures should not block main task