Agent Skills › plannotator/effective-html › html-diagram

html-diagram

GitHub

生成全屏SVG架构可视化HTML文件。支持深色模式、交互节点及动画流程。新增悬浮面板关闭功能，并实现基于SVG坐标系的拖拽平移与滚轮缩放，优化大屏查看体验。

skills/html-diagram/SKILL.md plannotator/effective-html

Trigger Scenarios

需要创建系统架构或栈结构的可视化图表希望以全屏HTML/SVG形式快速理解复杂架构要求输出内容侧重图形展示而非文字说明

Install

npx skills add plannotator/effective-html --skill html-diagram -g -y

More Options

Use without installing

npx skills use plannotator/effective-html@html-diagram

指定 Agent (Claude Code)

npx skills add plannotator/effective-html --skill html-diagram -a claude-code -g -y

安装 repo 全部 skill

npx skills add plannotator/effective-html --all -g -y

预览 repo 内 skill

npx skills add plannotator/effective-html --list

SKILL.md

Frontmatter

{
    "name": "html-diagram",
    "description": "Create a self-contained HTML file for visualizing architecture and understanding the stack with a high-quality SVG diagram. Use when the user wants a full-screen diagram, wants the output to be light on prose, or wants an HTML artifact that is mostly there to make the architecture click fast.",
    "disable-model-invocation": true
}

HTML Diagram

Review the SVG diagrams used throughout references/html-effectiveness/.

There are a bunch in there, and some of them are focused on architecture and whatnot.

After reviewing them, create an HTML file that is strictly for visualizing the architecture and understanding the stack.

It should not be prose-heavy. It should simplify more into a full-screen diagram and whatnot.

Build a high-quality diagram in SVG. Take your time iterating on the diagram more than anything.

If it makes sense, make the diagram interactive and able to visualize and animate different sequences of system behavior.

Also review references/architecture-example.html — a finished example of this skill done well (full-screen SVG stage, clickable nodes, flow chips that light up and animate request paths).

Always include dark mode: hand-rolled CSS variables on :root / html.dark, a small theme toggle button, localStorage persistence, and an apply-before-paint script in <head> (default to prefers-color-scheme). Style the SVG through CSS classes using those variables — never hard-coded hex inside the SVG — so the diagram follows the theme.

Always make floating overlays dismissible. Any card or panel that overlays the SVG stage (e.g., a detail panel, a legend, a side card) MUST have a visible close button, and MUST re-open when the user clicks a relevant node or filter. This prevents floating panels from permanently blocking content on the full-screen stage.

Architecture diagrams almost always exceed the screen. Support pan (drag) and zoom (mouse wheel). Wrap all SVG contents in <gid="svg-content"> and drive its transform attribute. Pan in SVG-space 1:1 (do NOT divide mouse delta by scale — dividing makes dragging feel sluggish when zoomed in). Zoom at the cursor position by translating so the SVG point under the cursor stays fixed. Suppress node click events after a drag (track a 5px movement threshold + a capture-phase one-shot stopPropagation). Provide visual feedback: grab / grabbing cursors, a zoom-level indicator, and a reset-to-100% button.