oh-my-customcode 0.9.3 → 0.10.0

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

@@ -1,103 +1,34 @@
 # [SHOULD] Interaction Rules
 
-> **Priority**: SHOULD - Strongly recommended
-> **Exception**: Emergency or explicit user request
+> **Priority**: SHOULD | **ID**: R003
 
 ## Response Principles
 
-### 1. Brevity
-```
-✓ Key information first
-✓ Skip unnecessary preamble
-✓ Answer only what's asked
-✗ Over-explanation
-✗ Repetitive confirmation
-```
-
-### 2. Clarity
-```
-✓ Specific expressions
-✓ Unambiguous instructions
-✓ Executable code format
-✗ Abstract descriptions only
-✗ Overuse of "maybe", "probably"
-```
-
-### 3. Transparency
-```
-✓ State actions performed
-✓ Report changes
-✓ Acknowledge uncertainty
-✗ Hide actions
-✗ Present guesses as facts
-```
+| 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 Report Format
+## Status Format
 
-### Start
 ```
 [Start] {task name}
-```
-
-### In Progress
-```
 [Progress] {current step} ({n}/{total})
+[Done] {task name} — Result: {summary}
+[Failed] {task name} — Cause: {reason} — Alternative: {solutions}
 ```
 
-### Complete
-```
-[Done] {task name}
-Result: {summary}
-```
-
-### Failed
-```
-[Failed] {task name}
-Cause: {reason}
-Alternative: {possible solutions}
-```
-
-## Handling Requests
-
-### Clear Request
-→ Execute immediately
-
-### Ambiguous Request
-```
-[Confirm]
-Understood "{request}" as {interpretation}.
-
-Proceed?
-```
-
-### Risky Request
-```
-[Warning]
-This action has {risk factor}.
+## Request Handling
 
-Continue?
-- Yes: {action to perform}
-- No: Cancel
-```
+| 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
 
-### Order
-1. Dependent tasks: Sequential
-2. Independent tasks: Parallel allowed
-
-### Report
-```
-[Task 1/3] Done - {result}
-[Task 2/3] In progress...
-[Task 3/3] Pending
-```
-
-## Long-running Tasks
-
-```
-[In Progress] {task name}
-Elapsed: {time}
-Current: {step}
-Remaining: {work left}
-```
+- 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,132 +1,39 @@
 # [SHOULD] Memory Integration Rules
 
-> **Priority**: SHOULD - Recommended for context persistence
-> **ID**: R011
+> **Priority**: SHOULD | **ID**: R011
 
-## Purpose
+## Architecture
 
-Provide persistent memory for agents using Claude Code's native auto memory system.
+**Primary**: Native auto memory (`memory` field in agent frontmatter). No external dependencies.
+**Supplementary**: claude-mem MCP (optional, for cross-session search and temporal queries).
 
-## Architecture: Native First
-
-```
-Primary: Native Auto Memory (memory field in agent frontmatter)
-  - Agent-specific persistent knowledge
-  - Automatic system prompt injection (MEMORY.md)
-  - No external dependencies
-
-Supplementary: claude-mem MCP (optional)
-  - Session-level temporal observations
-  - Cross-agent semantic search
-  - Only if installed and configured
-
-RULE: If native auto memory can handle the task,
-      DO NOT use claude-mem.
-```
+Rule: If native auto memory can handle it, do NOT use claude-mem.
 
 ## Native Auto Memory
 
-### How It Works
-
-1. Agent frontmatter includes `memory` field:
-   ```yaml
-   memory: project  # or user, local
-   ```
-
-2. System automatically:
-   - Creates memory directory for the agent
-   - Loads first 200 lines of MEMORY.md into system prompt
-   - Enables Read/Write/Edit tools for memory directory
-   - Agent learns and records patterns across conversations
-
-### Memory Scopes
-
-| Scope | Location | Use Case | Git Tracked |
-|-------|----------|----------|-------------|
-| `user` | `~/.codex/agent-memory/<name>/` | Cross-project patterns | No |
-| `project` | `.codex/agent-memory/<name>/` | Project-specific patterns | Yes |
-| `local` | `.codex/agent-memory-local/<name>/` | Local-only knowledge | No |
-
-### Current Agent Memory Map
-
-| Scope | Agents | Count |
-|-------|--------|-------|
-| `project` | lang-*, be-*, fe-*, arch-*, tool-*, qa-*, mgr-creator, mgr-updater, mgr-gitnerd, mgr-sauron, mgr-claude-code-bible, sys-memory-keeper | 28 |
-| `user` | infra-docker-expert, infra-aws-expert, db-supabase-expert | 3 |
-| `local` | mgr-supplier, mgr-sync-checker, sys-naggy | 3 |
-
-### Memory Best Practices
-
-```yaml
-do:
-  - Let agents consult memory before starting work
-  - Update memory after discovering patterns or conventions
-  - Keep MEMORY.md under 200 lines (auto-curate if exceeded)
-  - Use separate topic files for detailed notes
+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
 
-dont:
-  - Store sensitive data (API keys, credentials)
-  - Duplicate information already in AGENTS.md
-  - Use memory for temporary session state
-```
+| Scope | Location | Git Tracked |
+|-------|----------|-------------|
+| `user` | `~/.claude/agent-memory/<name>/` | No |
+| `project` | `.claude/agent-memory/<name>/` | Yes |
+| `local` | `.claude/agent-memory-local/<name>/` | No |
 
-## Claude-mem (Optional Supplement)
+## When to Use claude-mem
 
-claude-mem MCP provides session-level observations and semantic search.
-It is NOT required for basic memory functionality.
-
-### When to Use claude-mem
-
-| Scenario | Use Native Memory | Use claude-mem |
-|----------|------------------|---------------|
+| Scenario | Native | claude-mem |
+|----------|--------|------------|
 | Agent learns project patterns | Yes | |
-| Record debugging insights | Yes | |
-| Search across multiple sessions | | Yes |
-| Temporal queries (date-based) | | Yes |
-| Cross-agent knowledge sharing | | Yes |
-| Basic context persistence | Yes | |
-
-### claude-mem Integration (if installed)
-
-```yaml
-provider: claude-mem
-collection: claude_memories
-project_tag: my-project
-status: optional
-```
-
-## Context Compaction
-
-### Compaction Controls
-
-```yaml
-# Targeted compaction - preserve specific context
-/compact focus on {topic}
-
-# Examples
-/compact focus on agent routing decisions
-/compact focus on authentication implementation
-/compact focus on test failures and fixes
-```
-
-### Best Practices
-
-```
-do:
-  - Use /compact focus when nearing context limits
-  - Focus on the most relevant topic for current work
-  - Let auto-compaction handle routine cleanup
-
-dont:
-  - Manually compact when not near limits
-  - Lose important decision context by unfocused compaction
-```
+| Search across sessions | | Yes |
+| Temporal queries | | Yes |
+| Cross-agent sharing | | Yes |
 
-## Error Handling
+## Best Practices
 
-```yaml
-on_memory_write_failure:
-  - Log error
-  - Continue without blocking main task
-  - Memory is enhancement, not requirement
-```
+- Consult memory before starting work
+- Update after discovering patterns
+- Keep MEMORY.md under 200 lines
+- Do not store sensitive data or duplicate CLAUDE.md content
+- Memory write failures should not block main task

package/templates/.codex/skills/dev-lead-routing/SKILL.md

@@ -4,250 +4,77 @@ description: Routes development tasks to the correct language or framework exper
 user-invocable: false
 ---
 
-# Dev Lead Routing Skill
-
-## Purpose
-
-Routes development tasks to appropriate language and framework expert agents. This skill contains the coordination logic for orchestrating sw-engineer agents across language, frontend, backend, and tooling specializations.
-
-## Engineers Under Management
-
-| Type | Agents | Purpose |
-|------|--------|---------|
-| sw-engineer/language | lang-golang-expert, lang-python-expert, lang-rust-expert, lang-kotlin-expert, lang-typescript-expert, lang-java21-expert | Language expertise |
-| sw-engineer/frontend | fe-vercel-agent, fe-vuejs-agent, fe-svelte-agent | Frontend frameworks |
-| sw-engineer/backend | be-fastapi-expert, be-springboot-expert, be-go-backend-expert, be-nestjs-expert, be-express-expert | Backend frameworks |
-| sw-engineer/tooling | tool-npm-expert, tool-optimizer, tool-bun-expert | Build tools and optimization |
-| sw-engineer/database | db-supabase-expert, db-postgres-expert, db-redis-expert | Database design and optimization |
-| sw-architect | arch-documenter, arch-speckit-agent | Architecture documentation and spec-driven development |
-| infra-engineer | infra-docker-expert, infra-aws-expert | Container and cloud infrastructure |
-
-## Language/Framework Detection
-
-### File Extension Mapping
-
-| Extension | Agent | Language/Framework |
-|-----------|-------|-------------------|
-| `.go` | lang-golang-expert | Go |
-| `.py` | lang-python-expert | Python |
-| `.rs` | lang-rust-expert | Rust |
-| `.kt`, `.kts` | lang-kotlin-expert | Kotlin |
-| `.ts`, `.tsx` | lang-typescript-expert | TypeScript |
-| `.java` | lang-java21-expert | Java |
-| `.js`, `.jsx` (React) | fe-vercel-agent | React/Next.js |
-| `.vue` | fe-vuejs-agent | Vue.js |
-| `.svelte` | fe-svelte-agent | Svelte |
-| `.sql` (PostgreSQL) | db-postgres-expert | PostgreSQL |
-| `.sql` (Supabase) | db-supabase-expert | Supabase PostgreSQL |
-| `Dockerfile`, `*.dockerfile` | infra-docker-expert | Docker |
-| `*.tf`, `*.tfvars` | infra-aws-expert | Terraform/IaC |
-| `*.yaml`, `*.yml` (CloudFormation) | infra-aws-expert | AWS CloudFormation |
-
-### Keyword Mapping
-
-| Keyword | Agent |
-|---------|-------|
-| "go", "golang" | lang-golang-expert |
-| "python", "py" | lang-python-expert |
-| "rust" | lang-rust-expert |
-| "kotlin" | lang-kotlin-expert |
-| "typescript", "ts" | lang-typescript-expert |
-| "java" | lang-java21-expert |
-| "react", "next.js", "vercel" | fe-vercel-agent |
-| "vue" | fe-vuejs-agent |
-| "svelte" | fe-svelte-agent |
-| "fastapi" | be-fastapi-expert |
-| "spring", "springboot" | be-springboot-expert |
-| "nestjs" | be-nestjs-expert |
-| "express" | be-express-expert |
-| "npm" | tool-npm-expert |
-| "optimize", "bundle" | tool-optimizer |
-| "bun" | tool-bun-expert |
-| "postgres", "postgresql", "pg_stat", "psql" | db-postgres-expert |
-| "redis", "cache", "pub/sub", "sorted set" | db-redis-expert |
-| "supabase", "rls", "edge function" | db-supabase-expert |
-| "docker", "dockerfile", "container", "compose" | infra-docker-expert |
-| "aws", "cloudformation", "cdk", "terraform", "vpc", "iam", "s3", "lambda" | infra-aws-expert |
-| "architecture", "adr", "openapi", "swagger", "diagram" | arch-documenter |
-| "spec", "specification", "tdd", "requirements" | arch-speckit-agent |
-
-## Command Routing
-
-```
-Development Request → Detection → Expert Agent
-
-Go code     → lang-golang-expert
-Python code → lang-python-expert
-TypeScript  → lang-typescript-expert
-FastAPI     → be-fastapi-expert
-Multi-lang  → Multiple experts (parallel)
-```
+# Dev Lead Routing
+
+## Engineers
+
+| Type | Agents |
+|------|--------|
+| Language | lang-golang-expert, lang-python-expert, lang-rust-expert, lang-kotlin-expert, lang-typescript-expert, lang-java21-expert |
+| Frontend | fe-vercel-agent, fe-vuejs-agent, fe-svelte-agent |
+| Backend | be-fastapi-expert, be-springboot-expert, be-go-backend-expert, be-nestjs-expert, be-express-expert |
+| Tooling | tool-npm-expert, tool-optimizer, tool-bun-expert |
+| Database | db-supabase-expert, db-postgres-expert, db-redis-expert |
+| Architect | arch-documenter, arch-speckit-agent |
+| Infra | infra-docker-expert, infra-aws-expert |
+
+## File Extension Mapping
+
+| Extension | Agent |
+|-----------|-------|
+| `.go` | lang-golang-expert |
+| `.py` | lang-python-expert |
+| `.rs` | lang-rust-expert |
+| `.kt`, `.kts` | lang-kotlin-expert |
+| `.ts`, `.tsx` | lang-typescript-expert |
+| `.java` | lang-java21-expert |
+| `.js/.jsx` (React) | fe-vercel-agent |
+| `.vue` | fe-vuejs-agent |
+| `.svelte` | fe-svelte-agent |
+| `.sql` (PG) | db-postgres-expert |
+| `.sql` (Supabase) | db-supabase-expert |
+| `Dockerfile`, `*.dockerfile` | infra-docker-expert |
+| `*.tf`, `*.tfvars` | infra-aws-expert |
+| `*.yaml`, `*.yml` (CloudFormation) | infra-aws-expert |
+
+## Keyword Mapping
+
+| Keywords | Agent |
+|----------|-------|
+| go, golang | lang-golang-expert |
+| python, py | lang-python-expert |
+| rust | lang-rust-expert |
+| kotlin | lang-kotlin-expert |
+| typescript, ts | lang-typescript-expert |
+| java | lang-java21-expert |
+| react, next.js, vercel | fe-vercel-agent |
+| vue | fe-vuejs-agent |
+| svelte | fe-svelte-agent |
+| fastapi | be-fastapi-expert |
+| spring, springboot | be-springboot-expert |
+| nestjs | be-nestjs-expert |
+| express | be-express-expert |
+| npm | tool-npm-expert |
+| optimize, bundle | tool-optimizer |
+| bun | tool-bun-expert |
+| postgres, postgresql, psql, pg_stat | db-postgres-expert |
+| redis, cache, pub/sub, sorted set | db-redis-expert |
+| supabase, rls, edge function | db-supabase-expert |
+| docker, dockerfile, container, compose | infra-docker-expert |
+| aws, cloudformation, vpc, iam, s3, lambda, cdk, terraform | infra-aws-expert |
+| architecture, adr, openapi, swagger, diagram | arch-documenter |
+| spec, specification, tdd, requirements | arch-speckit-agent |
+
+## Model Selection
+
+| Task | Model |
+|------|-------|
+| Architecture analysis | opus |
+| Code review/implementation | sonnet |
+| Quick validation/search | haiku |
 
 ## Routing Rules
 
-### 1. Code Review Workflow
-
-```
-1. Receive review request
-2. Identify file types and languages:
-   - Use Glob to find files
-   - Parse file extensions
-   - Detect framework (package.json, go.mod, etc.)
-3. Select appropriate experts
-4. Distribute files to experts (parallel if 2+ languages)
-5. Aggregate review findings
-6. Present unified report
-```
-
-Example:
-```
-User: "Review src/*.go src/*.py src/*.ts"
-
-Detection:
-  - src/*.go → lang-golang-expert
-  - src/*.py → lang-python-expert
-  - src/*.ts → lang-typescript-expert
-
-Route (parallel):
-  Task(lang-golang-expert role → review src/*.go, model: "sonnet")
-  Task(lang-python-expert role → review src/*.py, model: "sonnet")
-  Task(lang-typescript-expert role → review src/*.ts, model: "sonnet")
-
-Aggregate:
-  Go: 2 issues found
-  Python: Clean
-  TypeScript: 5 suggestions
-```
-
-### 2. Feature Implementation Workflow
-
-```
-1. Analyze feature requirements
-2. Identify affected components:
-   - Backend API → backend expert
-   - Frontend UI → frontend expert
-   - Multiple layers → multiple experts
-3. Select required experts
-4. Coordinate implementation (sequential if dependent, parallel if independent)
-5. Ensure consistency across languages
-6. Report completion status
-```
-
-### 3. Multi-Language Projects
-
-For projects with multiple languages:
-
-```
-1. Detect all languages in project
-2. Identify primary language (most files)
-3. Route to appropriate experts:
-   - If task spans multiple languages → parallel experts
-   - If task is language-specific → single expert
-4. Coordinate cross-language consistency
-```
-
-## Sub-agent Model Selection
-
-### Model Mapping by Task Type
-
-| Task Type | Recommended Model | Reason |
-|-----------|-------------------|--------|
-| Architecture analysis | `opus` | Deep reasoning required |
-| Code review | `sonnet` | Balanced quality judgment |
-| Code implementation | `sonnet` | Standard code generation |
-| Refactoring | `sonnet` | Balanced transformation |
-| Quick validation | `haiku` | Fast response |
-| File search | `haiku` | Simple operation |
-
-### Model Mapping by Agent
-
-| Agent Type | Default Model | Alternative |
-|------------|---------------|-------------|
-| Language experts | `sonnet` | `opus` for architecture |
-| Frontend experts | `sonnet` | `haiku` for quick checks |
-| Backend experts | `sonnet` | `opus` for API design |
-| Tooling experts | `haiku` | `sonnet` for complex configs |
-
-### Task Call Examples
-
-```
-# Complex architecture analysis
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Analyze module dependencies and suggest improvements for src/",
-  model: "opus"
-)
-
-# Standard code review
-Task(
-  subagent_type: "general-purpose",
-  prompt: "Review Go code in src/handlers/ following lang-golang-expert guidelines",
-  model: "sonnet"
-)
-
-# Quick file search
-Task(
-  subagent_type: "Explore",
-  prompt: "Find all files importing auth package",
-  model: "haiku"
-)
-```
-
-## Parallel Execution
-
-Following R009:
-- Maximum 4 parallel instances
-- Only worker agents (sw-engineer/*)
-- Independent file/module reviews
-- Coordinate cross-expert consistency
-
-Example:
-```
-User: "Review all backend APIs"
-
-Detection:
-  - src/api/go/ → lang-golang-expert
-  - src/api/python/ → lang-python-expert
-  - src/api/kotlin/ → lang-kotlin-expert
-
-Route (parallel):
-  Task(lang-golang-expert role → review src/api/go/, model: "sonnet")
-  Task(lang-python-expert role → review src/api/python/, model: "sonnet")
-  Task(lang-kotlin-expert role → review src/api/kotlin/, model: "sonnet")
-```
-
-## Display Format
-
-```
-[Analyzing] Detected: Go, Python, TypeScript
-
-[Delegating] lang-golang-expert:sonnet → 5 Go files
-[Delegating] lang-python-expert:sonnet → 3 Python files
-[Delegating] lang-typescript-expert:sonnet → 8 TypeScript files
-
-[Progress] ███████████░ 2/3 experts completed
-
-[Summary]
-  Go: 2 issues found
-  Python: Clean
-  TypeScript: 5 suggestions
-
-Review completed.
-```
-
-## Integration with Other Agents
-
-- Receives requirements from arch-speckit-agent (sw-architect)
-- Reports to qa-lead for quality assurance
-- Coordinates with tooling experts (tool-npm-expert, tool-optimizer) for build/deploy
-
-## Usage
-
-This skill is NOT user-invocable. It should be automatically triggered when the main conversation detects development intent.
+Multi-language: detect all languages, route to parallel experts (max 4). Single-language: route to matching expert. Cross-layer (frontend + backend): multiple experts in parallel.
 
-Detection criteria:
-- User requests code review
-- User mentions language/framework name
-- User provides file paths for review
-- User requests refactoring/implementation
-- User uses dev:* commands
+Not user-invocable. Auto-triggered on development intent.