Prototype

prototype

Throwaway code that answers a single design or logic question through an interactive prototype.

mattpocock/skills·885.7Kinstalls276.6Kstars

SKILL.md

Full skill instructions

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. 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.
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.
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 implementation issue. Capture the answer too — the verdict and the question it settled — in the issue or a commit. The main branch keeps only the validated decision.

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/mattpocock/skills --skill prototype

View on GitHub

prototype

grill-me
Relentless interviewing skill that stress-tests plans and designs through systematic questioning.
1.3M installs
grill-with-docs
Relentless design interrogation that stress-tests plans against your domain model and sharpens terminology inline.
1.1M installs
improve-codebase-architecture
Analyze codebases for architectural friction and propose module-deepening refactors as testability improvements.
1M installs
tdd
Test-driven development with vertical slices, behavior-focused tests, and incremental red-green-refactor cycles.
1M installs

More skills from mattpocock

mattpocock/skills

setup-matt-pocock-skills

Configuration scaffold for engineering skills to locate issue tracker, triage labels, and domain documentation.

276.6K 941.3K

View

mattpocock/skills

handoff

Summarize conversations into handoff documents for seamless agent-to-agent transitions.

276.6K 919.3K

View

mattpocock/skills

triage

State machine-driven issue triage with role-based workflow management and agent brief generation.

276.6K 889.1K

View

mattpocock/skills

grilling

Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.

276.6K 836.2K

View

mattpocock/skills

domain-modeling

Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.

276.6K 756.1K

View

mattpocock/skills

teach

Teach the user a new skill or concept, within this workspace.

276.6K 755.9K

View

mattpocock/skills

codebase-design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

276.6K 733.2K

View

mattpocock/skills

diagnosing-bugs

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

276.6K 717.4K

View

mattpocock/skills

code-review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".

276.6K 668.7K

View

mattpocock/skills

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

276.6K 661.5K

View

mattpocock/skills

implement

Implement a piece of work based on a spec or set of tickets.

276.6K 661.1K

View

mattpocock/skills

wayfinder

Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.

276.6K 611.4K

View