prototype

Build throwaway prototypes that answer design questions about logic models or UI layouts.

1|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/filippolmt/skills --skill prototype-filippolmt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/filippolmt/skills/tree/main/skills/prototype
Command: npx skills add https://github.com/filippolmt/skills --skill prototype-filippolmt

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 a real implementation. ## Core Features & Use Cases - Logic Prototypes: Build a single self-contained HTML file with free-play buttons and tabbed guided walkthroughs that drive a pure reducer, state machine, or function set through edge cases — shareable with non-developers by double-click. - UI Prototypes: Generate 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, then preserve the prototype on a throwaway branch as a primary source linked from the implementation issue. - Use Case: A PM is unsure whether a state machine handles an edge case. You build a one-file HTML demo with scenario walkthroughs; they click through, spot the flaw in the idea, and you lift the validated reducer into the real module. ## Quick Start Ask the assistant to prototype whether your state model handles a specific edge case, or to generate three UI 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 before writing production code?

Build a single self-contained HTML file containing a pure reducer or state machine module, with one button per action and tabbed scenario walkthroughs. Anyone can open it by double-clicking, press buttons, and watch the full state re-render after each action.

How to compare 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 left and right arrows that updates the param via the framework router, so variants are shareable and reload-stable.

Should a prototype use a framework like React or plain HTML?

Logic prototypes should be one plain HTML file with no framework, bundler, or server so they survive being emailed and double-clicked. UI prototypes follow the host project's existing framework and component library since they live on real routes.

When should I not write a prototype?

Skip prototyping when there is no open design question to answer. A prototype exists to settle one specific question about logic or appearance; adding tests, persistence, or generalization turns it into production code written under prototype constraints.

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 kept out of main. Leave a pointer to that branch on the implementation issue so the prototype remains a re-runnable primary source.