brainstormlisted

# Brainstorm Turn ideas into designs through collaborative dialogue before implementation. ## Process ### Phase 1: Understand the Idea Check project context first, then ask questions one at a time: 1. **Gather context** - check files, docs, recent commits relevant to the idea 2. **Ask questions one at a time** - prefer multiple choice when possible 3. **Focus on**: purpose, constraints, success criteria, integration points Do not overwhelm with multiple questions. One question per message. If a topic needs more exploration, break it into multiple questions. ### Phase 2: Explore Approaches Once the problem is understood: 1. **Compare 2-3 approaches when several are credible** and explain their trade-offs 2. **When one approach is clearly supported**, explain why alternatives do not fit instead of inventing options 3. **Lead with the recommendation** and present it conversationally, not as a formal document When comparing approaches, put each option label on its own plain-text line in the form `Option A: Name (recommended)` or `Option B: Name`, followed by bullets for how it works and its trade-offs. Do not prefix option labels with Markdown heading markers, bullets, numbering, backticks, or emphasis markers, and do not wrap the response in a code fence. The labels must remain readable without Markdown rendering. ### Phase 3: Present Design After approach is selected: 1. **Break design into sections** of 200-300 words each 2. **Ask after each section** whether it l