prototype

Build throwaway HTML or UI prototypes to answer design questions.

10|3|Updated Jul 18, 2019
One-click install
npx skills add https://github.com/tanqimin/MyFavsORM --skill prototype-tanqimin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/tanqimin/MyFavsORM/tree/main/.agents/skills/prototype
Command: npx skills add https://github.com/tanqimin/MyFavsORM --skill prototype-tanqimin

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, flip between variants, and feel whether a design actually works before committing to real code. ## Core Features & Use Cases - Logic Prototypes: Generate a single self-contained HTML file with free-play buttons and tabbed guided walkthroughs that drive a pure state machine or reducer through edge cases, shareable with non-developers by double-click. - UI Prototypes: Generate 3-5 structurally different UI variants 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 archive the prototype on a throwaway branch as a primary source. - Use Case: Before building a checkout flow, prototype the state machine as a clickable HTML demo so a PM can discover that "cancel after payment" behaves unexpectedly. ## Quick Start Ask the AI to build a prototype that answers whether your state model handles a specific edge case, or to generate three UI variants of 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 real 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 and click through scenarios to find flaws in the model.

How to compare multiple UI design variants in one app?

Render 3-5 structurally different variants on the same route, gated by a ?variant= URL search param, with a floating bottom bar offering arrow buttons and keyboard navigation to cycle between them. Keep existing data fetching intact and only swap the rendered subtree.

Should a prototype use a real database or persistence?

No. Prototypes keep state in memory by default because persistence is usually the thing being checked, not a dependency. Only hit a scratch database or clearly marked throwaway file when the question explicitly involves storage behavior.

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

Choose a logic prototype when the question is whether a state model or business logic feels right, producing a clickable HTML demo. Choose a UI prototype when the question is what something should look like, producing multiple layout variants on a route.

What happens to prototype code after the question is answered?

The validated decision is folded into the real codebase, while the prototype itself is committed to a throwaway branch as a primary source with a pointer left on the implementation issue. Prototype code is never promoted directly to production.