html-prototype is a specialist skill for testing a product decision in the browser. The agent chooses between a mockup, when the open question is visual hierarchy or fit, and a prototype, when the question is navigation, input, state change or recovery.
It derives the visual direction from your conversation, references and project, scopes the smallest flow that answers the review question, lists the states that flow can reach, and verifies them at desktop and mobile widths. Delivery is one self-contained HTML file.
What You Get
- One self-contained HTML file with inline CSS and JavaScript and no build step
- A mockup or prototype mode chosen from the open question
- Realistic content and the reachable states: loading, empty, error, success, disabled and mobile
- Keyboard support, visible focus and dialog behavior with focus restoration
- A handoff naming the scenario, the states built and the production behavior left out
Common Use Cases
- Testing a checkout or onboarding flow before engineering starts
- Showing stakeholders a polished layout of a new screen
- Exploring how a form should validate and recover from errors
- Comparing a static mockup and a working prototype that share the same content
What Makes It Unique
It keeps fidelity matched to the question. A mockup stays mostly static and a prototype implements one flow end to end, with dead buttons removed and out-of-scope actions explained. It also checks computed colors on every surface and says which checks remain unverified when browser tooling is missing.
Under The Hood
The skill is a single instruction file with no scripts. The agent reads project design documents and writes one HTML file to your workspace. Verification asks it to open the page in a browser, resize it, press keys, read the console and test reduced motion. The delivered prototype needs no authentication, live API or external service.