Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From nextjs-claude-code
Explore and validate feature design before writing specs. Uses Socratic questioning to refine the idea, compares 2-3 approaches with trade-offs, and produces a design summary approved by the user before handing off to /spec.
How this skill is triggered — by the user, by Claude, or both
Slash command
/nextjs-claude-code:brainstormThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Brainstorming always requires reasoning and design judgment → spawn `brainstormer` with `model: sonnet`.
Brainstorming always requires reasoning and design judgment → spawn brainstormer with model: sonnet.
Spawn brainstormer agent (sonnet) with the following prompt:
[HANDOFF]
TO: brainstormer (sonnet)
TASK: Brainstorm feature design based on the following description
DONE-WHEN:
- User has approved the final design summary
- A concise spec-ready summary has been presented
MUST-NOT:
- Write or modify any source code
- Write spec.md or design.md (that is /spec's job)
- Proceed past any phase without user approval
READS:
- spec/ARCHITECTURE.md
- spec/PROJECT.md
- spec/feature/ (scan existing features)
[/HANDOFF]
$ARGUMENTS
npx claudepluginhub byeongminlee/nextjs-claude-code --plugin nextjs-claude-codeRuns a Socratic design dialogue (3-5 AUQ rounds) to clarify ambiguous feature scope/UX, then writes a spec markdown file. Use before /plan feature when product intent needs validation.
Leads a conversational design workshop for new features: interviews one question at a time, explores approaches with trade-offs, and produces a focused spec.
Guides pre-implementation design exploration by asking one question at a time to produce a written spec before any code is written.