rite-prototypelisted

# /rite-prototype: answer one question with throwaway code A prototype is throwaway code for exactly one question. Choose its shape from that question. ## 0. Read core rules Read `.claude/skills/devrites-lib/reference/standards/core.md` first: the operating rules and the "capture the answer" persistence discipline apply even to throwaway code. The other rule files load on demand. ## 1. Name the question If the user did not give the question explicitly, ask **one** short question to pin it down. Examples that count as "the question": - "Does this reducer correctly model add / undo / re-add of the same item?" - "Which of these three settings layouts feels right?" - "Will the proposed state machine deadlock when X overlaps Y?" A vague request such as "explore this feature" is not enough. Ask once for a specific question. ## 2. Pick the branch Read the user's prompt and surrounding code, then choose one branch: | Question shape | Branch | Artifact | |---|---|---| | "Does this **logic / state / data model** behave right?" | **Logic** | Smallest runnable harness (terminal script / REPL / mini node or python file) that pushes the model through the hard cases. | | "What should this **look like / which UX wins**?" | **UI** | 2-4 **radically different** UI variations on a single route, switchable via a query param + a small floating selector bar. | If genuinely ambiguous and the user is AFK: pick by the surrounding code (backend module → Logic; page / component → UI) and sta