| name | brainstorming |
| description | Diverge then converge on ideas before building. Use when the user wants options, concepts, directions, or "ideas for X" — generates multiple distinct approaches, pressure-tests them against goals/constraints, then recommends one with rationale. Pairs well with ui-ux-pro-max and goal. |
Brainstorming
Generate a real spread of options, stress-test them, and converge on a
recommendation — instead of jumping to the first idea.
When to use
Invoke when the user asks for ideas, concepts, directions, alternatives, or
"how could we do X". Especially before committing to a design or build.
Method
1. Frame
State the objective in one line and list the hard constraints (audience,
brand, tech, performance, time). Ideas are judged against these, not taste
alone.
2. Diverge (quantity first)
Produce at least 4–6 genuinely distinct options — not variations of one.
Push for range: safe → bold, literal → lateral. For each, give:
- a short name,
- the core idea in 1–2 sentences,
- why it could work.
Do not self-censor here; weird ideas often sharpen the good one.
3. Pressure-test (converge)
Score each option against the constraints. For the top contenders, name:
- Strengths (what it nails),
- Risks/cost (effort, performance, accessibility, maintenance),
- Fit with the stated goal and brand.
Kill options that lose; say why.
4. Recommend
Pick ONE (or a small combo) and justify it in terms of the objective and
constraints. Offer a clear runner-up. Note what you'd validate next.
Principles
- Distinct beats numerous-but-samey. 4 real directions > 10 tweaks.
- Tie every idea back to the user's goal and audience.
- Be honest about trade-offs; a recommendation without risks is a sales pitch.
- When the choice materially changes the work, surface it to the user (e.g.
via AskUserQuestion) rather than guessing.
Output shape
- Objective + constraints
- Options (named, with the why)
- Trade-off comparison of the finalists
- Recommendation + runner-up + next step to validate
