explore-claude-code

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.

Builds new Claude Code agents with consistent structure, enforced standards, and project-aware configuration. Use when creating a new agent, when the user describes a specialised role they want delegated to, or when discussing team composition.

Builds new Claude Code skills with consistent structure, enforced standards, and project-aware configuration. Use when creating a new skill, when the user describes a workflow they want automated, or when the user says they want a new slash command.

Collaborative brainstorming mode for thinking through problems, ideas, and features before planning. Use when the user wants to discuss, explore ideas, or think through a problem without writing code.

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

What this skill does and when to use it. Claude reads this to decide relevance. Include keywords users would naturally say.

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 execution of a planned feature.

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.