Saddss Vendored from mattpocock/skills under MIT.
Prototype
Throwaway code that answers one question. The question decides the shape.
Pick a branch
- Logic / state / routing policy? → LOGIC.md — interactive terminal TUI over a pure reducer/state machine
- Layout / UI? → UI.md — multiple variants on one route via
?variant=
If ambiguous: backend/routing module → LOGIC; page/component → UI. State the assumption at the top.
Rules (both branches)
- Clearly marked throwaway — name/path says prototype; live near the real module
- One command to run —
python …,pnpm …, Makefile target - No persistence by default — in-memory unless persistence is the question
- No polish — no tests, minimal error handling, no abstractions
- Surface state — print/render full state after every action
- Delete or absorb — capture answer in ADR/issue/NOTES.md, then delete shell
When done
The answer is what you keep. For routing/cache work, fold the validated reducer/policy into production code; delete the TUI.
Integration
| Before | After |
|---|---|
brainstorming, grill-with-docs |
Validated design |
| Prototype verdict | writing-plans or to-issues (inline decision snippets in issues OK) |
| Production impl | executing-plans + tdd |