prototypelisted

# Prototype: $ARGUMENTS Build a **throwaway** prototype to make a fuzzy design concrete enough to react to. You learn fastest by seeing options side by side and poking at them — not by arguing about them in the abstract. The only product is a **decision**; the code is disposable. `$ARGUMENTS` is the design question to explore. If empty, ask what to prototype, then stop. This skill carries only invariant workflow logic. Run commands, where source lives, the UI stack, and routing come from `.claude/PROJECT.md`. Prototype code lives in a **clearly throwaway location** and is **never** promoted into production — the real version is built fresh through the pipeline. --- ## Phase 0 — Load profile 1. Read `.claude/PROJECT.md` — **Commands** (`run`), **Stack** (UI framework, language), and **Architecture** (where the app's routes/entry points live, so the prototype can attach without polluting real source). If missing or `TEMPLATE`, fall back to the root `CLAUDE.md` (always in context) when it carries those facts — proceed on it, noting you're running without a kit profile. Only if *neither* has them, **STOP** → `/bootstrap` first. 2. If `CONTEXT.md` exists, read it so the prototype uses the project's real domain vocabulary. --- ## Phase 1 — Frame & choose a mode Pin down the question, then pick the mode that answers it: | Mode | Use when the open question is about… | Build | |------|--------------------------------------|-------| | **Logic** | state, business r