html-wireframe

1# HTML Wireframe
2 
3Turn a product question into a low-fidelity HTML artifact that is easy to inspect, change, and discuss. The wireframe should help reviewers decide what belongs on the screen and how the task should work. It should not look like a finished product.
4 
5## Establish the review question
6 
7Read the conversation, supplied brief, and nearby project material before choosing a layout. Reuse the project's vocabulary, content model, and known product constraints.
8 
9Authority runs in this order:
10 
111. The user's explicit instructions and accepted decisions.
122. The product's existing structure and terminology.
133. The user, task, and content being modeled.
144. Your own layout judgment.
15 
16Before coding, identify:
17 
18- the user and the job they need to complete;
19- the screen or bounded flow under review;
20- the information and actions the artifact must contain;
21- the assumptions that can be made safely;
22- the structural questions the wireframe should help answer.
23 
24Use real labels and representative content. Low fidelity is not permission to use anonymous boxes or lorem ipsum where wording affects the layout.
25 
26## Explore structure before style
27 
28When [`design-artifact`](../design-artifact/SKILL.md) is available, read it for
29subject-specific composition and hierarchy guidance without importing editorial
30polish. This skill's low-fidelity contract remains authoritative.
31…