Agent skill · Design & Presentation

html-prototype

Direct-invocation specialist for polished, responsive, self-contained HTML mockups and interactive prototypes grounded in the user's conversation, product context, and design language. Use when the user explicitly invokes html-prototype or the broad html skill routes a mockup or prototype request here. Do not activate independently from a general request. Treat a mockup as a noninteractive fidelity mode within this skill, not as a separate skill.

plannotator16★ · 1 repos on radarProfile →
claude-codecodexMIT
Install
npx skills add plannotator/effective-html --skill html-prototype --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/html-prototype/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,576
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# HTML Prototype Build 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. ## Choose the fidelity mode Use one of two modes: - **Mockup:** Create a polished, responsive, mostly static artifact when the open question is visual hierarchy, layout, typography, color, or product fit. - **Prototype:** Create a working flow when the open question is navigation, input, state change, feedback, recovery, or transition. Do 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. ## Derive the direction from context Inspect the conversation, supplied references, and project before designing. Look for design-system documentation, tokens, existing components, product screenshots, and nearby artifacts. Authority runs in this order: 1. The user's explicit visual and functional instructions. 2. The project's established design language and in

What's inside
Steps it walks through
  1. Choose the fidelity mode
  2. Derive the direction from context
  3. Scope one credible experience
  4. Model relevant states
  5. Make interaction complete
  6. Build contract
  7. Verify and hand off
  8. Further reading
Ships with 1 file
  • agents/openai.yaml
More from effective-html
All skills →
About this skill
What does the html-prototype skill do?

Direct-invocation specialist for polished, responsive, self-contained HTML mockups and interactive prototypes grounded in the user's conversation, product context, and design language. Use when the user explicitly invokes html-prototype or the broad html skill routes a mockup or prototype request here. Do not activate independently from a general request. Treat a mockup as a noninteractive fidelity mode within this skill, not as a separate skill.

How do I install it?

Run `npx skills add plannotator/effective-html --skill html-prototype --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.

Keep going