HTML Visualization
Input
$ARGUMENTS
Instructions
Visualize the user's request as an interactive single HTML file.
First, read references/common-rules.md to review common rules.
Type Determination
Determine the type from the first word of $ARGUMENTS.
| Argument |
Type |
Filename Pattern |
mockup |
UI mockup (high-fidelity) |
mockup-{name}.html |
wireframe |
Wireframe (low-fidelity, hand-drawn style) |
wireframe-{name}.html |
erd |
ERD |
erd-{name}.html |
flow |
Flowchart / Sequence diagram |
flow-{name}.html |
chart |
Data chart |
chart-{name}.html |
slides |
Presentation |
slides-{name}.html |
arch |
Architecture diagram |
arch-{name}.html |
dashboard |
Composite dashboard |
dashboard-{name}.html |
timeline |
Timeline / Gantt chart |
timeline-{name}.html |
mindmap |
Mindmap |
mindmap-{name}.html |
kanban |
Kanban board |
kanban-{name}.html |
table |
Interactive data table |
table-{name}.html |
No match: Infer the type from the request content. If unable to infer, ask the user.
When inferred, use visual-{name}.html as the filename.
{name} rule: Extract the core noun from the request and convert to kebab-case. e.g., "user login form" → login-form, "payment flow" → payment-flow.
Input Handling
- File path provided: Read and analyze the file, then visualize.
e.g.,
/html-visual erd schema.prisma → Analyze the Prisma schema to auto-generate ERD
- Existing HTML modification: Read and modify the existing file. Do not recreate from scratch.
- Natural language only: Infer the type, then generate.
Context Gathering
- Description is sufficient: Generate immediately (e.g., "simple login form mockup")
- Project code reference needed: Read code/schema/API first (e.g., "our project's ERD", "current payment flow")
- Criterion: If the request contains project context references like "our", "current", "project's", read the code first.
Type-Specific Guides
mockup
- Device frame: Actual device frame shape for mobile/tablet UI
- Multiple screens: Side-by-side layout + screen labels
- Placeholder data: Realistic data matching project context
- Tab/swipe for screen transitions
wireframe
- Hand-drawn (sketch) style: Slightly irregular lines, hand-drawn feel
- Black-and-white or grayscale. Minimal color
- Text areas shown as gray blocks (no "Lorem ipsum")
- Focus on layout and information structure, exclude visual details
erd
- Entity boxes with attribute lists. Distinguish PK/FK
- Relationship lines: 1:1, 1:N, N:M notation. Auto-track on node drag
- Include relationship type legend
flow
- Node types: Start/End (circle), Process (rectangle), Decision (diamond)
- Directional arrows. Auto-track on node drag
- Display branch conditions on connection lines
chart
- Auto-select appropriate chart type for the data (bar, line, pie, scatter, etc.)
- Axis labels + units, hover tooltips, legend
- Use Chart.js or D3.js
slides
- Reveal.js CDN-based
- Slide transition animations
- Code block highlighting (highlight.js)
- Speaker notes support (toggle with S key)
arch
- Separate system components by layer/zone (Frontend / Backend / DB / External)
- Label communication lines with protocols (HTTP, gRPC, pub/sub, etc.)
- Zoom/pan support
- D3.js force-directed or direct SVG generation
dashboard
- Arrange multiple charts/metrics in grid layout
- KPI cards at the top (numbers + change rates)
- Cross-chart interaction: Click one → filter others
timeline
- Horizontal or vertical timeline
- Event nodes + date labels
- Zoom/scroll for period navigation
- Use Mermaid gantt or D3.js
mindmap
- Radial expansion from center node
- Node collapse/expand
- Use Mermaid mindmap or direct SVG generation
kanban
- Columns: TODO / In Progress / Done (customizable)
- Drag and drop cards between columns
- Display labels/tags on cards
table
- Sort by clicking column headers (ascending/descending)
- Search/filter at the top
- Pagination or virtual scroll
- Cell highlight, row selection
Procedure
- Identify type + target. Ask if ambiguous. Read the file if a path is provided.
- Context gathering decision. Determine if project context is needed. If so, read relevant code/docs.
- Read
references/common-rules.md. Review common principles, aesthetics, CDN, and error prevention rules.
- Read
references/html-boilerplate.md. Start from the base HTML template.
- Generate HTML following the type-specific guide.
- Validate: Review the generated HTML.
- No smart quotes (curly quotes) in HTML attributes
- No unclosed tags
- No overlapping nodes/elements
- If issues found, fix and re-validate
- Instruct to
open {filename}.
1---
2name: html-visual
3version: 0.0.2
4category: design-frontend
5description: "Generate an interactive single-file HTML visualization — mockup, wireframe, ERD, flowchart, chart, slides, architecture diagram, dashboard, timeline, mindmap, kanban, or table. Use when the user wants something rendered rather than described: a UI mockup or wireframe, a database schema as an ERD, business logic as a flowchart, data as a chart, or content as slides. Also use when they point at a file (schema, spec, data) and ask to see it visualized."
6argument-hint: "[type] <content>"
7metadata:
8 source: https://skillmd.com/skills/2ykwang/html-visual
9---
10
11# HTML Visualization
12
13## Input
14
15```text
16$ARGUMENTS
17```
18
19## Instructions
20
21Visualize the user's request as an **interactive single HTML file**.
22First, read `references/common-rules.md` to review common rules.
23
24### Type Determination
25
26Determine the type from the first word of `$ARGUMENTS`.
27
28| Argument | Type | Filename Pattern |
29|----------|------|-----------------|
30| `mockup` | UI mockup (high-fidelity) | `mockup-{name}.html` |
31| `wireframe` | Wireframe (low-fidelity, hand-drawn style) | `wireframe-{name}.html` |
32| `erd` | ERD | `erd-{name}.html` |
33| `flow` | Flowchart / Sequence diagram | `flow-{name}.html` |
34| `chart` | Data chart | `chart-{name}.html` |
35| `slides` | Presentation | `slides-{name}.html` |
36| `arch` | Architecture diagram | `arch-{name}.html` |
37| `dashboard` | Composite dashboard | `dashboard-{name}.html` |
38| `timeline` | Timeline / Gantt chart | `timeline-{name}.html` |
39| `mindmap` | Mindmap | `mindmap-{name}.html` |
40| `kanban` | Kanban board | `kanban-{name}.html` |
41| `table` | Interactive data table | `table-{name}.html` |
42
43**No match**: Infer the type from the request content. If unable to infer, ask the user.
44When inferred, use `visual-{name}.html` as the filename.
45
46**`{name}` rule**: Extract the core noun from the request and convert to kebab-case. e.g., "user login form" → `login-form`, "payment flow" → `payment-flow`.
47
48### Input Handling
49
50- **File path provided**: Read and analyze the file, then visualize.
51 e.g., `/html-visual erd schema.prisma` → Analyze the Prisma schema to auto-generate ERD
52- **Existing HTML modification**: Read and modify the existing file. Do not recreate from scratch.
53- **Natural language only**: Infer the type, then generate.
54
55### Context Gathering
56
57- **Description is sufficient**: Generate immediately (e.g., "simple login form mockup")
58- **Project code reference needed**: Read code/schema/API first (e.g., "our project's ERD", "current payment flow")
59- Criterion: If the request contains project context references like "our", "current", "project's", read the code first.
60
61### Type-Specific Guides
62
63#### mockup
64- Device frame: Actual device frame shape for mobile/tablet UI
65- Multiple screens: Side-by-side layout + screen labels
66- Placeholder data: Realistic data matching project context
67- Tab/swipe for screen transitions
68
69#### wireframe
70- Hand-drawn (sketch) style: Slightly irregular lines, hand-drawn feel
71- Black-and-white or grayscale. Minimal color
72- Text areas shown as gray blocks (no "Lorem ipsum")
73- Focus on layout and information structure, exclude visual details
74
75#### erd
76- Entity boxes with attribute lists. Distinguish PK/FK
77- Relationship lines: 1:1, 1:N, N:M notation. Auto-track on node drag
78- Include relationship type legend
79
80#### flow
81- Node types: Start/End (circle), Process (rectangle), Decision (diamond)
82- Directional arrows. Auto-track on node drag
83- Display branch conditions on connection lines
84
85#### chart
86- Auto-select appropriate chart type for the data (bar, line, pie, scatter, etc.)
87- Axis labels + units, hover tooltips, legend
88- Use Chart.js or D3.js
89
90#### slides
91- Reveal.js CDN-based
92- Slide transition animations
93- Code block highlighting (highlight.js)
94- Speaker notes support (toggle with S key)
95
96#### arch
97- Separate system components by layer/zone (Frontend / Backend / DB / External)
98- Label communication lines with protocols (HTTP, gRPC, pub/sub, etc.)
99- Zoom/pan support
100- D3.js force-directed or direct SVG generation
101
102#### dashboard
103- Arrange multiple charts/metrics in grid layout
104- KPI cards at the top (numbers + change rates)
105- Cross-chart interaction: Click one → filter others
106
107#### timeline
108- Horizontal or vertical timeline
109- Event nodes + date labels
110- Zoom/scroll for period navigation
111- Use Mermaid gantt or D3.js
112
113#### mindmap
114- Radial expansion from center node
115- Node collapse/expand
116- Use Mermaid mindmap or direct SVG generation
117
118#### kanban
119- Columns: TODO / In Progress / Done (customizable)
120- Drag and drop cards between columns
121- Display labels/tags on cards
122
123#### table
124- Sort by clicking column headers (ascending/descending)
125- Search/filter at the top
126- Pagination or virtual scroll
127- Cell highlight, row selection
128
129### Procedure
130
1311. **Identify type + target**. Ask if ambiguous. Read the file if a path is provided.
1322. **Context gathering decision**. Determine if project context is needed. If so, read relevant code/docs.
1333. **Read `references/common-rules.md`**. Review common principles, aesthetics, CDN, and error prevention rules.
1344. **Read `references/html-boilerplate.md`**. Start from the base HTML template.
1355. **Generate HTML following the type-specific guide**.
1366. **Validate**: Review the generated HTML.
137 - No smart quotes (curly quotes) in HTML attributes
138 - No unclosed tags
139 - No overlapping nodes/elements
140 - If issues found, fix and re-validate
1417. **Instruct to `open {filename}`**.