Backend implementation specialist. Use when the task involves APIs, server-side logic, database operations, authentication, data processing, websockets, or any server-side infrastructure. Focuses on robustness, simplicity, and self-audited correctness.
Frontend implementation specialist. Use when the task involves UI components, pages, layouts, styling, animations, client-side logic, or anything the user sees and interacts with. Focuses on UX quality, accessibility, and cross-device reliability.
Central coordinator that decomposes tasks, delegates to specialist agents, manages feedback loops between implementers and reviewers, and ensures all agents are satisfied before returning control. Use when a task spans multiple agents, requires coordination between specialists, or when the user wants hands-off…
Strategic planner that validates and shapes ideas into actionable specs before implementation. Use when a brainstorm or feature idea needs to be pressure-tested, scoped, and turned into a clear specification with success criteria and UATs. Sits between brainstorming and technical planning.
Integration and compliance reviewer. Use after implementation agents finish to verify that pieces fit together, catch what authors missed, and confirm the implementation matches the spec. Not a style checker; a correctness and integration verifier.
Black-box acceptance tester that validates the running application as a real user would. Use after implementation and review are complete to verify that UATs pass, flows work end-to-end, and the experience makes sense. Does not read code.
Agents are isolated Claude instances you create and configure for specialised tasks. They come in two forms: subagents that operate within your session, and agent teams that coordinate across separate sessions.