claude-code-arcane 2.9.8 → 2.10.0

package/skills/patch-notes/SKILL.md

@@ -25,7 +25,7 @@ Read: `production/releases/[version]/changelog.md`, `docs/CHANGELOG.md` entry, `
 
 Check for tone/voice guidance in: `.claude/docs/technical-preferences.md`, `docs/PATCH-NOTES-STYLE.md`, `design/community/tone-guide.md`. Default: player-friendly, non-technical, enthusiastic not hyperbolic, focus on player experience.
 
-Check for template at `docs/patch-notes-template.md` or `.claude/docs/templates/patch-notes-template.md`. If found → use as structure instead of built-in styles.
+Use the project's own template at `docs/patch-notes-template.md` if it exists; otherwise `.claude/docs/templates/release-notes.md` (player-facing: headline, what's new, gameplay changes, fixes). Either one replaces the built-in styles.
 
 ## Phase 3: Categorize and Translate
 

package/skills/playtest-report/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion
 
 ## Phase 1: Parse Arguments
 
-Resolve review mode: `--review` arg > `production/review-mode.txt` > default `lean`. See `.claude/docs/director-gates.md`.
+Resolve review mode: `--review` arg > `production/review-mode.txt` > default `lean`.
 
 Modes: `new` → blank template, `analyze [path]` → structured findings from raw notes.
 
@@ -25,7 +25,7 @@ Read raw notes. Cross-reference with design documents. Fill template with struct
 
 | Bucket | Route |
 |--------|-------|
-| Design changes | `/propagate-design-change [path]` for downstream impacts |
+| Design changes | Update the GDD, then `/consistency-check` for downstream impacts |
 | Balance adjustments | `/balance-check [system]` before tuning |
 | Bugs | `/bug-report` to formally track |
 | Polish items | Add to `production/` polish backlog |
@@ -41,5 +41,4 @@ Ask to write to `production/qa/playtests/playtest-[date]-[tester].md`.
 ## Phase 5: Next Steps
 
 - Act on highest-priority finding category first
-- Design changes → `/design-review` on updated GDD
 - Bugs → `/bug-triage` to update priorities

package/skills/playwright-pro/CLAUDE.md

@@ -67,8 +67,8 @@ Leverage Claude Code's built-in capabilities:
 
 - **Large migrations**: Use `/batch` for parallel file-by-file conversion
 - **Post-generation cleanup**: Use `/simplify` after generating a test suite
-- **Debugging sessions**: Use `/debug` alongside `/pw:fix` for trace analysis
-- **Code review**: Use `/review` for general code quality, `/pw:review` for Playwright-specific
+- **Debugging sessions**: Use `/debug` alongside `/playwright-pro fix` for trace analysis
+- **Code review**: Use `/review` for general code quality, `/playwright-pro review` for Playwright-specific
 
 ### Integrations
 

package/skills/playwright-pro/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: playwright-pro
 description: "Production-grade Playwright testing toolkit. Generate tests, fix flaky failures, migrate from Cypress/Selenium, sync with TestRail, run on BrowserStack. 55 templates, 3 agents, smart reporting."
-argument-hint: ""
+argument-hint: "[browserstack|fix|generate|init|migrate|report|review|testrail] [args]"
 category: "testing"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Bash, Write, Edit
@@ -13,21 +13,25 @@ Production-grade Playwright testing toolkit for AI coding agents.
 
 > **Note:** This skill may create or modify files in your project. It will ask before writing.
 
+## Sub-commands
+
+`/playwright-pro` with no argument shows this overview. With a sub-command as its first argument, read `skills/<sub-command>/SKILL.md` from this skill's directory and follow it, passing the remaining arguments. Sub-commands: `browserstack`, `fix`, `generate`, `init`, `migrate`, `report`, `review`, `testrail`.
+
 ## Quick Start Workflow
 
 The recommended sequence for most projects:
 
 ```
-1. /pw:init          -> scaffolds config, CI pipeline, and a first smoke test
-2. /pw:generate      -> generates tests from your spec or URL
-3. /pw:review        -> validates quality and flags anti-patterns      <- always run after generate
-4. /pw:fix <test>    -> diagnoses and repairs any failing/flaky tests  <- run when CI turns red
+1. /playwright-pro init          -> scaffolds config, CI pipeline, and a first smoke test
+2. /playwright-pro generate      -> generates tests from your spec or URL
+3. /playwright-pro review        -> validates quality and flags anti-patterns      <- always run after generate
+4. /playwright-pro fix <test>    -> diagnoses and repairs any failing/flaky tests  <- run when CI turns red
 ```
 
 **Validation checkpoints:**
-- After `/pw:generate` -- always run `/pw:review` before committing
-- After `/pw:fix` -- re-run the full suite locally (`npx playwright test`)
-- After `/pw:migrate` -- run `/pw:coverage` to confirm parity before decommissioning old tests
+- After `/playwright-pro generate` -- always run `/playwright-pro review` before committing
+- After `/playwright-pro fix` -- re-run the full suite locally (`npx playwright test`)
+- After `/playwright-pro migrate` -- run both suites and compare test counts and results before decommissioning old tests
 
 ## Golden Rules
 
@@ -55,7 +59,7 @@ The recommended sequence for most projects:
 
 ## What's Included
 
-- **9 skills** with detailed step-by-step instructions
+- **8 skills** with detailed step-by-step instructions
 - **3 specialized agents**: test-architect, test-debugger, migration-planner
 - **55 test templates**: auth, CRUD, checkout, search, forms, dashboard, settings, onboarding, notifications, API, accessibility
 - **2 MCP servers** (TypeScript): TestRail and BrowserStack integrations

package/skills/playwright-pro/agents/migration-planner.md

@@ -2,7 +2,7 @@
 name: migration-planner
 description: >-
   Analyzes Cypress or Selenium test suites and creates a file-by-file
-  migration plan. Invoked by /pw:migrate before conversion starts.
+  migration plan. Invoked by /playwright-pro migrate before conversion starts.
 allowed-tools:
   - Read
   - Grep
@@ -118,4 +118,4 @@ Flag tests that may need manual intervention:
 
 ### Step 7: Return Plan
 
-Return the complete migration plan to `/pw:migrate` for execution.
+Return the complete migration plan to `/playwright-pro migrate` for execution.

package/skills/playwright-pro/agents/test-architect.md

@@ -1,8 +1,7 @@
 ---
 name: test-architect
 description: >-
-  Plans test strategy for complex applications. Invoked by /pw:generate and
-  /pw:coverage when the app has multiple routes, complex state, or requires
+  Plans test strategy for complex applications. Invoked by /playwright-pro generate when the app has multiple routes, complex state, or requires
   a structured test plan before writing tests.
 allowed-tools:
   - Read

package/skills/playwright-pro/agents/test-debugger.md

@@ -2,7 +2,7 @@
 name: test-debugger
 description: >-
   Diagnoses flaky or failing Playwright tests using systematic taxonomy.
-  Invoked by /pw:fix when a test needs deep analysis including running
+  Invoked by /playwright-pro fix when a test needs deep analysis including running
   tests, reading traces, and identifying root causes.
 allowed-tools:
   - Read

package/skills/playwright-pro/hooks/detect-playwright.sh

@@ -20,4 +20,4 @@ fi
 # Count existing test files
 TEST_COUNT=$(find . -name "*.spec.ts" -o -name "*.spec.js" -o -name "*.test.ts" -o -name "*.test.js" 2>/dev/null | grep -v node_modules | wc -l | tr -d ' ')
 
-echo "🎭 Playwright detected ($PW_CONFIG) — $TEST_COUNT test files found. Use /pw: commands for testing workflows."
+echo "🎭 Playwright detected ($PW_CONFIG) — $TEST_COUNT test files found. Use /playwright-pro for testing workflows."

package/skills/playwright-pro/skills/browserstack/SKILL.md

@@ -24,7 +24,7 @@ If not set, inform the user how to get them from [browserstack.com/accounts/sett
 ### 1. Configure for BrowserStack
 
 ```
-/pw:browserstack setup
+/playwright-pro browserstack setup
 ```
 
 Steps:
@@ -96,7 +96,7 @@ export default defineConfig({
 ### 2. Run Tests on BrowserStack
 
 ```
-/pw:browserstack run
+/playwright-pro browserstack run
 ```
 
 Steps:
@@ -113,7 +113,7 @@ Steps:
 ### 3. Get Build Results
 
 ```
-/pw:browserstack results
+/playwright-pro browserstack results
 ```
 
 Steps:
@@ -130,7 +130,7 @@ Steps:
 ### 4. Check Available Browsers
 
 ```
-/pw:browserstack browsers
+/playwright-pro browserstack browsers
 ```
 
 Steps:
@@ -141,7 +141,7 @@ Steps:
 ### 5. Local Testing
 
 ```
-/pw:browserstack local
+/playwright-pro browserstack local
 ```
 
 For testing localhost or staging behind firewall:

package/skills/playwright-pro/skills/migrate/SKILL.md

@@ -48,7 +48,7 @@ Migration Assessment:
 
 ### 3. Set Up Playwright (If Not Present)
 
-Run `/pw:init` first if Playwright isn't configured.
+Run `/playwright-pro init` first if Playwright isn't configured.
 
 ### 4. Convert Files
 

package/skills/playwright-pro/skills/report/SKILL.md

@@ -46,7 +46,7 @@ Check what's configured and route automatically:
 
 | Check | If found | Action |
 |---|---|---|
-| `TESTRAIL_URL` env var | TestRail configured | Push results via `/pw:testrail push` |
+| `TESTRAIL_URL` env var | TestRail configured | Push results via `/playwright-pro testrail push` |
 | `SLACK_WEBHOOK_URL` env var | Slack configured | Post summary to Slack |
 | `.github/workflows/` | GitHub Actions | Results go to PR comment via artifacts |
 | `playwright-report/` | HTML reporter | Open or serve the report |
@@ -98,7 +98,7 @@ curl -X POST "$SLACK_WEBHOOK_URL" \
 
 #### TestRail Push (If Configured)
 
-Invoke `/pw:testrail push` with the JSON results.
+Invoke `/playwright-pro testrail push` with the JSON results.
 
 #### HTML Report
 

package/skills/playwright-pro/skills/testrail/SKILL.md

@@ -25,7 +25,7 @@ If not set, inform the user how to configure them and stop.
 ### 1. Import Test Cases → Generate Playwright Tests
 
 ```
-/pw:testrail import --project <id> --suite <id>
+/playwright-pro testrail import --project <id> --suite <id>
 ```
 
 Steps:
@@ -40,7 +40,7 @@ Steps:
 ### 2. Push Test Results → TestRail
 
 ```
-/pw:testrail push --run <id>
+/playwright-pro testrail push --run <id>
 ```
 
 Steps:
@@ -58,7 +58,7 @@ Steps:
 ### 3. Create Test Run
 
 ```
-/pw:testrail run --project <id> --name "Sprint 42 Regression"
+/playwright-pro testrail run --project <id> --name "Sprint 42 Regression"
 ```
 
 Steps:
@@ -69,7 +69,7 @@ Steps:
 ### 4. Sync Status
 
 ```
-/pw:testrail status --project <id>
+/playwright-pro testrail status --project <id>
 ```
 
 Steps:
@@ -86,7 +86,7 @@ Steps:
 ### 5. Update Test Cases in TestRail
 
 ```
-/pw:testrail update --case <id>
+/playwright-pro testrail update --case <id>
 ```
 
 Steps:

package/skills/playwright-pro/templates/README.md

@@ -4,10 +4,10 @@
 
 ## Usage
 
-Templates are loaded by `/pw:generate` when it detects a matching scenario. You can also reference them directly:
+Templates are loaded by `/playwright-pro generate` when it detects a matching scenario. You can also reference them directly:
 
 ```
-/pw:generate "login flow"  → loads templates/auth/login.md
+/playwright-pro generate "login flow"  → loads templates/auth/login.md
 ```
 
 ## Template Index

package/skills/prototype/SKILL.md

@@ -9,7 +9,7 @@ allowed-tools: Read, Glob, Grep, Write, Edit, Bash, Task
 
 ## Phase 1: Define the Question
 
-Resolve review mode: `--review` arg > `production/review-mode.txt` > default `lean`. See `.claude/docs/director-gates.md`.
+Resolve review mode: `--review` arg > `production/review-mode.txt` > default `lean`.
 
 Read concept description. Identify core question the prototype must answer. If vague, state question explicitly before proceeding.
 

package/skills/quick-design/SKILL.md

@@ -44,4 +44,4 @@ Present draft → ask write approval → `design/quick-specs/[kebab-case]-[YYYY-
 
 Report: file written, type, system, GDD update status. Next: `/story-readiness` (reference spec in story's GDD Reference field).
 
-Bypasses `/design-review` by design. Redirect to full pipeline if: new system belongs in index, significantly alters cross-system behavior, introduces new player-facing mechanics affecting MDA balance, or >1 week implementation.
+Skips the full GDD pipeline (`/design-system`) by design. Redirect to full pipeline if: new system belongs in index, significantly alters cross-system behavior, introduces new player-facing mechanics affecting MDA balance, or >1 week implementation.

package/skills/release-checklist/SKILL.md

@@ -60,4 +60,3 @@ Present checklist + total items + known blockers. "May I write to `production/re
 ## Phase 6: Next Steps
 
 - `/gate-check` for formal phase gate verdict
-- Coordinate sign-offs via `/team-release`

package/skills/security-audit/SKILL.md

@@ -28,7 +28,7 @@ Output: `production/security/security-audit-[date].md`
 | `quick` | High-severity checks only (fastest) |
 | No arg | `full` |
 
-Read `.claude/docs/technical-preferences.md` for engine, language, platforms, multiplayer scope.
+Detect language, platforms and, for a game, the engine (`ProjectSettings/ProjectVersion.txt` (Unity) or the `.uproject` (Unreal)) from the project files. Take multiplayer scope from the GDD, or ask.
 
 ## Phase 2: Spawn Security Engineer
 

package/skills/self-improving-agent/CLAUDE.md

@@ -4,13 +4,13 @@ This plugin helps you curate Claude Code's auto-memory into durable project know
 
 ## Commands
 
-Use the `/si:` namespace for all commands:
+All commands are sub-commands of `/self-improving-agent`:
 
-- `/si:review` — Analyze auto-memory health and find promotion candidates
-- `/si:promote <pattern>` — Graduate a learning to CLAUDE.md or `.claude/rules/`
-- `/si:extract <pattern>` — Create a reusable skill from a proven pattern
-- `/si:status` — Quick memory health dashboard
-- `/si:remember <knowledge>` — Explicitly save something to auto-memory
+- `/self-improving-agent review` — Analyze auto-memory health and find promotion candidates
+- `/self-improving-agent promote <pattern>` — Graduate a learning to CLAUDE.md or `.claude/rules/`
+- `/self-improving-agent extract <pattern>` — Create a reusable skill from a proven pattern
+- `/self-improving-agent status` — Quick memory health dashboard
+- `/self-improving-agent remember <knowledge>` — Explicitly save something to auto-memory
 
 ## How auto-memory works
 
@@ -22,25 +22,25 @@ This plugin reads that directory — it never creates its own storage.
 
 ### After completing a feature or debugging session
 ```
-/si:review
+/self-improving-agent review
 ```
 Check if anything Claude learned should become a permanent rule.
 
 ### When a pattern keeps coming up
 ```
-/si:promote "Always run migrations before tests in this project"
+/self-improving-agent promote "Always run migrations before tests in this project"
 ```
 Moves it from MEMORY.md (background note) to CLAUDE.md (enforced rule).
 
 ### When you solved something non-obvious that could help other projects
 ```
-/si:extract "Docker build fix for ARM64 platform mismatch"
+/self-improving-agent extract "Docker build fix for ARM64 platform mismatch"
 ```
 Creates a standalone skill with SKILL.md, ready to install elsewhere.
 
 ### To check memory capacity
 ```
-/si:status
+/self-improving-agent status
 ```
 Shows line counts, topic files, stale entries, and recommendations.
 
@@ -55,8 +55,8 @@ Shows line counts, topic files, stale entries, and recommendations.
 
 ## Agents
 
-- **memory-analyst**: Spawned by `/si:review` to analyze patterns across memory files
-- **skill-extractor**: Spawned by `/si:extract` to generate complete skill packages
+- **memory-analyst**: Spawned by `/self-improving-agent review` to analyze patterns across memory files
+- **skill-extractor**: Spawned by `/self-improving-agent extract` to generate complete skill packages
 
 ## Hooks
 

package/skills/self-improving-agent/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: self-improving-agent
 description: "Curate Claude Code's auto-memory into durable project knowledge. Analyze MEMORY.md for patterns, promote proven learnings to CLAUDE.md and .claude/rules/, extract recurring solutions into reusable skills."
-argument-hint: ""
+argument-hint: "[extract|promote|remember|review|status] [args]"
 category: "arcane"
 user-invocable: true
 allowed-tools: Read, Glob, Grep, Bash, Write, Edit
@@ -11,15 +11,19 @@ allowed-tools: Read, Glob, Grep, Bash, Write, Edit
 
 Claude Code's auto-memory (v2.1.32+) automatically records project patterns, debugging insights, and your preferences in `MEMORY.md`. This skill adds the intelligence layer: it analyzes what Claude has learned, promotes proven patterns into project rules, and extracts recurring solutions into reusable skills. May write or edit CLAUDE.md, .claude/rules/ files, and new skill files during promotion and extraction.
 
+## Sub-commands
+
+`/self-improving-agent` with no argument shows this overview. With a sub-command as its first argument, read `skills/<sub-command>/SKILL.md` from this skill's directory and follow it, passing the remaining arguments. Sub-commands: `extract`, `promote`, `remember`, `review`, `status`.
+
 ## Quick Reference
 
 | Command | What it does |
 |---------|-------------|
-| `/si:review` | Analyze MEMORY.md -- find promotion candidates, stale entries, consolidation opportunities |
-| `/si:promote` | Graduate a pattern from MEMORY.md to CLAUDE.md or `.claude/rules/` |
-| `/si:extract` | Turn a proven pattern into a standalone skill |
-| `/si:status` | Memory health dashboard -- line counts, topic files, recommendations |
-| `/si:remember` | Explicitly save important knowledge to auto-memory |
+| `/self-improving-agent review` | Analyze MEMORY.md -- find promotion candidates, stale entries, consolidation opportunities |
+| `/self-improving-agent promote` | Graduate a pattern from MEMORY.md to CLAUDE.md or `.claude/rules/` |
+| `/self-improving-agent extract` | Turn a proven pattern into a standalone skill |
+| `/self-improving-agent status` | Memory health dashboard -- line counts, topic files, recommendations |
+| `/self-improving-agent remember` | Explicitly save important knowledge to auto-memory |
 
 ## How It Fits Together
 
@@ -33,9 +37,9 @@ Claude Code's auto-memory (v2.1.32+) automatically records project patterns, deb
 │  standards  │   + topic files  │   + continuity         │
 │  Full load  │   First 200 lines│   Contextual load      │
 ├─────────────┴──────────────────┴────────────────────────┤
-│              /si:promote          /si:review             │
+│              /self-improving-agent promote          /self-improving-agent review             │
 │         Self-Improving Agent (this skill)                │
-│              /si:extract      /si:remember              │
+│              /self-improving-agent extract      /self-improving-agent remember              │
 ├─────────────────────────────────────────────────────────┤
 │  .claude/rules/    │    New Skills    │   Error Logs     │
 │  (scoped rules)    │    (extracted)   │   (auto-captured)│
@@ -48,18 +52,18 @@ Claude Code's auto-memory (v2.1.32+) automatically records project patterns, deb
 
 | File | Who writes | Scope | Loaded |
 |------|-----------|-------|--------|
-| `./CLAUDE.md` | You (+ `/si:promote`) | Project rules | Full file, every session |
+| `./CLAUDE.md` | You (+ `/self-improving-agent promote`) | Project rules | Full file, every session |
 | `~/.claude/CLAUDE.md` | You | Global preferences | Full file, every session |
 | `~/.claude/projects/<path>/memory/MEMORY.md` | Claude (auto) | Project learnings | First 200 lines |
 | `~/.claude/projects/<path>/memory/*.md` | Claude (overflow) | Topic-specific notes | On demand |
-| `.claude/rules/*.md` | You (+ `/si:promote`) | Scoped rules | When matching files open |
+| `.claude/rules/*.md` | You (+ `/self-improving-agent promote`) | Scoped rules | When matching files open |
 
 ### The promotion lifecycle
 
 ```
 1. Claude discovers pattern -> auto-memory (MEMORY.md)
-2. Pattern recurs 2-3x -> /si:review flags it as promotion candidate
-3. You approve -> /si:promote graduates it to CLAUDE.md or rules/
+2. Pattern recurs 2-3x -> /self-improving-agent review flags it as promotion candidate
+3. You approve -> /self-improving-agent promote graduates it to CLAUDE.md or rules/
 4. Pattern becomes an enforced rule, not just a note
 5. MEMORY.md entry removed -> frees space for new learnings
 ```

package/skills/self-improving-agent/agents/memory-analyst.md

@@ -64,7 +64,7 @@ Organize findings into:
 
 ## Output Format
 
-Use the format defined in the `/si:review` skill. Be specific — include line numbers, exact text, and concrete suggestions.
+Use the format defined in the `/self-improving-agent review` skill. Be specific — include line numbers, exact text, and concrete suggestions.
 
 ## Constraints
 

package/skills/self-improving-agent/hooks/error-capture.sh

@@ -103,8 +103,8 @@ cat << EOF
 <error-detected>
 Command error detected (pattern: "$matched_pattern").
 If this was unexpected or required investigation to fix, save the solution:
-  /si:remember "explanation of what went wrong and the fix"
-Or if this is a known pattern, check: /si:review
+  /self-improving-agent remember "explanation of what went wrong and the fix"
+Or if this is a known pattern, check: /self-improving-agent review
 Context: $(echo "$error_context" | head -2 | tr '\n' ' ' | cut -c1-200)
 </error-detected>
 EOF

package/skills/self-improving-agent/reference/memory-architecture.md

@@ -103,7 +103,7 @@ When entries conflict:
 ```
 Auto-memory captures → This plugin curates → CLAUDE.md enforces
 
-MEMORY.md (raw notes)  →  /si:review (analyze)  →  /si:promote (graduate)
+MEMORY.md (raw notes)  →  /self-improving-agent review (analyze)  →  /self-improving-agent promote (graduate)
                                                           ↓
                                                     CLAUDE.md or
                                                     .claude/rules/
@@ -128,4 +128,4 @@ MEMORY.md (raw notes)  →  /si:review (analyze)  →  /si:promote (graduate)
 3. **Don't duplicate** — if it's in CLAUDE.md, remove it from MEMORY.md
 4. **Scope rules** — use `.claude/rules/` with paths for file-type-specific patterns
 5. **Review quarterly** — memory files go stale after refactors
-6. **Use /si:status** — monitor capacity before it becomes a problem
+6. **Use /self-improving-agent status** — monitor capacity before it becomes a problem

package/skills/self-improving-agent/reference/promotion-rules.md

@@ -74,10 +74,10 @@ When promoting, transform the learning:
 ## Promotion Workflow
 
 ```
-1. /si:review identifies candidate
+1. /self-improving-agent review identifies candidate
 2. Confirm the pattern is still valid
 3. Distill into one-line instruction
-4. /si:promote writes to CLAUDE.md or rules/
+4. /self-improving-agent promote writes to CLAUDE.md or rules/
 5. Remove from MEMORY.md
-6. Verify with /si:status
+6. Verify with /self-improving-agent status
 ```

package/skills/self-improving-agent/reference/rules-directory-patterns.md

@@ -125,7 +125,7 @@ paths:
 |--------|--------|
 | CLAUDE.md over 150 lines | Move scoped patterns to rules/ |
 | Same instruction repeated for different file types | Create a scoped rule |
-| `/si:promote` suggests a file-type-specific pattern | Create or append to a rule file |
+| `/self-improving-agent promote` suggests a file-type-specific pattern | Create or append to a rule file |
 | Team adds a new convention for a specific area | New rule file |
 
 ## Organization Tips

package/skills/self-improving-agent/settings.json

@@ -10,11 +10,11 @@
   "tags": ["memory", "auto-memory", "self-improvement", "learning", "rules", "skills"],
   "repository": "https://github.com/alirezarezvani/claude-skills",
   "commands": {
-    "review": "/si:review",
-    "promote": "/si:promote",
-    "extract": "/si:extract",
-    "status": "/si:status",
-    "remember": "/si:remember"
+    "review": "/self-improving-agent review",
+    "promote": "/self-improving-agent promote",
+    "extract": "/self-improving-agent extract",
+    "status": "/self-improving-agent status",
+    "remember": "/self-improving-agent remember"
   },
   "hooks": {
     "PostToolUse": {

package/skills/self-improving-agent/skills/extract/SKILL.md

@@ -7,17 +7,17 @@ user-invocable: false
 allowed-tools: Read, Glob, Grep, Bash, Write, Edit
 ---
 
-# /si:extract — Create Skills from Patterns
+# /self-improving-agent extract — Create Skills from Patterns
 
 Transforms a recurring pattern or debugging solution into a standalone, portable skill that can be installed in any project.
 
 ## Usage
 
 ```
-/si:extract <pattern description>                  # Interactive extraction
-/si:extract <pattern> --name docker-m1-fixes       # Specify skill name
-/si:extract <pattern> --output ./skills/            # Custom output directory
-/si:extract <pattern> --dry-run                     # Preview without creating files
+/self-improving-agent extract <pattern description>                  # Interactive extraction
+/self-improving-agent extract <pattern> --name docker-m1-fixes       # Specify skill name
+/self-improving-agent extract <pattern> --output ./skills/            # Custom output directory
+/self-improving-agent extract <pattern> --dry-run                     # Preview without creating files
 ```
 
 ## When to Extract
@@ -153,7 +153,7 @@ Source: MEMORY.md entries at lines {{n, m, ...}} (retained — the skill is port
 ### Extracting a debugging pattern
 
 ```
-/si:extract "Fix for Docker builds failing on Apple Silicon with platform mismatch"
+/self-improving-agent extract "Fix for Docker builds failing on Apple Silicon with platform mismatch"
 ```
 
 Creates `docker-m1-fixes/SKILL.md` with:
@@ -165,7 +165,7 @@ Creates `docker-m1-fixes/SKILL.md` with:
 ### Extracting a workflow pattern
 
 ```
-/si:extract "Always regenerate TypeScript API client after modifying OpenAPI spec"
+/self-improving-agent extract "Always regenerate TypeScript API client after modifying OpenAPI spec"
 ```
 
 Creates `api-client-regen/SKILL.md` with:

package/skills/self-improving-agent/skills/promote/SKILL.md

@@ -7,17 +7,17 @@ user-invocable: false
 allowed-tools: Read, Glob, Grep, Bash, Write, Edit
 ---
 
-# /si:promote — Graduate Learnings to Rules
+# /self-improving-agent promote — Graduate Learnings to Rules
 
 Moves a proven pattern from Claude's auto-memory into the project's rule system, where it becomes an enforced instruction rather than a background note.
 
 ## Usage
 
 ```
-/si:promote <pattern description>                    # Auto-detect best target
-/si:promote <pattern> --target claude.md             # Promote to CLAUDE.md
-/si:promote <pattern> --target rules/testing.md      # Promote to scoped rule
-/si:promote <pattern> --target rules/api.md --paths "src/api/**/*.ts"  # Scoped with paths
+/self-improving-agent promote <pattern description>                    # Auto-detect best target
+/self-improving-agent promote <pattern> --target claude.md             # Promote to CLAUDE.md
+/self-improving-agent promote <pattern> --target rules/testing.md      # Promote to scoped rule
+/self-improving-agent promote <pattern> --target rules/api.md --paths "src/api/**/*.ts"  # Scoped with paths
 ```
 
 ## Workflow

package/skills/self-improving-agent/skills/remember/SKILL.md

@@ -7,17 +7,17 @@ user-invocable: false
 allowed-tools: Read, Glob, Grep, Bash, Write, Edit
 ---
 
-# /si:remember — Save Knowledge Explicitly
+# /self-improving-agent remember — Save Knowledge Explicitly
 
 Writes an explicit entry to auto-memory when something is important enough that you don't want to rely on Claude noticing it automatically.
 
 ## Usage
 
 ```
-/si:remember <what to remember>
-/si:remember "This project's CI requires Node 20 LTS — v22 breaks the build"
-/si:remember "The /api/auth endpoint uses a custom JWT library, not passport"
-/si:remember "Reza prefers explicit error handling over try-catch-all patterns"
+/self-improving-agent remember <what to remember>
+/self-improving-agent remember "This project's CI requires Node 20 LTS — v22 breaks the build"
+/self-improving-agent remember "The /api/auth endpoint uses a custom JWT library, not passport"
+/self-improving-agent remember "Reza prefers explicit error handling over try-catch-all patterns"
 ```
 
 ## When to Use
@@ -63,7 +63,7 @@ Keep entries concise — one line when possible. Auto-memory entries don't need
 If MEMORY.md is over 180 lines, warn the user:
 
 ```
-⚠️ MEMORY.md is at {{n}}/200 lines. Consider running /si:review to free space.
+⚠️ MEMORY.md is at {{n}}/200 lines. Consider running /self-improving-agent review to free space.
 ```
 
 ### Step 4: Suggest promotion
@@ -72,7 +72,7 @@ If the knowledge sounds like a rule (imperative, always/never, convention):
 
 ```
 💡 This sounds like it could be a CLAUDE.md rule rather than a memory entry.
-   Rules are enforced with higher priority. Want to /si:promote it instead?
+   Rules are enforced with higher priority. Want to /self-improving-agent promote it instead?
 ```
 
 ### Step 5: Confirm
@@ -86,10 +86,10 @@ If the knowledge sounds like a rule (imperative, always/never, convention):
   Claude will see this at the start of every session in this project.
 ```
 
-## What NOT to use /si:remember for
+## What NOT to use /self-improving-agent remember for
 
 - **Temporary context**: Use session memory or just tell Claude in conversation
-- **Enforced rules**: Use `/si:promote` to write directly to CLAUDE.md
+- **Enforced rules**: Use `/self-improving-agent promote` to write directly to CLAUDE.md
 - **Cross-project knowledge**: Use `~/.claude/CLAUDE.md` for global rules
 - **Sensitive data**: Never store credentials, tokens, or secrets in memory files