Engineer production-ready code with AI using proven practices
Build a throwaway prototype - a terminal app for logic questions or toggleable UI variations - that answers one question, then gets deleted.
Maintainer of this project? Claim this page to edit the listing.
1.0.1Add to Favorites
Why it matters
Help developers build maintainable, well-architected applications with AI coding agents by providing composable skills that enforce software engineering fundamentals like alignment through grilling sessions, shared language documentation, test-driven development, and continuous design improvement.
Outcomes
What it gets done
Align on requirements before coding by running grilling sessions that ask detailed questions and build shared vocabulary documents
Write better code through test-driven development loops that enforce red-green-refactor cycles with automated feedback
Maintain clean architecture by analyzing module design, identifying complexity, and refactoring toward simpler interfaces
Debug systematically using structured diagnostic workflows that guide agents through proper troubleshooting steps
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/ag-prototype | bash Overview
Prototype
Builds throwaway prototype code - a terminal app for logic questions or toggleable UI variations for design questions - that answers one question and is then deleted. Use to flesh out a design or state model before committing to it, then capture only the answer and delete the scaffolding.
What it does
Prototype builds throwaway code whose sole job is answering one question, with the question deciding the shape. Two branches: "does this logic or state model feel right?" gets 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?" gets several radically different UI variations on a single route, switchable via a URL search param and a floating bottom bar. Getting the branch wrong wastes the whole prototype, so if the question is genuinely ambiguous and the user isn't reachable, it defaults by what the surrounding code is - a backend module gets the logic branch, a page or component gets the UI branch - and states that assumption at the top of the prototype.
When to use - and when NOT to
Use it to flesh out a design before committing to it: a runnable terminal app for state or business-logic questions, or several radically different UI variations toggleable from one route. Both branches share the same discipline: throwaway from day one and clearly marked as such, located next to the module or page it's prototyping so context is obvious, runnable with a single command matching the project's existing task runner, no persistence by default (state lives in memory since persistence is what's being checked, not depended on - a database question gets a scratch DB or a file explicitly named as disposable), and no polish: no tests, no abstractions, only the error handling needed to keep it runnable.
Inputs and outputs
Every action in the logic branch or every variant switch in the UI branch must surface the full relevant state by printing or rendering it, so the user can see exactly what changed. When the prototype has answered its question, it gets deleted or the validated decision gets folded into real code - it should never be left rotting in the repo.
LOGIC.md -> tiny terminal app, state machine, print state after every action
UI.md -> radically different variations, one route, URL param switch
Integrations
UI-branch prototypes obey whatever routing convention the project already uses rather than inventing a new top-level structure; logic-branch prototypes run via the project's existing task runner (pnpm, python, bun, or equivalent).
Who it's for
Developers who need a fast, disposable way to validate a state model or compare UI directions before writing production code - and who capture only the answer, not the scaffolding, in a commit message, ADR, issue, or a NOTES.md next to the prototype before deleting it.
Source README
Prototype
When to Use
Use when this workflow matches the user request: Build a throwaway prototype to flesh out a design - a runnable terminal app for state/business-logic questions, or several radically different UI variations toggleable from one route.
Source: mattpocock/skills (MIT).
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. 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. 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
- 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.
- One command to run. Whatever the project's existing task runner supports -
pnpm <name>,python <path>,bun <path>, etc. The user must be able to start it without thinking. - 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.
- Skip the polish. No tests, no error handling beyond what makes the prototype runnable, no abstractions. The point is to learn something fast and then delete it.
- 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.
- Delete or absorb when done. When the prototype has answered its question, either delete it or fold the validated decision into the real code - don't leave it rotting in the repo.
When done
The answer is the only thing worth keeping from a prototype. Capture it somewhere durable (commit message, ADR, issue, or a NOTES.md next to the prototype) along with the question it was answering. If the user is around, that capture is a quick conversation; if not, leave the placeholder so they (or you, on the next pass) can fill in the verdict before deleting the prototype.
Limitations
- Requires the upstream tool, account, API key, or local setup when the workflow names one.
- Does not authorize destructive, production, paid, or external-message actions without explicit user approval.
- Validate generated artifacts or recommendations against the user's real sources before treating them as final.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.