html

1# HTML
2 
3Build one self-contained HTML file that makes the subject clearer, easier to use, or easier to understand. The standard is consistent care, not a consistent look. Do not reproduce a house palette, typography stack, card system, or layout from prior runs.
4 
5## Route the request first
6 
7Use the narrowest skill that owns the main review question:
8 
9- Read and compose [`design-artifact`](../design-artifact/SKILL.md) with the
10  chosen workflow when palette, type, composition, theming, or overall visual
11  register remain open. It provides creative direction; it does not replace the
12  specialist that owns fidelity, structure, or behavior.
13- Read and follow [`html-wireframe`](../html-wireframe/SKILL.md) when structure, information hierarchy, navigation, or task flow is still unsettled. It should remain visibly low fidelity and may compare two or three layout directions.
14- Read and follow [`html-prototype`](../html-prototype/SKILL.md) when the user needs a polished mockup or a working interactive flow. A mockup is the static fidelity mode inside that skill.
15- Read and follow [`html-plan`](../html-plan/SKILL.md) when the artifact is primarily a plan, roadmap, implementation sequence, or rollout document whose source commitments must remain easy to verify.
16- Read and follow [`html-diagram`](../html-diagram/SKILL.md) when relationships, sequence, topology, state, hierarchy, or system behavior are the main content.
17…