Agent skill · shipshitdev
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.
What it needs
About 2k tokens when loaded.
What this skill does
Prototype A prototype is throwaway code that answers a question. The question decides the shape. Contract Inputs: One design question (state/logic, or how it should look) The surrounding module or page when one exists Outputs: A runnable prototype (single HTML file, or UI variants on one route) The captured answer (verdict + question it settled), pointed at from the implementation issue Creates/Modifies: Prototype files next to the real module or page, named so they read as prototypes A throwaway prototype/<name> branch when capturing the primary source External Side Effects: Local files. Git branch for capture. No production deploys. Confirmation Required: Before committing the throwaway branch Before folding a validated decision into production code Delegates To: None. Distinct from artifacts-builder (production artifacts) and theme-factory (visual theme systems). Pick a branch Identify which question is being answered — from the user's prompt, the surrounding code, or by asking: "Does this logic / state model feel right?" → references/LOGIC.md. A single shareable HTML file — free-play buttons plus tabbed guided walkthroughs. "What should this look like?" → references/UI.md. 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 is not 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 1. Throwaway from day one, and clearly marked as such. Locate the prototype close to where it will actually be used. Name it so a casual reader can see it is a prototype, not production. 2. Trivial to run. A UI prototype starts from one command in the project's task runner. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills shipshitdev/prototype--2d9ce4