Skip to content
Skills Library
Design & UX · Building & coding

prototype

/prototype

Build a bounded throwaway artifact to answer a design question. Use when the user wants to try a state model, compare interactions, or explore what a UI should look like before building it.

Repository
skills ↗
Licence
MIT
Last repository change
10.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
24
Scripts
0
HTML comments
0
URLs in SKILL.md
1
Deprecation

No signals detected. Repository changed on 10.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Build a bounded throwaway artifact to answer a design question. Use when the user wants to try a state model, compare interactions, or explore what a UI should look like before building it.

Original author description

Build a bounded throwaway artifact to answer a design question. Use when the user wants to try a state model, compare interactions, or explore what a UI should look like before building it.

How it works

  1. Frame the decision
  2. Build only the experiment
  3. Observe and conclude
  4. Provenance
Original SKILL.md headings · 45 lines, 544 words
SKILL.md preview
---
name: prototype
description: "Build a bounded throwaway artifact to answer a design question. Use when the user wants to try a state model, compare interactions, or explore what a UI should look like before building it."
license: MIT
metadata:
  source: "https://github.com/mattpocock/skills/blob/49dd158d1076134a641b33efb035946536778336/skills/engineering/prototype/SKILL.md"
  source-revision: "49dd158d1076134a641b33efb035946536778336"
  source-files: "skills/engineering/prototype/SKILL.md"
  local-changes: "Kept logic/UI branches and realistic consumer scenarios; made experience-first and alternatives optional; bounded effort and proof; removed branch, commit, push, server, and production-promotion mandates."
---

# Prototype

A prototype is **throwaway code that answers a question**. The question decides the artifact and the evidence.

## Frame the decision

Name one decision, the realistic cases it must expose, and the stopping point before building. Use the user's scope and effort limit; for an open request, state a small artifact and a finite exploration budget. Reuse existing decisions and references.

If two readings would produce different artifacts, resolve that ambiguity or state a reversible assumption. Ordinary implementation does not need a prototype.

Pick the branch that answers the question:

- **Logic or state.** Read [the logic method](references/logic.md) when the question concerns data shape, legal actions, transitions, timing, or behavior.
- **UI or interaction.** Read [the UI method](references/ui.md) when the question concerns layout, information order, density, controls, or interaction.
- **Consumer experience.** Read [the decision methods](references/decision-methods.md) when trying alternatives or a consumer journey would distinguish competing ideas. This is optional, including for libraries and internal APIs.

Done when the question and an observation that could change the decision are explicit.

## Build only the experiment

1. Use realistic representative inputs, awkward boundary cases, and the project's domain terms. Preserve supplied values and identifiers; label invented fixtures.
2. Put the artifact in a clearly named prototype location within the authorized write scope. Use a scratch artifact unless the question needs the existing page or module context. Follow existing routes and runners where applicable.
3. Choose the smallest runnable form: a self-contained logic demo, a short script, or a temporary UI rendering path. Keep relevant state visible and scenarios repeatable.
4. Keep state in memory by default. Use stubs for real mutations; use a named scratch store only when persistence is the question and that store is authorized.
5. Skip production abstractions and polish that cannot affect the decision. Retain the checks needed for a valid observation and safe operation. A blanket ban on tests is no substitute for reliable evidence.

If alternatives would settle the question, label and compare them under the same inputs. A single decisive experiment is enough when comparison adds nothing.

## Observe and conclude

Drive the artifact on the surface the decision concerns. For logic, record the actual outputs, transitions, or timing and the exercised inputs. For UI, inspect the rendered alternatives and drive their relevant interactions through supported host preview or browser tools. Use the existing runner only when the artifact requires it.

State which cases were observed and which remain untested. A screenshot alone cannot establish an interaction, and source inspection cannot establish a rendered result. If the necessary surface is unavailable, preserve the artifact and leave the conclusion qualified.

Return the question, artifact path and run instructions, observations, trade-offs, and the supported conclusion. Preserve that conclusion in the requested or established decision artifact; the reply suffices when no durable note was requested. Keep the experiment available for review.

A validated idea can inform a later authorized build. Prototype completion does not authorize production changes, branch creation, commits, pushes, or publication. End at the experiment unless that further work is already in scope.

Done when the bounded artifact answers the decision with appropriate observations, or records the precise unresolved case without claiming success.

## Provenance

Read [the per-file sources](references/SOURCES.md) when checking attribution, original hashes, destinations, and adaptation.
Files in this package (24)
  • LICENSE-mattpocock 1 KB
  • LICENSE-pstack 1 KB
  • LICENSE-pstack-claude 1 KB
  • NOTICE-skills.md 2 KB
  • NOTICE.md 11 KB
  • SKILL.md 4 KB
  • evals/examples.md 2 KB
  • evals/results/2026-11-08-codex-gpt-6.1-sol-activation-1-core5.md 4 KB
  • evals/results/2026-11-08-codex-gpt-6.1-sol-activation-2-core5.md 4 KB
  • evals/results/2026-11-08-codex-gpt-6.1-sol-activation-3-core5.md 4 KB
  • evals/results/2026-11-08-codex-gpt-6.1-sol-near-miss-1-core5.md 4 KB
  • evals/results/2026-11-08-codex-gpt-6.1-sol-near-miss-2-core5.md 4 KB
  • evals/results/2026-11-08-codex-gpt-6.1-sol-near-miss-3-core5.md 4 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-activation-1-claude.md 4 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-activation-2-claude.md 5 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-activation-2-round2-pre-claude.md 4 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-activation-3-claude.md 5 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-near-miss-1-claude.md 4 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-near-miss-2-claude.md 4 KB
  • evals/results/2026-11-09-claude-claude-opus-5-5-near-miss-3-claude.md 4 KB
  • references/SOURCES.md 7 KB
  • references/decision-methods.md 1 KB
  • references/logic.md 2 KB
  • references/ui.md 2 KB

Versions

RepositoryScoreLicence
This page · cravingmaker/skills90MIT
leanstacks/lstk100MIT
A7-studio/jobmigo100MIT
akillness/jeo-skills100MIT
runwield/runwield100MIT
yuan88964/RelayStudio100MIT
mathews-tom/armory100MIT
deaconb28-lang/prototype100MIT
drvoss/everything-copilot-cli100MIT

Database snapshot: 13.11.2026 · package version d703031bc4bb (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 85workflow-prototype
    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
  • 90throwaway-prototype
    Use when a design question needs a throwaway runnable answer: a terminal app that exercises a state model, or switchable UI variants on one route. Not for production code.
  • 90jor-prototype
    Build a throwaway prototype to answer a design question. Use to sanity-check whether a state model or logic feels right, or to explore what a UI should look like with variants screenshotted at the project's breakpoints.
  • 100plan-prototype
    Build throwaway code that a person runs to answer one design question before anything is committed. A clickable HTML file for a state model or logic, or variants a person switches by hand on a real page for a UI. Builds two or three competing variants when the repo has no…
  • 100design-prototype
    Assemble a clickable, runnable prototype from screens/components — wiring navigation, state, and interactions so a team can actually click through it. Use when the user says "make it clickable", "build a prototype", "wire up the flow", "interactive prototype", "make the screens…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.