html-prototype

1# HTML Prototype
2 
3Build a credible model of a product decision. Match the artifact to the user's context instead of applying a recurring house style. The goal is not to make every possible screen. The goal is to make the important visual or behavioral question testable.
4 
5## Choose the fidelity mode
6 
7Use one of two modes:
8 
9- **Mockup:** Create a polished, responsive, mostly static artifact when the open question is visual hierarchy, layout, typography, color, or product fit.
10- **Prototype:** Create a working flow when the open question is navigation, input, state change, feedback, recovery, or transition.
11 
12Do not create a separate `html-mockup` skill. Do not add behavior merely to make a mockup seem more complete. If a user asks for both modes, preserve the same content and structure so changes in fidelity remain easy to compare.
13 
14## Derive the direction from context
15 
16Inspect the conversation, supplied references, and project before designing. Look for design-system documentation, tokens, existing components, product screenshots, and nearby artifacts.
17 
18Authority runs in this order:
19 
201. The user's explicit visual and functional instructions.
212. The project's established design language and interaction conventions.
223. The product, audience, content, and scenario.
234. Your own design judgment.
24 
25Before coding, settle:
26 
27- the user and critical job;
28- the bounded scenario under review;
29- mockup or prototype mode;
30- the source of the visual direction;
31- the relevant state model;
32…