prototype · git:20260917.a589e3f · 2026-09-17 · sha256 a300b80d46b33edb
prototype git:20260917.a589e3fA
Immutable. This exact content never changes and is served at /api/v1/blob/a300b80d46b33edb.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3x77rgqvoin6nzm6/a300b80d46b33edb7986427b599fc0a085a72107de476895b3def3c029445b07.json
Then /plugin install prototype@markdownregistry-3x77rgqvoin6nzm6 in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
--- name: prototype description: Build a throwaway prototype to answer a design question. Use when the user wants to prototype, sanity-check a state model or business logic, or explore what a UI should look like. --- # Prototype A prototype is **throwaway code that answers a question**. The question decides the shape. ## Pick a branch Identify which question is being answered — from the user's prompt, the surrounding code, or by asking if the user is around: - **"Does this logic / state model feel right?"** → [LOGIC.md](LOGIC.md). Build a tiny interactive terminal app that pushes the state machine through cases that are hard to reason about on paper. - **"What should this look like?"** → [UI.md](UI.md). Generate several radically different UI variations on a single route, switchable via a URL search param and a floating bottom bar. The two branches produce very different artifacts — getting this wrong wastes the whole prototype. If the question is genuinely ambiguous and the user isn't reachable, default to whichever branch better matches the surrounding code (a backend module → logic; a page or component → UI) and state the assumption at the top of the prototype. ## Rules that apply to both 1. **Throwaway from day one, and clearly marked as such.** Locate the prototype code close to where it will actually be used (next to the module or page it's prototyping for) so context is obvious — but name it so a casual reader can see it's a prototype, not production. For throwaway UI routes, obey whatever routing convention the project already uses; don't invent a new top-level structure. 2. **One command to run.** Whatever the project's existing task runner supports — `make <name>`, `just <name>`, `python <path>`, `go run <path>`, etc. The user must be able to start it without thinking. 3. **No persistence by default.** State lives in memory. Persistence is the thing the prototype is _checking_, not something it should depend on. If the question explicitly involves a database, hit a scratch DB or a local file with a clear "PROTOTYPE — wipe me" name. 4. **Skip the polish.** No tests, no error handling beyond what makes the prototype _runnable_, no abstractions. The point is to learn something fast. 5. **Surface the state.** After every action (logic) or on every variant switch (UI), print or render the full relevant state so the user can see what changed. 6. **Capture it when done.** Fold any validated decision into the real code, then capture the prototype itself as a **primary source**: commit it to a throwaway branch, out of main, and leave a context pointer to that branch on the tracker issue driving the implementation. Capture the answer too (the verdict and the question it settled) in the issue or a commit. Main keeps only the validated decision.