html-diagram — Claude Code skill: what it does, how to install
Generates standalone interactive HTML diagrams without external services or build steps. Helps visualize component topology, state transitions, timelines, and quantitative structures.
npx skills add plannotator/effective-html --skill html-diagram -a claude-codeWhat html-diagram does
The skill builds self-contained diagrams in a single .html file with inline styles and JavaScript. Depending on the question to answer, it picks a visual model such as a component topology, call sequence, state transition, hierarchy, matrix, or timeline. It renders the structure using HTML and CSS, SVG, Canvas, or WebGL without build steps or external dependencies.
Interactivity stays purposeful. Controls include filtering, path tracing, pan, zoom, or animations that respect prefers-reduced-motion. Notably, this skill never activates on general coding queries by itself. You must invoke it directly or route requests through the broader html skill.
When design-artifact is present in the workspace, the skill checks it to match overall visual composition. Each completed run outputs the absolute file path and key simplifications made along the way.
What it helps with
- visualize state transitions and conditions in application logic
- generate an interactive component topology inside a single HTML file
- illustrate ordered message sequences over time
- display component hierarchy and ownership without build tools
Example prompts for the agent
- Use html-diagram to generate an interactive state machine diagram for our checkout flow in a standalone HTML file.
- Using html-diagram, create a service topology map with filtering and pan controls.
- Invoke html-diagram to build a sequence diagram showing our authentication handshake.
How to install html-diagram
1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-diagram -a claude-code2Manually: put the files in place
~/.claude/skills/html-diagram/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/html-diagram/
1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-diagram -a codex2Manually: put the files in place
.agents/skills/html-diagram/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-diagram -a cursor2Manually: put the files in place
.cursor/skills/html-diagram/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install plannotator/effective-html html-diagram2Manually: put the files in place
.github/skills/html-diagram/SKILL.md1Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-diagram -a gemini-cli2Platform CLI
gemini skills install https://github.com/plannotator/effective-html --path skills/html-diagramManually: put the files in place
.devin/skills/html-diagram/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add plannotator/effective-html --skill html-diagram -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set3
The whole set →Similar
Questions about html-diagram
How to install html-diagram in Claude Code?
Run npx skills add plannotator/effective-html --skill html-diagram -a claude-code in your terminal. You can also place the skill file directly at ~/.claude/skills/html-diagram/SKILL.md.
What does html-diagram do?
It designs and generates self-contained interactive diagrams in HTML format without build steps or external dependencies. It automatically chooses the right visual form, including topologies, sequence charts, state diagrams, or matrices.
Does html-diagram require external libraries or a build step?
No, the skill outputs a single self-contained file with inline CSS and JavaScript. The diagram opens directly in the browser without external CDN links or build tools.
Source text
SKILL.md · MIT
--- name: html-diagram description: Direct-invocation specialist for self-contained HTML diagrams whose layout, notation, and interaction clarify relationships, sequence, topology, state, hierarchy, or quantitative structure. Use when the user explicitly invokes html-diagram or the broad html skill routes a diagram request here. Do not activate independently from a general request. --- # HTML Diagram Build the smallest visual model that makes the relationship easier to understand than prose alone. Match the notation and visual language to the user's project and subject. Do not force every topic into the same SVG boxes and arrows. ## Choose the right model Identify the question the reader should answer, then select the form: - topology for components and connections; - sequence for ordered messages over time; - process for steps, branches, and handoffs; - state for transitions and conditions; - hierarchy for containment or ownership; - timeline for change over time; - matrix for repeated relationships; - quantitative view when magnitude matters. Decide what must remain visible together and what can be revealed on demand. Use a simpler form when it carries the same meaning. ## Choose the rendering method Use HTML and CSS, SVG, Canvas, or WebGL according to the information and scale. Do not use SVG merely because the output is a diagram. - Keep labels, grouping, direction, and connectors legible before adding interaction. - Use stable node positions when readers must compare states or steps. - Keep edge crossings and ambiguous arrowheads to a minimum. - Put intentionally broad canvases in a contained pan or scroll region. - Use legends only when notation is not self-explanatory. Add sequencing, filtering, path tracing, pan and zoom, or animation only when it helps answer the stated question. Keep overlays dismissible, controls keyboard-accessible, and motion compatible with `prefers-reduced-motion`. When [`design-artifact`](../design-artifact/SKILL.md) is available, read it for the diagram's surrounding composition and visual register. Keep the chosen diagram grammar, label legibility, and relationships authoritative over decorative treatment. ## Build and verify Deliver one self-contained HTML file with essential CSS and JavaScript inline. Require no build step or external service. Use accessible text alternatives and keep important meaning available without animation or color alone. Inspect the result at wide and narrow widths. Check label collisions, clipped nodes, edge routing, reading order, keyboard operation, overflow, and every interactive state. Return the absolute path, the diagram form chosen, and the main simplifications or assumptions.
© plannotator · MIT · plannotator/effective-html