claude-code-arcane 2.1.0 → 2.3.0

package/docs/USER-GUIDE.md

@@ -2,7 +2,7 @@
 
 ## What is Arcane?
 
-Arcane is a configuration harness for [Claude Code](https://docs.anthropic.com/en/docs/claude-code). It provides a curated library of **375 skills**, **92 agents**, **16 hooks**, and **25 rules** that you selectively deploy into any project. Instead of shipping everything to every project (wasting tokens and degrading performance), you pick a **profile** that matches your stack and only the relevant tools get installed.
+Arcane is a configuration harness for [Claude Code](https://docs.anthropic.com/en/docs/claude-code). It provides a curated library of **397 skills**, **106 agents**, **16 hooks**, and **27 rules** that you selectively deploy into any project. Instead of shipping everything to every project (wasting tokens and degrading performance), you pick a **profile** that matches your stack and only the relevant tools get installed.
 
 ## Table of Contents
 
@@ -38,7 +38,7 @@ Arcane is a configuration harness for [Claude Code](https://docs.anthropic.com/e
 No installation needed — Arcane runs via `npx`:
 
 ```bash
-npx arcane install backend-ts+agile
+npx claude-code-arcane install backend-ts+agile
 ```
 
 That's it. `npx` downloads and runs the latest version automatically.
@@ -50,7 +50,7 @@ That's it. `npx` downloads and runs the latest version automatically.
 cd ~/projects/my-app
 
 # 2. Install a profile
-npx arcane install backend-ts+agile
+npx claude-code-arcane install backend-ts+agile
 
 # 3. Open Claude Code
 claude
@@ -62,130 +62,135 @@ Your project now has skills, agents, hooks, rules, and permissions tailored for
 
 ## Commands Reference
 
-### `npx arcane install` — Install profiles
+### `npx claude-code-arcane install` — Install profiles
 
 ```bash
 # Show available profiles (interactive)
-npx arcane install
+npx claude-code-arcane install
 
 # Install a specific profile
-npx arcane install backend-ts
+npx claude-code-arcane install backend-ts
 
 # Combine profiles with +
-npx arcane install backend-ts+agile+testing
+npx claude-code-arcane install backend-ts+agile+testing
 
 # Install to a specific directory (default: current dir)
-npx arcane install unity-dev --target ~/projects/my-game
+npx claude-code-arcane install unity-dev --target ~/projects/my-game
 
 # Preview without installing
-npx arcane install unity-dev --dry-run
+npx claude-code-arcane install unity-dev --dry-run
 
 # Force overwrite without backup
-npx arcane install unity-dev --force
+npx claude-code-arcane install unity-dev --force
 ```
 
 If `.claude/` already exists, it gets backed up to `.claude.bak/` and replaced.
 
-### `npx arcane add` — Add skills or profiles
+### `npx claude-code-arcane add` — Add skills or profiles
 
 ```bash
 # Add a single skill
-npx arcane add api-design
+npx claude-code-arcane add api-design
 
 # Add multiple skills
-npx arcane add security-audit owasp
+npx claude-code-arcane add security-audit owasp
 
 # Add an entire profile as addon
-npx arcane add +security
+npx claude-code-arcane add +security
 
 # Add multiple profiles
-npx arcane add +database +testing
+npx claude-code-arcane add +database +testing
 ```
 
-### `npx arcane remove` — Remove skills, profiles, or agents
+### `npx claude-code-arcane remove` — Remove skills, profiles, or agents
 
 ```bash
 # Remove a single skill
-npx arcane remove api-design
+npx claude-code-arcane remove api-design
 
 # Remove multiple skills
-npx arcane remove slack postman
+npx claude-code-arcane remove slack postman
 
 # Remove entire profile (exclusive skills + agents + rules)
-npx arcane remove +agile
+npx claude-code-arcane remove +agile
 
 # Mix: remove a profile and a skill
-npx arcane remove +testing api-design
+npx claude-code-arcane remove +testing api-design
+
+# Remove using a specific content source instead of the installed version
+npx claude-code-arcane remove +testing --source bundled
 ```
 
 When removing a profile, Arcane only deletes assets **exclusive** to that profile. Skills, agents, and rules shared with other active profiles are preserved. Core skills (21) and the core profile cannot be removed.
 
-### `npx arcane list` — List available profiles and skills
+What gets deleted is read from that profile's definition, so `remove` uses the content of the version recorded in your manifest. If that version is no longer cached it falls back to the current one and says so: a profile whose skill or agent list changed between the two can leave files behind, and `--source` is the escape hatch. The known limit is that two builds sharing a version number (a local checkout and the published release, say) are indistinguishable, so removing content installed from an unreleased source needs `--source bundled` explicitly.
+
+### `npx claude-code-arcane list` — List available profiles and skills
 
 ```bash
-npx arcane list
+npx claude-code-arcane list
 ```
 
 Shows all base profiles and add-ons with descriptions, and marks which are currently installed.
 
-### `npx arcane status` — Check current installation
+### `npx claude-code-arcane status` — Check current installation
 
 ```bash
-npx arcane status
+npx claude-code-arcane status
 ```
 
 Shows installed profiles, skill count, rules, agents, installation date, and worktree info.
 
-### `npx arcane update` — Check for updates
+### `npx claude-code-arcane update` — Check for updates
 
 ```bash
-npx arcane update
+npx claude-code-arcane update
 
 # Quiet mode (for hooks — fails silently)
-npx arcane update --quiet
+npx claude-code-arcane update --quiet
 ```
 
-### `npx arcane clean` — Remove Arcane from a project
+### `npx claude-code-arcane clean` — Remove Arcane from a project
 
 ```bash
-npx arcane clean --force
+npx claude-code-arcane clean --force
 ```
 
 Removes `.claude/` and `.claude.bak/` from the current directory. Requires `--force` flag.
 
-### `npx arcane worktree` — Create worktrees with Arcane
+### `npx claude-code-arcane worktree` — Create worktrees with Arcane
 
 ```bash
 # Create worktree + install Arcane in one step
-npx arcane worktree feat/new-api --profile backend-ts+agile
+npx claude-code-arcane worktree feat/new-api --profile backend-ts+agile
 
 # Inherits profile from current installation
-npx arcane worktree feat/new-api
+npx claude-code-arcane worktree feat/new-api
 
 # With dependency install and Docker port isolation
-npx arcane worktree feat/new-api --install-deps --isolate
+npx claude-code-arcane worktree feat/new-api --install-deps --isolate
 
 # Custom path and base branch
-npx arcane worktree feat/new-api --path ../my-api-worktree --base develop
+npx claude-code-arcane worktree feat/new-api --path ../my-api-worktree --base develop
 
 # Preview without creating
-npx arcane worktree feat/new-api --dry-run
+npx claude-code-arcane worktree feat/new-api --dry-run
 
 # Don't share hooks/docs from current installation
-npx arcane worktree feat/new-api --no-share
+npx claude-code-arcane worktree feat/new-api --no-share
 ```
 
-### `npx arcane global` — Manage global hooks
+### `npx claude-code-arcane global` — Manage global hooks
 
 ```bash
 # Install global SessionStart hook (worktree-isolation auto-apply)
-npx arcane global
+npx claude-code-arcane global
 
 # Show global hooks status
-npx arcane global --status
+npx claude-code-arcane global --status
 
 # Remove global hooks
-npx arcane global --remove
+npx claude-code-arcane global --remove
 ```
 
 ---
@@ -252,7 +257,7 @@ Every installation automatically loads `core.yaml` first:
 Profiles are combined using the `+` separator. The system deduplicates skills automatically.
 
 ```bash
-npx arcane install <base>[+<base>][+<addon>][+<addon>]
+npx claude-code-arcane install <base>[+<base>][+<addon>][+<addon>]
 ```
 
 ### Rules
@@ -274,30 +279,30 @@ After the initial install, you can incrementally add or remove skills and profil
 
 ```bash
 # Start with a base profile
-npx arcane install backend-ts
+npx claude-code-arcane install backend-ts
 
 # Later, add testing and security
-npx arcane add +testing +security
+npx claude-code-arcane add +testing +security
 
 # Add a specific skill you need
-npx arcane add docker-setup
+npx claude-code-arcane add docker-setup
 
 # Check what you have
-npx arcane status
+npx claude-code-arcane status
 ```
 
 ### Remove workflow
 
 ```bash
 # Remove a profile you no longer need (only exclusive assets are deleted)
-npx arcane remove +testing
+npx claude-code-arcane remove +testing
 
 # Remove a specific skill
-npx arcane remove docker-setup
+npx claude-code-arcane remove docker-setup
 
 # Start over completely
-npx arcane clean --force
-npx arcane install backend-ts+agile
+npx claude-code-arcane clean --force
+npx claude-code-arcane install backend-ts+agile
 ```
 
 ---
@@ -310,18 +315,18 @@ Work on multiple features in parallel using git worktrees, each with its own Arc
 
 ```bash
 # Create worktree + install Arcane in one step
-npx arcane worktree feat/new-api --profile backend-ts+agile
+npx claude-code-arcane worktree feat/new-api --profile backend-ts+agile
 
 # Inherits profile from current installation
-npx arcane worktree feat/new-api
+npx claude-code-arcane worktree feat/new-api
 
 # With dependency install and Docker port isolation
-npx arcane worktree feat/new-api --install-deps --isolate
+npx claude-code-arcane worktree feat/new-api --install-deps --isolate
 ```
 
 ### Worktree-aware installation
 
-When you run `npx arcane install` inside a git worktree, Arcane automatically:
+When you run `npx claude-code-arcane install` inside a git worktree, Arcane automatically:
 - Detects it's in a worktree
 - Finds the main worktree's Arcane installation
 - **Shares** hooks/ and docs/ via symlink (read-only, identical across worktrees)
@@ -347,13 +352,13 @@ Install worktree-isolation scripts that auto-apply on every new Claude Code sess
 
 ```bash
 # Install global hooks
-npx arcane global
+npx claude-code-arcane global
 
 # Check status
-npx arcane global --status
+npx claude-code-arcane global --status
 
 # Remove
-npx arcane global --remove
+npx claude-code-arcane global --remove
 ```
 
 This copies scripts to `~/.claude/scripts/worktree-isolation/` and adds a `SessionStart` hook to `~/.claude/settings.json`.
@@ -364,41 +369,41 @@ This copies scripts to `~/.claude/scripts/worktree-isolation/` and adds a `Sessi
 
 ```bash
 # Unity dev only
-npx arcane install unity-dev
+npx claude-code-arcane install unity-dev
 
 # Unity with team and management
-npx arcane install unity-dev+unity-design+agile+clickup
+npx claude-code-arcane install unity-dev+unity-design+agile+clickup
 
 # Go microservice with infra
-npx arcane install backend-go+infra+agile+jira
+npx claude-code-arcane install backend-go+infra+agile+jira
 
 # Full-stack monorepo
-npx arcane install backend-ts+frontend+testing+database
+npx claude-code-arcane install backend-ts+frontend+testing+database
 
 # Mobile app with CI/CD
-npx arcane install mobile+agile+clickup+testing
+npx claude-code-arcane install mobile+agile+clickup+testing
 
 # Secure backend with docs
-npx arcane install backend-ts+security+docs+database
+npx claude-code-arcane install backend-ts+security+docs+database
 
 # AI/ML project with data pipelines
-npx arcane install backend-go+ai+infra
+npx claude-code-arcane install backend-go+ai+infra
 
 # SaaS with full marketing stack
-npx arcane install backend-ts+marketing+business+finance
+npx claude-code-arcane install backend-ts+marketing+business+finance
 
 # Regulated medical device
-npx arcane install backend-ts+regulatory+security+testing
+npx claude-code-arcane install backend-ts+regulatory+security+testing
 
 # With status bar
-npx arcane install backend-ts+agile+statusline
+npx claude-code-arcane install backend-ts+agile+statusline
 ```
 
 ---
 
 ## What Gets Installed
 
-When you run `npx arcane install`, the following structure is created inside your project:
+When you run `npx claude-code-arcane install`, the following structure is created inside your project:
 
 ```
 my-project/.claude/
@@ -471,7 +476,7 @@ Once installed, manage the installation from within a Claude Code session:
 
 ### "Profile not found" error
 
-Check available profiles with `npx arcane list`. Profile names are exact: `unity-dev`, not `unity`.
+Check available profiles with `npx claude-code-arcane list`. Profile names are exact: `unity-dev`, not `unity`.
 
 ### Skills show as "WARN: not found"
 
@@ -511,15 +516,15 @@ Yes. The `.claude/` directory is part of your project. It persists until you run
 
 ### Can I add a single skill without changing profiles?
 
-Yes. Use `npx arcane add <skill-name>` to add individual skills. Use `npx arcane remove <skill-name>` to remove them. Changes are tracked in the manifest.
+Yes. Use `npx claude-code-arcane add <skill-name>` to add individual skills. Use `npx claude-code-arcane remove <skill-name>` to remove them. Changes are tracked in the manifest.
 
 ### How do I update Arcane?
 
 ```bash
-npx arcane update
+npx claude-code-arcane update
 ```
 
-Since Arcane runs via `npx`, you always get the latest version. Use `npx arcane update` to check if a newer version is available.
+Since Arcane runs via `npx`, you always get the latest version. Use `npx claude-code-arcane update` to check if a newer version is available.
 
 ### What's the difference between `+clickup` and `+jira`?
 
@@ -536,7 +541,7 @@ Yes, and it's recommended. This way everyone on the team gets the same Claude Co
 
 ### How many tokens does a profile consume?
 
-Each skill adds ~30-100 tokens to the system prompt. A typical base profile (20-30 skills) adds ~1-2k tokens. The core profile adds ~500 tokens. Compare that to loading all 375 skills, which is why selective deploy matters.
+Each skill adds ~30-100 tokens to the system prompt. A typical base profile (20-30 skills) adds ~1-2k tokens. The core profile adds ~500 tokens. Compare that to loading all 397 skills, which is why selective deploy matters.
 
 ### Why replace instead of merge on install?
 

package/docs/agent-hierarchy.md

@@ -21,7 +21,7 @@ Cada división sigue una jerarquía de estudio real con 3 niveles de autoridad:
 
 ---
 
-## Roster Completo (135 Agentes)
+## Roster Completo (143 Agentes)
 
 ### División 1 — Game Development Studio (44)
 
@@ -121,6 +121,26 @@ Cada división sigue una jerarquía de estudio real con 3 niveles de autoridad:
 
 **Specialists (2):** `quality-manager`, `compliance-officer`
 
+### División 14 — Career & Job Hunt (4)
+
+**Leads (1):** `career-strategist`
+
+**Specialists (3):** `cv-reviewer`, `hiring-manager`, `mock-interviewer`
+
+Los cuatro son **read-only por diseño, no por precaución**. Existen porque la búsqueda laboral tiene lecturas que solo sirven con contexto fresco: el que escribió el CV no lo puede revisar, y el que preparó las respuestas STAR no puede simular la entrevista. Un agente que hereda ese contexto no agrega nada.
+
+Se lanzan desde los skills del perfil `+job-hunt`, no entre ellos: `cv-reviewer` y `hiring-manager` son lentes independientes sobre la misma postulación y corren **en paralelo**.
+
+### División 15 — Freelance (4)
+
+**Leads (1):** `pipeline-strategist`
+
+**Specialists (3):** `client-screener`, `proposal-reviewer`, `discovery-call`
+
+Read-only, igual que la División 14, y por la misma razón de fondo con una vuelta más: acá el que redacta no solo está convencido de su propio texto, además **está gastando plata en enviarlo**. `client-screener` es explícitamente adversarial - arranca de la hipótesis de que el trabajo es un problema, porque el sesgo del usuario apunta al otro lado.
+
+Se lanzan desde los skills de `+freelance`. `client-screener` y `proposal-reviewer` corren **en paralelo**: uno juzga al cliente, el otro la propuesta.
+
 ---
 
 ## Reglas de Delegación

package/docs/presentations/build_arcane_deck.py

@@ -152,7 +152,7 @@ txt(s, 0.78, 2.0, 11.7, 1.0,
 rect(s, 0.78, 3.25, 11.7, 1.5, RGBColor(0x14, 0x11, 0x33), radius=True, line=VIOLET, line_w=1.5)
 txt(s, 1.1, 3.45, 11, 0.4, [[("terminal", 11, MUTED, False)]])
 txt(s, 1.1, 3.85, 11, 0.7,
-    [[("$ ", 26, CYAN, True), ("npx arcane install ", 26, WHITE, True),
+    [[("$ ", 26, CYAN, True), ("npx claude-code-arcane install ", 26, WHITE, True),
       ("backend-ts", 26, GREEN, True), ("+agile", 26, AMBER, True), ("+testing", 26, AMBER, True)]])
 
 cols = [("backend-ts", "base", GREEN), ("+agile", "addon", AMBER), ("+testing", "addon", AMBER)]
@@ -301,7 +301,7 @@ txt(s, 0.78, 5.7, 11.7, 0.55,
     [[("Configuracion de IA, modular y versionada — un comando para empezar.", 19, WHITE, True)]],
     align=PP_ALIGN.CENTER)
 txt(s, 0.78, 6.25, 11.7, 0.5,
-    [[("npx arcane install <profile>", 22, WHITE, True)]], align=PP_ALIGN.CENTER)
+    [[("npx claude-code-arcane install <profile>", 22, WHITE, True)]], align=PP_ALIGN.CENTER)
 badge(s, 8); footer(s)
 
 out = os.path.join(os.path.dirname(os.path.abspath(__file__)), "arcane-overview.pptx")

package/docs/presentations/build_arcane_deck_12.py

@@ -172,7 +172,7 @@ txt(s, 0.78, 1.95, 11.7, 0.9,
 rect(s, 0.78, 3.05, 11.7, 1.45, CODEBG, radius=True, line=VIOLET, line_w=1.5)
 txt(s, 1.1, 3.22, 11, 0.35, [[("terminal", 11, MUTED, False)]], font=MONO)
 txt(s, 1.1, 3.62, 11, 0.7,
-    [[("$ ", 24, CYAN, True), ("npx arcane install ", 24, WHITE, True),
+    [[("$ ", 24, CYAN, True), ("npx claude-code-arcane install ", 24, WHITE, True),
       ("backend-ts", 24, GREEN, True), ("+agile", 24, AMBER, True), ("+testing", 24, AMBER, True)]], font=MONO)
 cols = [("backend-ts", "base", GREEN), ("+agile", "addon", AMBER), ("+testing", "addon", AMBER)]
 cx = 0.78
@@ -390,7 +390,7 @@ rect(s, 0.78, 5.25, 11.7, 1.45, VIOLET, radius=True)
 txt(s, 0.78, 5.4, 11.7, 0.5,
     [[("Configuracion de IA, modular y versionada — un comando para empezar.", 17, WHITE, True)]],
     align=PP_ALIGN.CENTER)
-txt(s, 0.78, 5.95, 11.7, 0.5, [[("npx arcane install backend-ts+agile", 21, WHITE, True)]],
+txt(s, 0.78, 5.95, 11.7, 0.5, [[("npx claude-code-arcane install backend-ts+agile", 21, WHITE, True)]],
     align=PP_ALIGN.CENTER, font=MONO)
 
 out = os.path.join(os.path.dirname(os.path.abspath(__file__)), "arcane-overview-12.pptx")

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "claude-code-arcane",
-  "version": "2.1.0",
-  "description": "Skills, agents, hooks and rules for Claude Code — installable via npx arcane",
+  "version": "2.3.0",
+  "description": "Skills, agents, hooks and rules for Claude Code — installable via npx claude-code-arcane",
   "type": "module",
   "bin": {
     "arcane": "./dist/cli.js"

package/profiles/audio.yaml

@@ -0,0 +1,45 @@
+name: audio
+description: "Game Audio — direccion sonora, composicion, sound design, middleware, VO y QA"
+type: base
+
+skills:
+  - audio-bible
+  - audio-spec
+  - music-composition
+  - adaptive-music
+  - midi-compose
+  - sfx-design
+  - procedural-audio
+  - ui-sound-design
+  - spatial-audio
+  - audio-mix
+  - middleware-integration
+  - voice-pipeline
+  - audio-audit
+
+rules:
+  universal:
+    []
+  gamedev:
+    - audio-code
+
+agents:
+  - audio
+
+permissions:
+  allow:
+    - "Bash(python *)"
+    - "Bash(python3 *)"
+    - "Bash(git status*)"
+    - "Bash(git add*)"
+    - "Bash(git commit*)"
+    - "Bash(git diff*)"
+    - "Bash(git log*)"
+    - "Bash(ls *)"
+    - "Bash(find *)"
+    - "Read(*)"
+    - "Glob(*)"
+    - "Grep(*)"
+  deny:
+    - "Bash(rm -rf *)"
+    - "Bash(git push --force*)"

package/profiles/freelance.yaml

@@ -0,0 +1,43 @@
+name: freelance
+description: "Freelance — conseguir proyectos como freelancer y ejecutarlos: scan de fuentes publicas sin API key con dedup y scoring, busqueda en los marketplaces (Upwork, Workana) via WebSearch, inteligencia de tarifas de mercado, screening de riesgo del cliente, perfil de plataforma, propuestas con cotizacion sobre piso de tarifa neto, contratos y SOWs, kickoff con validacion de horas contra lo cotizado, registro de horas y change orders, pipeline con costo de adquisicion y utilizacion, y 4 agentes de contexto fresco (review de propuesta, screener adversarial, discovery call, estratega de pipeline)"
+type: addon
+
+skills:
+  # Nucleo del perfil
+  - freelance-hunt
+  - freelance-profile
+  - freelance-scan
+  - client-screen
+  - freelance-proposal
+  - freelance-pipeline
+  - freelance-kickoff
+  - freelance-deliver
+  # Compartidas con +job-hunt (una sola fuente de verdad del perfil profesional)
+  - master-profile
+  - portfolio-site
+  - cold-outreach
+  - job-outcome
+  - career-registry
+  # Compartidas con +business y +agile
+  - contract-and-proposal-writer
+  - estimate
+
+rules:
+  universal:
+    - freelance-guardrails
+  gamedev:
+    []
+
+agents:
+  - freelance
+
+permissions:
+  allow:
+    - "Bash(python *import_history.py*)"
+    - "Bash(python3 *import_history.py*)"
+    - "Bash(python *career_registry.py*)"
+    - "Bash(python3 *career_registry.py*)"
+    - "Bash(python *freelance_search.py*)"
+    - "Bash(python3 *freelance_search.py*)"
+  deny:
+    []

package/profiles/job-hunt.yaml

@@ -1,5 +1,5 @@
 name: job-hunt
-description: "Job Hunt — busqueda laboral end-to-end: perfil maestro, CV ATS con verificacion, scraping de ofertas con dedup, pipeline de postulacion, LinkedIn, portfolio, cover letters, outreach a recruiters, scoring de ofertas, gaps/upskill y prep de entrevistas"
+description: "Job Hunt — busqueda laboral end-to-end: perfil maestro, CV ATS con verificacion, scraping de ofertas con dedup, pipeline de postulacion, LinkedIn, portfolio, cover letters, outreach a recruiters, scoring de ofertas, gaps/upskill, prep de entrevistas y 4 agentes de contexto fresco (review de CV, hiring manager, mock interview, diagnostico del embudo)"
 type: addon
 
 skills:
@@ -13,6 +13,7 @@ skills:
   - job-scrape
   - job-aplicar
   - job-outcome
+  - career-registry
   - job-upskill
   - cover-letter
   - cold-outreach
@@ -27,10 +28,12 @@ rules:
     []
 
 agents:
-  []
+  - career
 
 permissions:
   allow:
+    - "Bash(python *career_registry.py*)"
+    - "Bash(python3 *career_registry.py*)"
     - "Bash(python *cv_export.py*)"
     - "Bash(python3 *cv_export.py*)"
     - "Bash(python *verify_pdf.py*)"

package/rules/drafter-reviewer.md

@@ -9,14 +9,19 @@ Las rutas son relativas al career workspace (`./career-workspace/` o env `CAREER
 - Al terminar el borrador de un CV custom (flujo cv-tailor) o de una cover / mensaje de aplicación (flujo cover-letter) destinado a una postulación concreta.
 - NO aplica a ediciones menores de un CV ya revisado (typos, cambiar una fecha) ni a los CVs base de `02-CVs/` fuera de una postulación.
 
+Quién la ejecuta: `/job-aplicar` (paso 7, obligatorio), y `/cv-tailor` y `/cover-letter` cuando se corren sueltos. Los tres declaran `Task` en `allowed-tools` justamente para poder cumplirla - un skill sin `Task` no puede aplicar esta regla, y ahí la regla sería solo una intención.
+
 ## El paso reviewer
 
-Lanzar UN agente `general-purpose` de contexto fresco vía el Agent tool, con este contenido inline en el prompt (para que no dependa de leer archivos de la conversación):
+Lanzar UN agente **`cv-reviewer`** de contexto fresco vía el Agent tool. El agente ya trae la persona, el límite de lectura y el contrato de salida; el prompt solo tiene que aportar lo que el agente no puede saber:
 
 1. El texto completo de la job description.
 2. El borrador del CV y/o cover, verbatim.
-3. Instrucción de lectura acotada: solo puede leer `01-Perfiles/<perfil usado>.md` del workspace. NO debe leer los templates ni el resto del workspace - critica contenido, no estructura.
-4. Instrucción de research: búsqueda web breve sobre la empresa (misión, producto, noticias recientes, cultura) para detectar ángulos no aprovechados.
+3. Cuál es el perfil usado, para que sepa qué archivo de `01-Perfiles/` puede leer.
+
+Va inline en el prompt para que no dependa de leer archivos de la conversación.
+
+Si el agente `cv-reviewer` no está instalado (perfil `+job-hunt` sin su directorio de agentes), usar un `general-purpose` y pasarle en el prompt las cuatro restricciones: lectura acotada a `01-Perfiles/<perfil usado>.md`, prohibido leer templates y el resto del workspace, research web breve de la empresa, y el contrato de salida de abajo.
 
 El reviewer devuelve dos partes:
 
@@ -27,6 +32,14 @@ El reviewer devuelve dos partes:
   - Bullets que se pueden reformular como logro medible
   - Tono / estilo (registro, longitud, muletillas)
 
+## Segunda lente (opcional): `hiring-manager`
+
+`cv-reviewer` contesta "¿pasa el filtro?". Un CV puede pasar con match del 85% y morir igual en el escritorio de quien contrata, por una razón distinta: **no hay evidencia de que la persona ya hizo el trabajo**.
+
+Cuándo vale el segundo agente: postulación que importa, rol senior, o racha de rechazos post-CV. Se lanza **en paralelo** con `cv-reviewer` (no en cadena: son lentes independientes y encadenarlos solo suma latencia). Devuelve veredicto, evidencia faltante y las 3 preguntas que haría, que además son material de `/interview-prep`.
+
+No es obligatorio. Para una aplicación de rutina, `cv-reviewer` solo alcanza.
+
 ## Reglas de aplicación del feedback
 
 - **Una sola ronda.** El drafter aplica la Parte A, incorpora de la Parte B lo que corresponda, y sigue. Sin ida y vuelta iterativo.