prototypeslisted

# Prototypes — Divergent Prototype Fan-out (Design Directions) People can't describe what they want but **can judge when they see it** (unknown knowns). Origin: Four Design Directions / Mock before you wire — see skills/loop/references/talk-source.md. ## Iron Rules 1. **Never start final implementation.** Prototypes are tools to elicit reactions. 2. Options must have **clearly different design philosophies — not small variations**. ## Procedure 1. Parse target and count (default 4) from `$ARGUMENTS`; if empty, target = the thing last discussed, count 4. 2. Make options differ along these axes: - Information structure (what shows first) - User flow (operation order) - Visual density (dense vs whitespace) - Interaction mode (click/drag/keyboard/automatic) - Implementation complexity (simple-robust vs rich-complex) 3. Attach to each option: **name + one-line design philosophy + pros/cons + when it fits**. 4. After user reacts: convert chosen elements into an **explicit requirements list** — taste they couldn't verbalize (unknown knowns) becomes spec. 5. Proceed to real implementation only after the combined option is confirmed. ## Output Artifact tool if available → else `.unknowns/<YYYY-MM-DD>-prototypes-<slug>.html` → else markdown (also when HTML is unnatural: static document, API design); always echo the assembled reply in chat. Each option — and each element inside it — carries **steal / skip chips**; selections assemble into a **requirements lis