prototype

Build throwaway HTML demos or UI variants to answer design questions.

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/salomepoulain/makery-stations --skill prototype-salomepoulain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/salomepoulain/makery-stations/tree/main/stations/claude/workbench/pantry/skills/prototype
Command: npx skills add https://github.com/salomepoulain/makery-stations --skill prototype-salomepoulain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state models, business logic, or UI layouts are hard to settle on paper. This Skill produces throwaway prototypes that let you press buttons, watch state change, or flip between radically different UI variants before committing to real code. ## Core Features & Use Cases - Logic Prototypes: Generate a single self-contained HTML file with free-play action buttons and tabbed guided walkthroughs that drive a pure reducer, state machine, or function set through edge cases, runnable by double-click with no install. - UI Prototypes: Render 3-5 structurally different variants of a page on one route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key navigation. - Capture Workflow: Fold validated decisions into real code and preserve the prototype on a throwaway branch as a primary source. - Use Case: A PM is unsure whether a state machine handles an edge case; you build a shareable HTML demo they can click through to find the flaw in the idea before any production code is written. ## Quick Start Ask the assistant to prototype whether your state model handles a specific edge case, or to generate three different layout variants for an existing page.

Frequently Asked Questions about prototype

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prototype a state machine before writing production code?

Build a single self-contained HTML file with a pure reducer or state machine module, free-play action buttons, and tabbed guided walkthroughs for edge cases. Anyone can open it by double-clicking, with no framework, bundler, or server required.

How to compare multiple UI layout options on one page?

Render 3 to 5 structurally different variants on the same route, gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Variants must differ in layout and information hierarchy, not just colors or copy.

When should I use a logic prototype versus a UI prototype?

Use a logic prototype when the question is whether a state model or data shape feels right under real cases. Use a UI prototype when the question is what a page should look like. If ambiguous, match the surrounding code: backend module means logic, page or component means UI.

Can a prototype be promoted directly to production?

No. Prototype code is written under throwaway constraints with no tests and minimal error handling. Fold the validated decision or winning variant into the real code by rewriting it properly, and keep the prototype itself on a separate throwaway branch.

Should a prototype connect to a real database?

No. State lives in memory by default, since persistence is usually the thing being checked, not a dependency. If the question explicitly involves a database, use a scratch DB or local file clearly marked as disposable.