---
{
  "name": "prototype",
  "description": "Create cheap, rough artifacts to raise the fidelity of a discussion and get concrete feedback. Use when \"how should it look?\" is the key question or a rough take would advance the discussion.",
  "credit": "Matt Peacock (mattpocock/skills)"
}
---

# Prototype

Create cheap, rough artifacts to raise the fidelity of a discussion and get concrete feedback.

## Process

1. **Identify the question** — What specific thing needs a prototype?
2. **Keep it cheap** — Rough, disposable, fast.
3. **Build the artifact** — Code, outline, stub, or diagram.
4. **Present it** — Show what was built and what it demonstrates.
5. **Gather feedback** — What does this teach us?

## Rules

- Prototypes are disposable — don't over-invest.
- Speed over quality.
- The goal is learning, not production code.
- Link the prototype, don't paste it.

## Credit

This skill is based on the work of **Matt Peacock** ([@mattpocock](https://github.com/mattpocock)). Original source: [mattpocock/skills](https://github.com/mattpocock/skills). Licensed under MIT.