HTML Wireframe
Direct-invocation specialist for low-fidelity, self-contained HTML wireframes that test...
Install
npx skills add plannotator/effective-html --skill html-wireframe -g -a claude-code -y- Repository
- plannotator/effective-html3.8k
- Category
- Design
- Updated
- 4d ago
- License
- MIT
- Context cost
- Lightabout 1,092 tokens
- Runs scripts
- No, instructions only
What it does
Direct-invocation specialist for low-fidelity, self-contained HTML wireframes that test information hierarchy, content, navigation, task flow, and responsive structure before visual design. Use when the user explicitly invokes html-wireframe or the broad html skill routes a wireframe request here. Do not activate independently from a general request. Do not use for polished mockups or production-like interaction; use html-prototype for those.
HTML Wireframe
Turn 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.
Establish the review question
Read the conversation, supplied brief, and nearby project material before choosing a layout. Reuse the project's vocabulary, content model, and known product constraints.
Authority runs in this order:
- The user's explicit instructions and accepted decisions.
- The product's existing structure and terminology.
- The user, task, and content being modeled.
- Your own layout judgment.
Before coding, identify:
- the user and the job they need to complete;
- the screen or bounded flow under review;
- the information and actions the artifact must contain;
- the assumptions that can be made safely;
- the structural questions the wireframe should help answer.
Use real labels and representative content. Low fidelity is not permission to use anonymous boxes or lorem ipsum where wording affects the layout.
Explore structure before style
When design-artifact is available, read it for
subject-specific composition and hierarchy guidance without importing editorial
polish. This skill's low-fidelity contract remains authoritative.
When the layout is still unsettled, create two or three meaningfully different directions. Vary product decisions such as:
- navigation model;
- grouping and order;
- primary-action placement;
- content density;
- overview versus step-by-step flow;
- desktop-to-mobile reflow.
Do not call color changes or minor card rearrangements separate directions. Give each direction a short descriptive name and one sentence about its tradeoff.
