From viz
Quick interactive diagram generator - ask user what they want, generate Mermaid, and render as HTML
How this command is triggered — by the user, by Claude, or both
Slash command
/viz:diagram [description]This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# Quick Diagram Generator Interactive command to generate Mermaid diagrams and render them as HTML pages. ## Workflow ### Step 1: Determine Diagram Requirements If the user provided a description via argument, skip to Step 2. Otherwise, use AskUserQuestion to gather requirements: **Question 1: Diagram Type** **Question 2: Diagram Content** Ask the user to describe what the diagram should show -- components, actors, relationships, flows. ### Step 2: Generate Mermaid Code Based on user input: 1. Choose appropriate diagram syntax from `../skills/mermaid-display/references/diagram-typ...
Interactive command to generate Mermaid diagrams and render them as HTML pages.
If the user provided a description via argument, skip to Step 2.
Otherwise, use AskUserQuestion to gather requirements:
Question 1: Diagram Type
{
"questions": [
{
"question": "What type of diagram would you like to create?",
"header": "Diagram Type",
"multiSelect": false,
"options": [
{"label": "Flowchart", "description": "Process flows, decision trees, algorithms"},
{"label": "Sequence Diagram", "description": "API interactions, communications, time-based flows"},
{"label": "Class Diagram", "description": "Object-oriented design, data models"},
{"label": "State Diagram", "description": "State machines, workflow states, transitions"},
{"label": "ER Diagram", "description": "Database schemas, entity relationships"},
{"label": "Gantt Chart", "description": "Project timelines, task scheduling"},
{"label": "Pie Chart", "description": "Data distribution, proportions"}
]
}
]
}
Question 2: Diagram Content Ask the user to describe what the diagram should show -- components, actors, relationships, flows.
Based on user input:
../skills/mermaid-display/references/diagram-types.mdWrap the generated Mermaid code as a markdown document:
# {Diagram Title}
```mermaid
{generated mermaid code}
`` `
Write this markdown content to a temp file /tmp/viz-diagram-{name}.md using the Write tool.
Then run the render script via Bash:
bash "${CLAUDE_PLUGIN_ROOT}/lib/render.sh" "/tmp/viz-diagram-{name}.md" "diagram-{name}"
Report what was created and the output path printed by the render script.
If the user explicitly asks for a PNG or SVG file (not HTML), use the render script instead:
/tmp/viz-diagram-{timestamp}.mmd../skills/mermaid-display/references/render-script.sh with INPUT_FILE set to the .mmd pathIf the description is too complex for a single diagram, suggest splitting:
Your description covers multiple aspects. I suggest separate diagrams for:
1. High-level architecture (Flowchart)
2. Authentication flow (Sequence Diagram)
3. Data model (ER Diagram)
Which one first?
../skills/mermaid-display/references/diagram-types.md../skills/mermaid-theme/references/color-schemes.md../skills/mermaid-display/references/render-script.shnpx claudepluginhub musingfox/cc-plugins --plugin viz/diagramGenerates Mermaid diagrams from codebase analysis or descriptions. Supports flowcharts, sequences, classes, ER diagrams, graphs, and states. Outputs validated Markdown embeds.
/diagramCreates Mermaid or ASCII diagrams for flowcharts, sequence diagrams, ERDs, C4 models, mindmaps, architecture, and more from natural language descriptions.
/generate-web-diagramGenerates a standalone HTML diagram from input using visual-explainer skill, CSS patterns, and optional AI images via surf, then opens it in the browser.
/generate-diagramsGenerates Mermaid diagrams including C4 architecture (L0-L3), data flows, sequence diagrams, user journeys, and ERDs from codebase analysis. Supports --type filter.
/createCreates production-quality draw.io diagrams by analyzing project context to auto-select type, applying styles, themes, multi-page support, and layers.