Effective HTML

Five focused skills for creating useful, self-contained HTML artifacts, from low-fidelity wireframes to working interactive prototypes.

svg_small.mp4

Render and annotate local HTML with Plannotator.

Choose a skill

HTML skills for pragmatic visual artifacts.

Skill	Use it for
html	Broad HTML requests, mixed artifacts, reports, explainers, presentations, landing pages, tools, and routing to a specialist
html-wireframe	Low-fidelity layout directions that test content, hierarchy, navigation, flows, and responsive structure
html-prototype	Working prototypes with realistic states, interaction, keyboard support, and responsive behavior
html-plan	Plans, roadmaps, rollouts, and implementation sequences that preserve source commitments
html-diagram	Architecture, sequence, process, state, hierarchy, timeline, and system diagrams

Visit: Effective HTML Website/Guide for more details.

Install

Install the collection:

npx skills add plannotator/effective-html

List or install individual skills:

npx skills add plannotator/effective-html --list
npx skills add plannotator/effective-html --skill html-wireframe
npx skills add plannotator/effective-html --skill html-prototype

Invoke a skill directly:

Use $html-wireframe to explore three responsive layouts for this checkout brief.

Use $html-prototype to make the checkout flow work, including validation, loading, failure, success, keyboard, and mobile states.

Only $html is eligible for implicit invocation. Call a specialist directly when you know the artifact type, or use $html to route a broad request. Each specialist remains independently usable when invoked directly.

Claude Code plugin

/plugin marketplace add plannotator/effective-html
/plugin install plannotator-effective-html@effective-html

Codex plugin

codex plugin marketplace add plannotator/effective-html
codex plugin add plannotator-effective-html@effective-html

How the skills work

The skills separate creative freedom from reliability:

• Visual direction comes from the conversation, project, audience, and subject.
• Wireframes stay intentionally unfinished so reviewers focus on structure.
• Prototypes implement one credible flow and its relevant states.
• Plans preserve source commitments.
• Diagrams choose a visual model and rendering method that fit the relationship being explained.
• Every artifact is responsive, accessible, self-contained, and verified in a browser.

Detailed guidance lives only where it is needed. The broad html skill keeps shared references for creative direction, documents, interfaces, diagrams, charts, and data. The specialist skills remain concise and independently usable.

Repository shape

skills/
├── html/
│   ├── SKILL.md
│   ├── agents/openai.yaml
│   └── references/
├── html-wireframe/
├── html-prototype/
├── html-plan/
└── html-diagram/

examples/
└── release-readiness/
    ├── brief.md
    ├── states.md
    ├── wireframe.html
    ├── prototype.html
    └── screenshots/

site/
├── app/          # Next.js routes
├── content/docs/ # Fumadocs guide
└── public/       # Deployed catalog artifacts

The installable skills and their examples stay at the repository root. The website is isolated under site/ and deployed from that directory.

This project was inspired by Thariq Shihipar's The unreasonable effectiveness of HTML.

Create a shareable link for an HTML file with tot.