html-wireframe
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.
Profile →npx skills add plannotator/effective-html --skill html-wireframe --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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: 1. The user's explicit instructions and accepted decisions. 2. The product's existing structure and terminology. 3. The user, task, and content being modeled. 4. 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`](../design-artifact/SKILL.md) is
- Establish the review question
- Explore structure before style
- Keep the artifact intentionally unfinished
- Add only useful behavior
- Build contract
- Verify and hand off
- Further reading
What does the html-wireframe skill do?
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.
How do I install it?
Run `npx skills add plannotator/effective-html --skill html-wireframe --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From plannotator/effective-html, a repository with 1,576 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.