ROUTING
01Agent
Highest-priority signal wins. Read top-to-bottom; stop at the first match.
A Claude Code configuration kit that makes the assistant behave like a senior engineering team instead of an eager junior.
Agent
Highest-priority signal wins. Read top-to-bottom; stop at the first match.
Agent
Use for localized bugs, runtime errors, failing tests, console errors, regressions, or broken behavior where root cause can be isolated. Escalate protected areas.
Agent
Use for database schema changes, data modeling, ORM queries, indexes, constraints, transactions, and migration deployment safety (destructive changes, rollback, backward compatibility, production risk, deployment order, backups). Read-only — produces a plan, waits for approval; never executes migrations.
Agent
Use when a project's visual design has to be decided rather than matched — a first page or screen with no DESIGN-SPEC.md, a redesign, a brief with references or brand assets, or "make it look like its own product". Produces the direction, the tokens and the signature moment; hands construction to ui-fixer.
Agent
CI/CD, Docker, Terraform, Kubernetes, and infrastructure change guardian — plans first, requires explicit approval for destructive or production-affecting changes. Use for: GitHub Actions, GitLab CI, K8s manifests, Helm charts, docker-compose, deployment scripts.
Agent
Use for slow queries, N+1, bundle size, caching, render loops, memory leaks, latency, and expensive computations.
Agent
Use for auth, authorization, payment, billing, input validation, secrets, injection risks, session/token handling, rate limiting, sensitive data, and security reviews — plus tool-driven dependency, secret, SAST, and container/filesystem scans. Read-only by default — delegates implementation to senior-engineer.
Agent
Use for scoped medium feature implementation or safe refactors requiring multiple files, tests, and existing project patterns. Do not use for critical protected changes without a plan.
Agent
Use for low-risk frontend-only UI changes — modals, buttons, layout, responsive styling, Tailwind/CSS, component polish, new pages, new screens. Do not use for backend, auth, payment, database, migrations, secrets, or CI.