claude-code-arcane 2.9.8 → 2.9.9

package/CHANGELOG.md

@@ -1,3 +1,17 @@
+## [2.9.9](https://github.com/SebastianLuser/claude-code-arcane/compare/v2.9.8...v2.9.9) (2026-10-10)
+
+
+### Bug Fixes
+
+* **content:** remove stale facts and dated prompting found by a prompt audit ([f6d0cf0](https://github.com/SebastianLuser/claude-code-arcane/commit/f6d0cf0abef40682a5ea7b5546c740787267c2bb))
+* **rules:** install the LLM rule with backend-go as llm-code ([8fbac31](https://github.com/SebastianLuser/claude-code-arcane/commit/8fbac317376dd0243878db501ce996df705e3478))
+* **skills:** price current Claude models in the cost estimators ([352e062](https://github.com/SebastianLuser/claude-code-arcane/commit/352e0623123de5833e6734fa785e71c06c004429))
+* **skills:** reach playwright-pro and self-improving-agent sub-skills through their parent ([4cc9dff](https://github.com/SebastianLuser/claude-code-arcane/commit/4cc9dffe71c406d1e12ccdb041587b3607a301b2))
+* **skills:** read the engine from the project in the last four skills ([120c8eb](https://github.com/SebastianLuser/claude-code-arcane/commit/120c8eb0ddee200acea6e2f29b0f04e3118b6b5a))
+* **skills:** route the remaining skills to skills and files that exist ([eb2eea0](https://github.com/SebastianLuser/claude-code-arcane/commit/eb2eea0eed4e1ba8964a1944548cb9ae9b386a4e))
+* **skills:** stop pricing and advising prompts from 2023 in the prompt tools ([429247d](https://github.com/SebastianLuser/claude-code-arcane/commit/429247db70689e3df86fc1bfdf7b78cab3e10195))
+* **update:** keep .claude/docs/ current like the other installed content ([f753c03](https://github.com/SebastianLuser/claude-code-arcane/commit/f753c030b73c89d5f3d035f0460954ba8d8c69a4))
+
 ## [2.9.8](https://github.com/SebastianLuser/claude-code-arcane/compare/v2.9.7...v2.9.8) (2026-09-09)
 
 

package/agents/business/business-ops-lead.md

@@ -32,20 +32,7 @@ Sos el **Business Operations Lead**. Tu rol: que el motor comercial funcione —
 
 ## Customer Health Score
 
-```
-Health Score = weighted average of:
-  Product Usage (30%):    DAU/MAU, feature adoption, depth
-  Support (20%):          Ticket volume, CSAT, escalations
-  Engagement (20%):       NPS, exec sponsor active, QBR attendance
-  Financial (15%):        Payment on time, expansion signals
-  Relationship (15%):     Champion changes, stakeholder map
-  
-Tiers:
-  90-100: Healthy (green)  → Expansion candidate
-  70-89:  Monitor (yellow) → Proactive outreach
-  50-69:  At Risk (orange) → Success plan
-  <50:    Critical (red)   → Executive intervention
-```
+Calculate it with `health_score_calculator.py` from the `customer-success-manager` skill: its dimensions, weights and segment thresholds are the ones in use. Do not compute it by hand.
 
 ## Protocolo
 

package/agents/game/gameplay-programmer.md

@@ -69,10 +69,9 @@ arrive. Decide, act, and make your reasoning auditable in the report.
 ### Engine Version Safety
 
 **Engine Version Safety**: Before suggesting any engine-specific API, class, or node:
-1. Check `docs/engine-reference/[engine]/VERSION.md` for the project's pinned engine version
-2. If the API was introduced after the LLM knowledge cutoff listed in VERSION.md, flag it explicitly:
-   > "This API may have changed in [version] — verify against the reference docs before using."
-3. Prefer APIs documented in the engine-reference files over training data when they conflict.
+1. Read the engine version from the project: `ProjectSettings/ProjectVersion.txt` (Unity) or `EngineAssociation` in the `.uproject` (Unreal)
+2. If the API may have changed in that version, flag it explicitly:
+   > "This API may have changed in [version] — verify against the engine docs before using."
 
 **ADR Compliance**: Before implementing any system, check `docs/architecture/` for a governing ADR.
 If an ADR exists for this system:

package/agents/game/technical-artist.md

@@ -68,10 +68,9 @@ arrive. Decide, act, and make your reasoning auditable in the report.
 ### Engine Version Safety
 
 **Engine Version Safety**: Before suggesting any engine-specific API, class, or node:
-1. Check `docs/engine-reference/[engine]/VERSION.md` for the project's pinned engine version
-2. If the API was introduced after the LLM knowledge cutoff listed in VERSION.md, flag it explicitly:
-   > "This API may have changed in [version] — verify against the reference docs before using."
-3. Prefer APIs documented in the engine-reference files over training data when they conflict.
+1. Read the engine version from the project: `ProjectSettings/ProjectVersion.txt` (Unity) or `EngineAssociation` in the `.uproject` (Unreal)
+2. If the API may have changed in that version, flag it explicitly:
+   > "This API may have changed in [version] — verify against the engine docs before using."
 
 ### Performance Budgets
 

package/dist/cli.js

@@ -751,7 +751,8 @@ function computeContentHashes(claudeDir) {
     skills: {},
     rules: {},
     agents: {},
-    hooks: {}
+    hooks: {},
+    docs: {}
   };
   const skillsDir = path7.join(claudeDir, "skills");
   if (fs6.existsSync(skillsDir)) {
@@ -790,6 +791,8 @@ function computeContentHashes(claudeDir) {
       }
     }
   }
+  const docsDir = path7.join(claudeDir, "docs");
+  if (fs6.existsSync(docsDir)) hashes.docs = hashDirectory(docsDir);
   return hashes;
 }
 function computeSourceHashes(packageRoot, skills, rules, agents) {
@@ -797,7 +800,8 @@ function computeSourceHashes(packageRoot, skills, rules, agents) {
     skills: {},
     rules: {},
     agents: {},
-    hooks: {}
+    hooks: {},
+    docs: {}
   };
   for (const skill of skills) {
     const skillDir = path7.join(packageRoot, "skills", skill);
@@ -836,6 +840,8 @@ function computeSourceHashes(packageRoot, skills, rules, agents) {
       }
     }
   }
+  const docsDir = path7.join(packageRoot, "docs");
+  if (fs6.existsSync(docsDir)) hashes.docs = hashDirectory(docsDir);
   return hashes;
 }
 
@@ -2547,6 +2553,10 @@ Update available: ${chalk7.red(installedVersion)} -> ${chalk7.green(currentVersi
   const sourceHashes = computeSourceHashes(root, merged.skills, allRules, merged.agents);
   const claudeDir = path17.join(target, ".claude");
   const installedHashes = computeContentHashes(claudeDir);
+  if (isSymlink(path17.join(claudeDir, "docs"))) {
+    sourceHashes.docs = {};
+    installedHashes.docs = {};
+  }
   const unhashed = earlySync;
   const items = computeUpdatePlan(
     manifest.content_hashes ?? null,
@@ -2649,10 +2659,21 @@ function printGeneralSummary(results, isDryRun) {
 ${prefix}Done. ${results.length} installation${results.length === 1 ? "" : "s"} processed:`));
   console.log(`  ${chalk7.green(updated)} ${isDryRun ? "would change" : "updated"}, ${chalk7.dim(unchanged + " unchanged")}`);
 }
+var RETIRED_DOCS = /* @__PURE__ */ new Set([
+  "RELEASE-SETUP.md",
+  "trusted-publishing-setup.md",
+  "presentations/arcane-overview.pptx",
+  "presentations/arcane-overview-12.pptx",
+  "presentations/build_arcane_deck.py",
+  "presentations/build_arcane_deck_12.py"
+]);
 function makeOwnershipCheck(manifest) {
   const hashes = manifest.content_hashes;
   if (hashes) {
-    return (type, name) => name in (hashes[type] ?? {});
+    return (type, name) => {
+      if (type === "docs" && !hashes.docs) return RETIRED_DOCS.has(name);
+      return name in (hashes[type] ?? {});
+    };
   }
   const skills = new Set(manifest.installed_skills ?? []);
   const rules = new Set(
@@ -2671,6 +2692,8 @@ function makeOwnershipCheck(manifest) {
         return agents.has(name);
       case "hooks":
         return true;
+      case "docs":
+        return RETIRED_DOCS.has(name);
     }
   };
 }
@@ -2689,7 +2712,8 @@ function hashesToRecord(fresh, previous, items, force) {
     skills: { ...fresh.skills },
     rules: { ...fresh.rules },
     agents: { ...fresh.agents },
-    hooks: { ...fresh.hooks }
+    hooks: { ...fresh.hooks },
+    docs: { ...fresh.docs }
   };
   for (const item of items) {
     const bucket = `${item.type}s`;
@@ -2706,8 +2730,8 @@ function hashesToRecord(fresh, previous, items, force) {
 }
 function computeUpdatePlan(manifestHashes, installedHashes, sourceHashes, owned, exemptAgentDivisions = /* @__PURE__ */ new Set()) {
   const items = [];
-  for (const contentType of ["skills", "rules", "agents", "hooks"]) {
-    const itemType = contentType === "skills" ? "skill" : contentType === "rules" ? "rule" : contentType === "agents" ? "agent" : "hook";
+  for (const contentType of ["skills", "rules", "agents", "hooks", "docs"]) {
+    const itemType = contentType === "skills" ? "skill" : contentType === "rules" ? "rule" : contentType === "agents" ? "agent" : contentType === "hooks" ? "hook" : "doc";
     const manifest = manifestHashes?.[contentType] ?? {};
     const installed = installedHashes[contentType];
     const source = sourceHashes[contentType];
@@ -2942,6 +2966,8 @@ function getSourcePath(item, root) {
       return path17.join(root, "agents", item.name);
     case "hook":
       return path17.join(root, "hooks", item.name);
+    case "doc":
+      return path17.join(root, "docs", item.name);
     default:
       return null;
   }
@@ -2956,6 +2982,15 @@ function getInstalledPath(item, claudeDir) {
       return path17.join(claudeDir, "agents", item.name);
     case "hook":
       return path17.join(claudeDir, "hooks", item.name);
+    case "doc":
+      return path17.join(claudeDir, "docs", item.name);
+  }
+}
+function isSymlink(p3) {
+  try {
+    return fs15.lstatSync(p3).isSymbolicLink();
+  } catch {
+    return false;
   }
 }
 

package/docs/USER-GUIDE.md

@@ -414,7 +414,7 @@ La lista `agents:` de un profile acepta dos formas:
 
 ```yaml
 agents:
-  - game                        # la división entera: 30 agentes
+  - game                        # la división entera: 32 agentes
   - quality/security-architect  # solo ese agente
 ```
 

package/docs/coordination-rules.md

@@ -49,7 +49,7 @@ Cuando un agente es invocado como "gate" (approval gate), debe empezar la respue
 
 Luego el rationale. El token en la primera línea permite que el skill orquestador lo parsee.
 
-**Escalation:** Cuando múltiples gates corren en paralelo, aplica el verdict más estricto — un REJECT override cualquier APPROVE. Ver `director-gates.md` para gates definidos.
+**Escalation:** Cuando múltiples gates corren en paralelo, aplica el verdict más estricto — un REJECT override cualquier APPROVE.
 
 ## Regla #6 — Cross-Division Collaboration
 

package/docs/directory-structure.md

@@ -1,31 +1,40 @@
 # Estructura de Directorios
 
+Hay dos layouts distintos y conviene no mezclarlos:
+
+- **El repo** (`claude-code-arcane/`): la fuente. Acá se edita el contenido y el instalador.
+- **Un proyecto instalado** (`<proyecto>/.claude/`): lo que `npx claude-code-arcane install <profile>` copia. Solo llega lo que algún profile lista.
+
+## El repo
+
 ```
-Claude-Code-Arcane/
-├── CLAUDE.md                          # Configuración maestra
-├── README.md                          # Documentación del repo
-├── pyproject.toml                     # Python package config
+claude-code-arcane/
+├── CLAUDE.md                          # Guía para trabajar en este repo
+├── README.md                          # Documentación pública
+├── CHANGELOG.md                       # Generado por semantic-release, no se edita a mano
+├── ATTRIBUTION.md                     # Origen del contenido adaptado de terceros
 ├── LICENSE
-├── .gitignore
+├── package.json                       # CLI npm: build (tsup), test (vitest), test:skills (Python)
+├── tsconfig.json
+├── vitest.config.ts                   # Aísla ARCANE_SOURCE y ARCANE_HOME para la suite
+├── .releaserc.json                    # semantic-release
+│
+├── src/                               # Instalador TypeScript (único código con build y typecheck)
+│   ├── cli.ts                         # Entry point: arcane install/add/remove/update/...
+│   ├── commands/                      # Un archivo por subcomando
+│   ├── installer.ts                   # Copia contenido a .claude/ y genera settings.json
+│   ├── profiles.ts                    # Parser y merge de profiles/*.yaml
+│   ├── agent-entries.ts               # Entradas de agentes: división entera o agente suelto
+│   ├── content-source.ts, cache.ts    # Fuente del contenido: bundled / github / cache
+│   ├── manifest.ts, content-hash.ts   # arcane-manifest.json y hashes para update
+│   ├── registry.ts                    # ~/.arcane/installations.json
+│   ├── worktree.ts                    # Instalación en git worktrees
+│   ├── wizard.ts, detect.ts           # Wizard interactivo y auto-detección de stack
+│   └── __tests__/                     # Suite vitest, incluidos los invariantes de docs
 │
-├── arcane/                            # Python CLI (installer, profiles parser)
-│   ├── cli.py                         # Entry point: arcane install/list/clean
-│   ├── installer.py                   # Profile installer logic
-│   └── profiles.py                    # Profile parser & merger
+├── profiles/                          # Profiles declarativos (.yaml); core.yaml siempre se carga
 │
-├── profiles/                          # 27 profile definitions (.profile)
-│   ├── core.profile                   # Always included (21 skills, hooks, rules)
-│   ├── backend-go.profile             # Base: Go backend
-│   ├── backend-ts.profile             # Base: TypeScript backend
-│   ├── frontend.profile               # Base: React frontend
-│   ├── unity-dev.profile              # Base: Unity programmer
-│   ├── ai.profile                     # Add-on: AI/ML
-│   ├── clevel.profile                 # Add-on: C-suite advisory
-│   ├── business.profile               # Add-on: Business ops
-│   ├── marketing.profile              # Add-on: Marketing
-│   ├── finance.profile                # Add-on: Finance
-│   ├── regulatory.profile             # Add-on: Regulatory & compliance
-│   └── ...                            # agile, testing, infra, security, etc.
+├── skills/                            # Un directorio por skill: SKILL.md + references/ + scripts/
 │
 ├── agents/                            # 115 agent definitions (root level)
 │   ├── ai/                            # 4 agents
@@ -46,116 +55,78 @@ Claude-Code-Arcane/
 │   ├── regulatory/                    # 3 agents
 │   └── visualnovel/                   # 6 agents
 │
-├── .claude/                           # Claude Code configuration
-│   ├── settings.json                  # Hooks, permissions, safety
-│   ├── settings.local.json            # User-specific overrides (gitignored)
-│   ├── statusline.sh                  # Status line bash script
-│   ├── setup-skill-junctions.bat      # Windows: create skill junctions
-│   ├── remove-skill-junctions.bat     # Windows: remove skill junctions
-│   │
-│   ├── skills-agile/                  # 35 agile/PM skills
-│   ├── skills-ai/                     # 7 AI/ML skills
-│   ├── skills-arcane/                 # 7 Arcane self-management skills
-│   ├── skills-backend/                # 45 backend skills
-│   ├── skills-business/               # 4 business skills
-│   ├── skills-clevel-advisors/        # 10 C-suite advisor skills
-│   ├── skills-clevel-operations/      # 18 C-suite operations skills
-│   ├── skills-design/                 # 9 design skills
-│   ├── skills-devops/                 # 17 DevOps/infra skills
-│   ├── skills-docs/                   # 13 documentation skills
-│   ├── skills-finance/                # 3 finance skills
-│   ├── skills-frontend/               # 9 frontend skills
-│   ├── skills-gamedev/                # 19 gamedev skills + _rules/ + _templates/
-│   ├── skills-git/                    # 21 git workflow skills
-│   ├── skills-integrations/           # 3 integration skills
-│   ├── skills-marketing-content/      # 8 content marketing skills
-│   ├── skills-marketing-growth/       # 10 growth marketing skills
-│   ├── skills-marketing-seo/          # 11 SEO/CRO skills
-│   ├── skills-marketing-strategy/     # 15 marketing strategy skills
-│   ├── skills-mobile/                 # 5 mobile skills
-│   ├── skills-regulatory/             # 13 regulatory/compliance skills
-│   ├── skills-release/                # 5 release skills
-│   ├── skills-security/               # 9 security skills
-│   ├── skills-testing/                # 13 testing skills
-│   │
-│   ├── hooks/                         # 14 lifecycle hooks
-│   │   ├── session-start.sh
-│   │   ├── session-stop.sh
-│   │   ├── detect-division.sh
-│   │   ├── detect-gaps.sh
-│   │   ├── validate-commit.sh
-│   │   ├── validate-push.sh
-│   │   ├── validate-secrets.sh
-│   │   ├── validate-assets.sh
-│   │   ├── validate-skill-change.sh
-│   │   ├── notify.sh
-│   │   ├── pre-compact.sh
-│   │   ├── post-compact.sh
-│   │   ├── log-agent.sh
-│   │   └── log-agent-stop.sh
-│   │
-│   ├── rules/                         # 9 path-scoped rules
-│   │   ├── backend-code.md
-│   │   ├── frontend-code.md
-│   │   ├── api-code.md
-│   │   ├── migration-code.md
-│   │   ├── infra-code.md
-│   │   ├── ai-code.md
-│   │   ├── data-files.md
-│   │   ├── test-standards.md
-│   │   └── prototype-code.md
-│   │
-│   └── docs/                          # Internal documentation
-│       ├── division-structure.md
-│       ├── agent-hierarchy.md
-│       ├── directory-structure.md      # This file
-│       ├── coding-standards.md
-│       ├── technical-preferences.md
-│       ├── coordination-rules.md
-│       ├── context-management.md
-│       ├── workflow-catalog.yaml
-│       ├── stack-registry.md
-│       └── templates/
+├── rules/                             # Rules universales (rules.universal en los profiles)
+│   └── gamedev/                       # Rules de gamedev (rules.gamedev en los profiles)
 │
-├── docs/                              # Public documentation
-│   ├── SKILLS-CATALOG.md              # Complete skill catalog
-│   └── USER-GUIDE.md                  # User guide
+├── hooks/                             # Scripts bash de lifecycle; statusline.sh incluido
+├── output-styles/                     # Output styles (arcane.md)
+├── templates/
+│   └── gamedev/                       # Plantillas de GDD y docs de juego
+├── docs/                              # Documentación; se copia entera a .claude/docs/
+│   ├── templates/                     # Plantillas de ADR, PRD, RFC, test plan, etc.
+│   ├── gates/                         # Gates de fase (software y gamedev)
+│   └── gamedev/, software/            # coding-standards por dominio
 │
-├── tools/                             # Migration & wrapper scripts
-│   ├── arcane.sh                      # Legacy bash installer
-│   ├── arcane.bat                     # Windows wrapper
-│   └── migrate-*.sh                   # Migration tools
-│
-├── skills-selftest/                   # QA framework for skills/agents
+├── skills-selftest/                   # QA de skills y agentes (no se instala)
 │   ├── CLAUDE.md
-│   ├── catalog.yaml                   # Registry: 305 skills + 94 agents
-│   ├── quality-rubric.md
-│   ├── skills/[category]/             # Behavioral specs per skill
-│   ├── agents/[tier]/                 # Behavioral specs per agent
-│   ├── templates/
-│   └── results/                       # Test outputs (gitignored)
+│   ├── catalog.yaml                   # Registro de skills y agentes con su spec
+│   ├── quality-rubric.md              # Métricas por categoría
+│   ├── skills/<categoria>/            # Specs de comportamiento por skill
+│   ├── agents/<tier>/                 # Specs de comportamiento por agente
+│   └── templates/                     # Plantillas para specs nuevos
 │
-└── production/                        # Runtime state
-    └── session-state/
+├── tests/                             # Specs Python de los scripts de skills (npm run test:skills)
+├── maintainers/                       # Cómo publicar Arcane (release, npm). No se instala ni se publica
+├── scripts/                           # Utilidades de mantenimiento del repo
+├── .github/workflows/                 # ci.yml (vitest, typecheck, specs Python) y release.yml (semantic-release)
+└── .claude/                           # La instalación de Arcane que usa este mismo repo
 ```
 
-## Rules Split Policy
+## Un proyecto instalado
 
-- **`.claude/rules/`** — reglas universales que aplican a cualquier stack software (backend APIs, frontends web/mobile, DBs, infra, LLM apps). Usan paths genéricos (`src/api/**`, `src/components/**`, `migrations/**`).
-- **`.claude/skills-gamedev/_rules/`** — reglas exclusivas de gamedev (frame budgets, shaders, NPC AI, GDDs, lore). Usan paths gamedev (`src/gameplay/**`, `assets/shaders/**`, `design/gdd/**`, `design/narrative/**`).
+```
+<proyecto>/
+├── .claude/
+│   ├── settings.json                  # Generado: permisos, hooks y statusline
+│   ├── arcane-manifest.json           # Profiles instalados y content_hashes de cada archivo
+│   ├── skills/<skill>/                # Los skills de los profiles elegidos, con sus references/ y scripts/
+│   │   └── _templates/                # templates/gamedev/, solo si algún profile trae rules de gamedev
+│   ├── agents/<division>/             # Divisiones enteras o agentes sueltos, según el profile
+│   ├── rules/                         # Universales y de gamedev juntas, en un solo nivel
+│   ├── hooks/                         # Todos los hooks de hooks/ salvo statusline.sh
+│   ├── statusline.sh                  # Solo con el profile statusline
+│   ├── output-styles/                 # Solo si algún profile declara output_styles
+│   ├── docs/                          # Copia de docs/; arcane update la mantiene al día
+│   └── .arcane-trash/                 # Lo que arcane update saca; nunca se borra con rm
+├── .claude.bak/                       # Backup de .claude/ antes de instalar
+└── production/session-state/          # Estado de sesión que escriben los hooks
+```
 
-Cuando un proyecto es dual (ej. web + game), ambos sets de rules aplican por sus paths scoped.
+Fuera del proyecto, `~/.arcane/` guarda el registro de instalaciones (`installations.json`) y el contenido descargado de GitHub (`cache/<version>/`). `ARCANE_HOME` lo desvía.
 
-## Hook Events Wiring
+En un git worktree, `hooks/` y `docs/` son symlinks al worktree principal; `skills/`, `agents/` y `rules/` se copian para que puedan divergir por rama.
 
-Ver `settings.json`. Los eventos wireados:
+## Rules: dos carpetas en el repo, una en el proyecto
+
+- **`rules/`**: reglas para cualquier stack de software (backend, frontend, APIs, DBs, infra, apps LLM). Paths genéricos como `src/api/**` o `src/components/**`.
+- **`rules/gamedev/`**: reglas exclusivas de gamedev (frame budgets, shaders, IA de NPCs, GDDs, lore). Paths como `src/gameplay/**`, `assets/shaders/**` o `design/gdd/**`.
+
+El installer copia las dos al mismo `.claude/rules/`, sin subcarpeta. Por eso un nombre no puede repetirse entre las dos carpetas: el segundo archivo pisaría al primero. La rule de apps LLM se llama `llm-code.md` justamente para no chocar con `gamedev/ai-code.md`, que es la de IA de NPCs.
+
+Cuando un proyecto es dual (por ejemplo web + juego), las dos familias aplican cada una por sus paths.
+
+## Hooks: cómo se cablean
+
+Los eventos los define `src/installer.ts` al generar `settings.json`, no los profiles. Todo proyecto instalado recibe estos:
 
 | Evento | Hooks |
 |--------|-------|
-| SessionStart | session-start.sh → detect-division.sh → detect-gaps.sh |
-| PreToolUse (Bash) | validate-commit.sh, validate-push.sh, validate-secrets.sh |
-| PostToolUse (Write/Edit) | validate-assets.sh, validate-skill-change.sh |
-| Notification | notify.sh |
-| PreCompact / PostCompact | pre-compact.sh / post-compact.sh |
-| Stop | session-stop.sh |
-| SubagentStart / SubagentStop | log-agent.sh / log-agent-stop.sh |
+| SessionStart | `session-start.sh` → `detect-division.sh` → `detect-unreal.sh` → `detect-gaps.sh` → `check-update.sh` |
+| PreToolUse (`Bash`) | `validate-commit.sh`, `validate-push.sh`, `validate-secrets.sh` |
+| PostToolUse (`Write\|Edit`) | `validate-assets.sh`, `validate-skill-change.sh` |
+| Notification | `notify.sh` |
+| PreCompact / PostCompact | `pre-compact.sh` / `post-compact.sh` |
+| Stop | `session-stop.sh` |
+| SubagentStart / SubagentStop | `log-agent.sh` / `log-agent-stop.sh` |
+
+La statusline (`statusline.sh`) se configura aparte, solo con el profile `statusline`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-code-arcane",
-  "version": "2.9.8",
+  "version": "2.9.9",
   "description": "Skills, agents, hooks and rules for Claude Code — installable via npx claude-code-arcane",
   "type": "module",
   "bin": {

package/profiles/backend-go.yaml

@@ -41,6 +41,7 @@ rules:
     - backend-code
     - api-code
     - migration-code
+    - llm-code
   gamedev:
     []
 

package/rules/gamedev/engine-code.md

@@ -13,7 +13,7 @@ paths:
 - Changes to public interfaces require a deprecation period and migration guide
 - Use RAII / deterministic cleanup for all resources
 - All engine systems must support graceful degradation
-- Before writing engine API code, consult `docs/engine-reference/` for the current engine version and verify APIs against the reference docs
+- Before writing engine API code, read the project's engine version (`ProjectSettings/ProjectVersion.txt` or the `.uproject`) and verify APIs against that version's docs
 
 ## Examples
 

package/rules/gamedev/shader-code.md

@@ -13,7 +13,6 @@ visual quality, performance, and cross-platform compatibility.
   - `SG_Env_Water` (Unity Shader Graph)
   - `M_Env_Water` (Unreal Material)
 - Use descriptive names that indicate the material purpose
-- Prefix with shader type: `spatial_`, `canvas_`, `particles_`, `post_`
 
 ## Code Quality
 - All uniforms/parameters must have descriptive names and appropriate hints
@@ -32,7 +31,7 @@ visual quality, performance, and cross-platform compatibility.
 ## Cross-Platform
 - Test shaders on minimum spec target hardware
 - Provide fallback/simplified versions for lower quality tiers
-- Document which render pipeline the shader targets (Forward/Deferred, URP/HDRP, Forward+/Mobile/Compatibility)
+- Document which render pipeline the shader targets (Forward/Deferred, URP/HDRP)
 - Do not mix shaders from different render pipelines in the same directory
 
 ## Variant Management

package/rules/gamedev/vn-code.md

@@ -1,6 +1,7 @@
 ---
-name: vn-code
-description: "Coding rules for Ren'Py visual novel development"
+paths:
+  - "game/**"
+  - "**/*.rpy"
 ---
 
 # Visual Novel Code Rules

package/rules/implementation-workflow.md

@@ -1,6 +1,6 @@
 # Implementation Workflow Rule
 
-Before starting any non-trivial implementation task, you MUST present the user with work mode options using AskUserQuestion. This is mandatory — do not skip it and jump to coding.
+Before starting a non-trivial implementation task, present the user with work mode options using AskUserQuestion, so they choose how much planning the task gets before any code is written.
 
 ## When to trigger
 

package/rules/{ai-code.md → llm-code.md}

@@ -1,9 +1,9 @@
 ---
 paths:
-  - "src/ai/**"
+  - "src/**/ai/**"
+  - "src/**/llm/**"
+  - "src/**/agents/**"
   - "src/ml/**"
-  - "src/llm/**"
-  - "src/agents/**"
   - "src/inference/**"
   - "prompts/**"
   - "models/**"
@@ -12,7 +12,7 @@ paths:
 # AI / LLM / ML Code Rules
 
 Applies to software integrations with LLMs, ML inference, and AI agents — not NPC behavior in games
-(that rule lives in `skills-gamedev/_rules/ai-code.md`).
+(the gamedev profiles ship their own `ai-code` rule for that).
 
 ## Prompts & Templates
 
@@ -28,7 +28,7 @@ Applies to software integrations with LLMs, ML inference, and AI agents — not
 - **Cost budget per request is measured and logged**: token counts in + out, model, cost in $. Track P50/P95 cost per feature.
 - **Timeouts and retries are bounded**: max retries ≤ 2, exponential backoff, circuit breaker on the provider. A hung LLM call must not hang a user request.
 - **Streaming for user-facing generation**; batch / async for back-office work.
-- **Cache deterministic calls** (same system + same user + temperature 0 → cache the response). Document TTL and invalidation.
+- **Cache deterministic calls** (same model + same system + same user → cache the response). Document TTL and invalidation.
 
 ## Safety & PII
 

package/skills/agent-designer/README.md

@@ -377,7 +377,8 @@ with open('my_tools_anthropic.json') as f:
 # Use with Anthropic tool use
 client = anthropic.Anthropic()
 response = client.messages.create(
-    model="claude-3-opus-20240229",
+    model="claude-opus-5-5",
+    max_tokens=16000,
     messages=[{"role": "user", "content": "Search for AI news"}],
     tools=schemas['tools']
 )

package/skills/agent-designer/agent_evaluator.py

@@ -220,11 +220,6 @@ class AgentEvaluator:
     def _define_cost_benchmarks(self) -> Dict[str, Any]:
         """Define cost benchmarks for different operations"""
         return {
-            "token_costs": {
-                "gpt-4": {"input": 0.00003, "output": 0.00006},
-                "gpt-3.5-turbo": {"input": 0.000002, "output": 0.000002},
-                "claude-3": {"input": 0.000015, "output": 0.000075}
-            },
             "operation_costs": {
                 "simple_task": 0.005,
                 "complex_task": 0.050,

package/skills/ai-sdk-setup/SKILL.md

@@ -15,7 +15,7 @@ allowed-tools: Read, Glob, Grep, Bash, Write, Edit, Task
 ### Step 0: Gather Requirements
 1. **Caso:** chat / generación one-shot / extracción structured / agente con tools / RAG
 2. **Streaming** al cliente o respuesta completa
-3. **Modelo:** Opus 4.8 (`claude-opus-4-8`, razonamiento) / Sonnet 4.6 (`claude-sonnet-4-6`, balance) / Haiku 4.5 (`claude-haiku-4-5-20251001`, rápido/barato)
+3. **Modelo:** Opus 5.5 (`claude-opus-5-5`, razonamiento) / Sonnet 5.5 (`claude-sonnet-5-5`, balance) / Haiku 5.5 (`claude-haiku-5-5`, rápido/barato)
 4. ¿Necesita tool calling / structured output / RAG (ver skill `pgvector-search`)?
 
 ### Step 1: Instalar
@@ -33,7 +33,7 @@ import { streamText, convertToModelMessages } from 'ai';
 export async function POST(req: Request) {
   const { messages } = await req.json();
   const result = streamText({
-    model: anthropic('claude-sonnet-4-6'),
+    model: anthropic('claude-sonnet-5-5'),
     messages: convertToModelMessages(messages),
   });
   return result.toUIMessageStreamResponse();
@@ -44,7 +44,7 @@ Cliente: `useChat()` de `@ai-sdk/react`.
 ### Step 3: Structured output (Zod)
 ```ts
 const { object } = await generateObject({
-  model: anthropic('claude-sonnet-4-6'),
+  model: anthropic('claude-sonnet-5-5'),
   schema: z.object({ sentiment: z.enum(['pos','neg','neutral']), score: z.number() }),
   prompt: text,
 });
@@ -53,7 +53,7 @@ const { object } = await generateObject({
 ### Step 4: Tool calling / agente
 ```ts
 const result = await generateText({
-  model: anthropic('claude-opus-4-8'),
+  model: anthropic('claude-opus-5-5'),
   tools: {
     search: tool({
       description: 'Buscar docs', inputSchema: z.object({ q: z.string() }),

package/skills/architecture-decision/SKILL.md

@@ -18,11 +18,10 @@ allowed-tools: Read, Glob, Grep, Write, Task, AskUserQuestion
 
 ## Phase 0: Load Engine Context (ALWAYS FIRST)
 
-1. Read `docs/engine-reference/[engine]/VERSION.md` → engine name, version, cutoff risk
+1. Read the engine version from the project: `ProjectSettings/ProjectVersion.txt` (Unity) or `EngineAssociation` in the `.uproject` (Unreal). For Unreal, also read `docs/unreal/project-context.md` if `/ue-project-context` has run
 2. Identify domain from title (Physics, Rendering, UI, Audio, etc.)
-3. Read module reference + `breaking-changes.md` + `deprecated-apis.md`
-4. Display knowledge gap warning if MEDIUM/HIGH risk
-5. No engine configured → prompt to run `/setup-engine`
+3. If the engine version is newer than what you know reliably, say so before proposing engine APIs
+4. No engine detected → ask the user which engine and version
 
 ## Phase 1: Context Gathering