
Generate a project-level CLAUDE.md from stack detection and user-selected rule categories. Use when starting a new project, onboarding a repo, or when the user says "seed claude.md", "create project rules", "set up CLAUDE.md", "configure this project for me", or wants to establish coding conventions.
Assesses team fitness and composes agent teams. Use when "set up a team", "team for this", "should I use agents", "design a team", "how many agents", "agent team".
Turn rough ideas into clear work orders before planning or building. Use when request is vague like "add a button", "make it better", "fix the thing". Triggers on ambiguous or underspecified requests. Produces a brief with scope, acceptance criteria, and stop conditions.
--- name: shape description: Resolves technical HOW decisions — architecture choices, technology selection, and design patterns — from a defined spec or intent. Distinct from hope:intent (which clarifies WHAT to build): shape starts when the goal is clear but the technical path is not. Use when: needing an implementation roadmap, choosing between architectural approaches, or resolving design trade-offs before coding. Triggers on: "shape this", "architecture for X", "how should I build", "system
--- name: consult description: Simulates expert panels, compares documented positions across thought leaders, and synthesizes anonymous recommendations grouped by concern. Invoke when facing design tradeoffs, architecture decisions, repeated failure modes, or domain questions where multiple perspectives would reduce decision regret. Triggers on: expert names, "panel", "debate", "what would [X] say", "stuck on", style requests. --- Simulate expert perspectives by reasoning from documented positi