prototype

Build throwaway HTML or UI prototypes to answer design questions about logic or layout.

Updated Aug 22, 2026
One-click install
npx skills add https://github.com/falentio/cimi --skill prototype-falentio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/falentio/cimi/tree/main/.agents/skills/skills/prototype
Command: npx skills add https://github.com/falentio/cimi --skill prototype-falentio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design questions about state models, business logic, or UI layout are hard to settle on paper. This Skill produces throwaway prototypes that let you press buttons, flip between variants, and feel whether a model or 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 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 an existing route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key navigation. - Capture workflow: Fold validated decisions into real code while preserving the prototype on a throwaway branch as a primary source. - Use Case: You are unsure whether a membership invitation state machine handles revocation after acceptance. Build a logic prototype, hand the HTML file to a PM, and watch them discover the illegal transition in minutes. ## 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, with no framework, bundler, or server required.

How to generate multiple UI variants of an existing page?

Render 3 to 5 structurally different variant components on the existing route, gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Keep the existing data fetching and auth intact so variants are judged against real content.

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, since the two branches produce very different artifacts.

Should prototype code have tests or connect to a real database?

No. Prototypes skip tests, error handling, and persistence by default; state lives in memory. If the question explicitly involves a database, use a scratch database or local file clearly marked as disposable.

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 as a primary source with a pointer on the implementation issue. The main branch keeps only the validated decision, not the prototype shell.