prototype

Builds throwaway HTML demos and UI variants to answer design questions.

1|Updated Mar 2, 2025
One-click install
npx skills add https://github.com/marjorg/setup --skill prototype-marjorg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/marjorg/setup/tree/main/home/.agents/skills/archive/0-matt/prototype
Command: npx skills add https://github.com/marjorg/setup --skill prototype-marjorg

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 and stakeholders press buttons, flip between variants, and feel whether a model or layout actually works before committing to real code. ## Core Features & Use Cases - Logic prototypes: Generates 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, readable by non-developers. - UI prototypes: Renders 3-5 structurally different variants of a page on an existing route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key navigation. - Capture workflow: Folds validated decisions into real code and preserves the prototype on a throwaway branch as a primary source. - Use Case: A product manager is unsure whether an order state machine handles cancellation-after-shipping. You build a shareable HTML demo with scenario walkthroughs so they can click through the edge case and confirm the model. ## Quick Start Ask the agent to prototype whether your state machine handles a specific edge case, or to generate three layout variants of an existing page switchable via a URL parameter.

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 without writing production code?

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

How to show multiple UI design variants on one page?

Render each variant as a separate exported component on the same route, gated by a ?variant= URL search param. Add a floating bottom bar with previous and next arrows that updates the URL via the framework router, plus left and right arrow-key cycling.

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, generating structurally different variants rather than color or copy tweaks.

Should prototype code include tests or error handling?

No. A prototype that needs tests is no longer a prototype. Skip tests, persistence, and abstractions; keep only the minimal error handling needed to make the demo runnable, then rewrite properly when folding the validated decision into production code.

What happens to prototype code after the question is answered?

Fold the validated decision into the real codebase, then commit the full prototype to a throwaway branch outside main as a primary source. Leave a pointer to that branch on the implementation issue so the main branch keeps only the validated decision.