brainstorming

# Brainstorming Ideas Into Designs ## Purpose Turn raw ideas into **clear, validated designs** through structured dialogue **before any implementation begins**. Prevent premature coding, hidden assumptions, and misaligned solutions. **You must NOT implement, code, or modify files while this skill is active.** ## Process ### 1. Understand Current Context Before asking questions: - Review the current project state (files, docs, prior decisions) - Identify what already exists vs. what is proposed - Note implicit constraints ### 2. Clarify the Idea (One Question at a Time) - Ask **one question per message** - Prefer **multiple-choice questions** when possible - Focus on: purpose, constraints, success criteria, and explicit non-goals - For algorithms/math: clarify accuracy requirements, edge cases, expected inputs ### 3. Technical Requirements Explicitly clarify or propose assumptions for: - **Performance**: allocation budget, runtime targets, real-time constraints - **Accuracy**: numerical precision, validation references (papers, test cases) - **Differentiability**: which AD backends must work, what needs to be differentiable - **Composability**: how it integrates with existing types and interfaces - **Scope**: what is explicitly out of scope If the user is unsure, propose reasonable defaults and mark them as **assumptions**. ### 4. Understanding Lock (Hard Gate) Before proposing any design, provide a summary covering: - What is being built and why - Key constraints...