prototype

Installation
SKILL.md

Prototype

Purpose

A prototype is throwaway code that answers a question. The question decides the shape; getting the branch wrong wastes the whole prototype.

Workflow

  1. Name the question the prototype must answer, in one sentence. If you cannot, the prototype has no purpose — go back to discovery.
  2. Pick the branch:
    • Logic / state model → a single shareable HTML file (or minimal script) that pushes the state machine through the cases hard to reason about on paper, drivable by a non-developer.
    • UI → several radically different variations on one route or page, switchable without editing code (URL param or a small switcher). If genuinely ambiguous, default to whichever branch matches the surrounding code (backend module → logic; page or component → UI) and state the assumption at the top of the artifact.
  3. Build it under the prototype rules (below).
  4. Report the verdict: the question, the answer the prototype gave, and what should change in the real design.
  5. Capture: fold any validated decision into the real design by recording it in the spec or ticket it informed; production code edits belong to a separate, explicitly authorized implementation scope. Keep the prototype itself as a primary source on a clearly-marked throwaway branch or scratch path, pointed at from that spec or ticket. The main branch keeps only the validated decision.

Prototype Rules

Installs
4
First Seen
Oct 13, 2026