prototypelisted

# prototype Get an idea out of the user's head and onto a screen in one round. Grayscale wireframes, not mockups. They exist to make a vague idea concrete enough to react to — then they get thrown away. Optimize for speed and cheapness over polish. A round that costs a lot of tokens and produces one beautiful screen has failed; a handful of rough screens the user can point at has worked. **Default: 3–5 options** — as many genuinely different structures as the brief supports, never fewer than 3. The user can force a number ("prototype 5 ways…"). **Never block on setup.** If this repo has no `.prototypes/kit.md`, use the gray defaults and add one line at the end: *"These are generic gray boxes — run `/prototype-setup` once and they'll match your house style."* Then move on. Don't ask about it, don't offer to run it. ## Step 1 — Get the brief **The conversation is the brief.** Before asking anything, read back over what's already been discussed — the feature, the problem, constraints, things already rejected. Proceed without questions when it pins down **the screen or flow** and **the one thing the user does on it**. State the brief back in one line and start. **If either is missing, interview — for the missing parts only.** Don't guess and don't generate a generic screen. Ask in **one message, at most four questions**, phrased for someone thinking out loud: - What are you picturing? Describe the screen as if it already existed. - What has to happen on it — the one thing