prototype

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

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

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 design actually works 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, shareable with non-developers by double-click. - UI Prototypes: Generate 3-5 radically different layout variants on an existing route, switchable via a ?variant= URL param and a floating bottom bar with arrow-key cycling, hidden from production builds. - Capture Workflow: Fold validated decisions into real code and preserve the prototype on a throwaway branch as a primary source, keeping main clean. - Use Case: A product manager questions whether an order state machine handles cancellation-after-payment. The Skill builds a one-file HTML demo with scenario walkthroughs so the PM can click through the edge case and confirm the model. ## Quick Start Ask the assistant to prototype whether your checkout state machine handles a refund after shipment, or to generate three layout variants of the settings 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 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 create multiple UI layout variants on one page?▼

Render structurally different variant components on the same route, gated by a ?variant= URL search param, with a floating bottom bar to cycle between them. Keep existing data fetching intact and hide the switcher in production builds via an environment check.

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 behaves correctly under real cases. Use a UI prototype when the question is what a page should look like, comparing several radically different layouts side by side.

Should prototype code include tests and error handling?▼

No. Prototypes are throwaway by design: skip tests, persistence, and abstractions beyond what makes them runnable. Once a prototype answers its question, fold the validated decision into real code and move the prototype to a throwaway branch.

Can a non-developer use a logic prototype?▼

Yes. The HTML demo uses domain language instead of code terms, renders state as labelled fields rather than raw JSON, and provides guided scenario walkthroughs. A designer, PM, or domain expert can drive it by clicking buttons in a browser.