prototype

Build throwaway HTML or UI prototypes to answer design questions.

2|Updated May 12, 2026
One-click install
npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill prototype-tajo9128
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prototype
Source: https://github.com/tajo9128/BioDockify-Pharma-AI/tree/main/.agents/skills/prototype
Command: npx skills add https://github.com/tajo9128/BioDockify-Pharma-AI --skill prototype-tajo9128

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, runnable prototypes that let you and stakeholders feel the answer before committing to real implementation. ## 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. - UI Prototypes: Generate several 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 preserve 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 they can click through to expose the flaw before any backend code is written. ## Quick Start Ask the agent to prototype whether your state machine 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 production code?

Build a single self-contained HTML file containing a pure reducer or state machine module, with one button per action and tabbed walkthrough scenarios for edge cases. Anyone can open it by double-clicking, and the validated logic module can later be lifted into the real codebase.

How to generate multiple UI variants for one page?

Render several 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 only swap the rendered subtree per variant.

Should a prototype use a framework like React or a dev server?

Logic prototypes should be one plain HTML file with inline CSS and JS so they survive being emailed and opened by double-click. UI prototypes follow the host project's existing framework and routing conventions rather than introducing new tooling.

When should I not build a prototype?

Skip prototyping when the question is already answered or when you start adding tests, persistence, or generalizations. A prototype answers exactly one question; if it needs tests or a real database, it has stopped being a prototype.

What happens to prototype code after the question is answered?

Fold the validated decision into the real code, 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.