# Reference: Agents The specialized agents available to route work to. Generated from the agent registry. _37 specialized agents._ | Agent | When to use it | | --- | --- | | `_TEMPLATE` | | | `accessibility` | Accessibility (a11y) specialist — WCAG compliance, semantics, keyboard navigation, screen-reader support, color contrast, focus management. Use when building/reviewing UI to ensure it's usable by everyone. (design-team squad) | | `agent-architect` | Interviews the developer through the canonical INTERVIEW_QUESTIONS list, validates the result against the Agent Blueprint schema, and produces the YAML blueprint that drives the rest of the agent-forge pipeline. Touches templates/contextkit/squads/agent-forge/lib/architect.mjs (INTERVIEW_QUESTIONS + validateBlueprint + fillDefaults). (agent-forge squad) | | `architect` | Cross-cutting design specialist. Use for decisions that span multiple modules — choosing a pattern, designing a subsystem, planning a migration, or whether to adopt a dependency (fit, maintenance, lock-in) — BEFORE code is written. (A dependency's security/supply-chain risk is the security agent's call.) Pairs with /new-adr and /simulate-impact. (devteam squad) | | `code-reviewer` | Pre-merge code review specialist. Use proactively before opening a PR, after a meaningful diff, or to audit a branch against the project constitution in CLAUDE.md. Focuses on style, structure, naming, SRP, and the immutable rules. (devteam squad) | | `code-security` | Application-code & supply-chain security specialist (security-team). Use for the threat model of the code's OWN external surface — third-party integration code (API clients/SDKs, webhooks & callbacks, (de)serialization of external responses), dependency provenance/SBOM & license policy, and SAST/CodeQL triage. Pairs with security (AppSec lead) and infra-security (platform). (security-team) | | `context-keeper` | Specialist for the ContextDevKit platform itself. Use when the task touches session logs, ADRs, the glossary, slash commands, hooks (Claude Code or git), the SESSIONS/WORKSPACE indices, the config, or any change to the context system under contextkit/. (devteam squad) | | `conversion-strategist` | Conversion strategy & neurodesign specialist — interview-first market research, persuasive fold anatomy, benefit-led copy. Use when a landing page or public funnel needs the WHY behind each section (pain, anchoring, objections), before or alongside landing-architect's structural pass. Refuses invented social proof and dark patterns; asks the four strategy questions when the brief doesn't answer them. (design-team squad, ADR-0050) | | `devops` | DevOps / platform specialist — CI/CD, build & deploy, environments, secrets, infrastructure, observability, and release safety. Use for pipelines, deployments, env/secret config, and operational concerns. (ops-team squad) | | `domain-modeler` | Domain-modeling specialist for bounded contexts, language, invariants, aggregates, state authority, and transactional boundaries. Recommend for genuinely domain-heavy work; never make this specialist a write prerequisite. (devteam squad) | | `eval-designer` | Designs the eval set for a forged agent — extends the seed golden cases into the 10-50 the dev actually needs, expands red-team beyond the universal baseline (prompt injection / jailbreak / PII), and confirms the rubric + thresholds derived from the blueprint match the domain. Touches templates/contextkit/squads/agent-forge/lib/eval-designer.mjs + the package's evals/ dir. (agent-forge squad) | | `forge-orchestrator` | Runs the agent-forge pipeline end-to-end — invokes architect→router→prompt-engineer→tool-designer→(eval+governance Fase 3)→packager and refuses to ship if a gate fails. Use when a new Agent Package is requested (typically through /forge-new). Touches templates/contextkit/squads/agent-forge/lib/* and writes the package under agent-packages/@/. (agent-forge squad) | | `governance-officer` | Builds and validates the three governance pillars (cost / compliance / quality) + the fallback chain + the audit schema for a forged agent. Refuses to ship if any pillar is under-configured. Touches templates/contextkit/squads/agent-forge/lib/governance-officer.mjs + the package's governance/ dir. (agent-forge squad) | | `growth` | Growth specialist — activation, funnels, growth loops, experimentation, and the instrumentation that powers them. Use to find where users drop before they reach value, design the loop that compounds, or instrument an event taxonomy. Acquisition/SEO → seo-specialist; keeping users → retention. Audit-first; proposes, never dark-patterns. (growth-team squad) | | `implementation-engineer` | Senior implementation specialist for the smallest safe production diff, tests with behavior, explicit deviations, and evidence. Recommend for material code changes; never require agent presence or a packet before owner-authorized work. (devteam squad) | | `infra-security` | Infrastructure & cloud security specialist (security-team). Use for the threat model of the platform the app RUNS on — IaC (Terraform/k8s/CloudFormation) misconfig, IAM & least-privilege, network exposure, secrets management, container/runtime hardening, and CI/CD supply-chain. Pairs with devops (who builds it) and security (who owns AppSec). (security-team) | | `landing-architect` | Landing-page & high-conversion site specialist. Use when designing or reviewing a public-facing landing page, marketing site, or any indexable surface where conversion is the metric. Reads the landing-page playbook on every invocation and refuses the cookie-cutter "Lovable / v0 / Tailwind UI" pattern by default. Pairs with seo-specialist (mandatory indexability gate), ui-designer, ux-designer, accessibility, and /media-gen for non-stock imagery. (design-team squad) | | `model-router` | Routes the Agent Blueprint to a provider/model selection via the deterministic capability-matrix + decision-rules engine, writes the canonical Model Selection Rationale (structural facts only — never quality claims), and refuses to fabricate opinions. Touches templates/contextkit/squads/agent-forge/lib/router.mjs and router/{capability-matrix.json,decision-rules.json}. (agent-forge squad) | | `packager` | Assembles the final Agent Package (APF v1) directory — copies the template tree, stamps provenance + Model Selection Rationale, writes the per-provider files from prompt-engineer/tool-designer, and emits a versioned package under agent-packages/@/. Touches templates/contextkit/squads/agent-forge/lib/packager.mjs and templates/contextkit/squads/agent-forge/templates/agent-package/. (agent-forge squad) | | `privacy-lgpd` | LGPD risk-review specialist for Brazilian personal-data processing. Produces non-blocking, evidence-labeled guidance and routes binding legal questions to the DPO/legal team. (compliance-team squad) | | `product-owner` | Product specialist — turns goals into a prioritized roadmap and well-formed requirements (user stories + acceptance criteria), challenges scope, and owns the deepen-existing-features lens (maturing what already ships, not only greenfield ideation). Use for product decisions, prioritization, and writing what to build (not how). (product-team squad) | | `prompt-engineer` | Renders the canonical system prompt (prompts/system.canonical.md) to per-provider variants — Fase 1 ships Anthropic (XML, cache=ephemeral on Context) and OpenAI (Markdown with `# Role` / `## Section`), preserving the section map (Role/Context/Rules/Output/Examples). Touches templates/contextkit/squads/agent-forge/lib/prompt-gen.mjs. (agent-forge squad) | | `qa-e2e` | QA squad (Tier 2) — end-to-end specialist. Use when a critical user journey must be verified through the real UI/app (browser or mobile), or before a release that touches a key flow. Tests behavior as a user, not internals. | | `qa-fuzzer` | QA squad — adversarial / property-based test specialist. Dispatched by qa-orchestrator (not usually called directly). Attacks boundaries (parsers, validators, schemas, auth) with generated inputs and invariants. | | `qa-integration` | QA squad — integration test specialist. Dispatched by qa-orchestrator (not usually called directly). Tests across module/IO boundaries (HTTP, DB, queues, filesystem) against real adapters or high-fidelity fakes. | | `qa-orchestrator` | Single entry point for the QA squad (Level ≥ 4). Use for /test-plan, /scaffold-tests, /qa-signoff, or any "make sure this is well tested" request. Routes work to qa-unit / qa-integration / qa-fuzzer / qa-perf / qa-e2e and consolidates the result. Does NOT write tests itself. (Below L4, or for a quick in-flow regression, use test-engineer.) | | `qa-perf` | QA squad (Tier 2) — performance specialist. Use when a hot path is identified, a latency/throughput regression is suspected, or before scaling a critical flow. Benchmarks and profiles; does not micro-optimize on a hunch. | | `qa-unit` | QA squad — unit test specialist. Dispatched by qa-orchestrator (not usually called directly). Writes fast, isolated unit tests for pure functions and modules with mocked dependencies. | | `rag-designer` | Designs the retrieval-augmented-generation bundle for a forged agent — chunking, embedding model (multilingual vs english-only), index backend (pgvector/qdrant/faiss/pinecone), reranker, hybrid search, score thresholds. ONLY activated when `capabilities.rag: true`. Touches templates/contextkit/squads/agent-forge/lib/rag-designer.mjs + the package's rag/ dir. (agent-forge squad) | | `retention` | Retention specialist — cohort retention, churn (voluntary + involuntary), engagement loops, habit formation, lifecycle messaging, and resurrection. Use to read the retention curve, find why users leave, or design the loop that brings them back. Activation/acquisition → growth. Audit-first; refuses engagement-bait. (growth-team squad) | | `security` | Security specialist and lead of the security-team. Use for auth, secrets, credentials, tokens, crypto, input handling at trust boundaries, dependency & supply-chain risk (pinning, CVEs, licenses), infra/CI security, or reviewing a change for security impact. (security-team) | | `seo-specialist` | SEO + AISO specialist — indexability, structured data, Core Web Vitals, llms.txt, FAQ schema. Use when reviewing or building a public-facing landing page, marketing site, or any surface the user wants discoverable by Google AND by LLM answer engines (ChatGPT, Perplexity, Claude search, Gemini). Pairs with landing-architect and code-reviewer; refuses unindexable SPAs by default. (design-team squad) | | `test-engineer` | Testing specialist (devteam). The go-to for tests when the full QA squad isn't in play (Level < 4) or for a quick regression/coverage pass inside a dev flow. At Level ≥ 4, qa-orchestrator is the entry point and routes to the qa-* specialists. Adapts to the project's runner; never adds a second framework. (devteam squad) | | `tool-designer` | Converts the canonical JSON tool schemas (tools/schemas.canonical.json) into per-provider adapters — Fase 1 ships Anthropic (name/description/input_schema) and OpenAI (type:function wrapper), preserving descriptions, required fields, and the WHAT/WHEN/WHEN-NOT/EXAMPLE convention. Touches templates/contextkit/squads/agent-forge/lib/tool-gen.mjs. (agent-forge squad) | | `tracking-integrator` | Marketing-integration specialist — GTM container, tracking pixels, webhooks and lead-capture plumbing, consent-first by contract. Use when a public page needs analytics/ads instrumentation or a form needs to reach n8n/Make/CRM. Never wires a tracker to fire before cookie consent; ships pixel MODELS (commented templates), not live tags; pairs with privacy-lgpd. (design-team squad, ADR-0050) | | `ui-designer` | UI / visual & design-system specialist — layout, spacing, typography, color, components, responsive behaviour, and visual consistency via tokens. Use to design or polish the look of a screen and keep the design system coherent. (design-team squad) | | `ux-designer` | UX specialist — user flows, information architecture, interaction design, and usability. Use when designing or critiquing a screen/flow, reducing friction, or deciding how something should behave for the user. (design-team squad) |