Diagram
Skill leolionart/claude-skills/plugins/diagram/skills/diagram
Generate diagrams in ASCII or Mermaid formats. Auto-selects format based on context, or accepts explicit format parameter. Use for flowcharts, sequence diagrams, architecture diagrams, state machines, Gantt charts, ERDs, user journeys, or any visual representation needs.From its SKILL.md
npx -y skills add leolionart/claude-skills --skill diagramAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
5.7 KB, as published. Nobody here has run it
Diagram Generator Skill
Unified skill to generate diagrams in two formats:
- ASCII diagrams (text-based, universal, great for Slack/comments)
- Mermaid diagrams (rendered in GitHub, Notion, Confluence, Obsidian)
Format Selection
Auto-Detection Rules
| User mentions | Selected Format |
|---|---|
mermaid, gantt, sequence, state, c4, flowchart, ERD, diagram | Mermaid |
ascii, text, monospace, console, slack, comment | ASCII |
| Ambiguous or unspecified | Default to Mermaid |
Explicit Format Parameter
User can specify format directly:
- "Vẽ Mermaid flowchart cho login flow"
- "ASCII diagram cho system architecture"
- "Tạo sequence diagram" → defaults to Mermaid
Format 1: ASCII Diagrams
Best for: Slack, GitHub comments, code comments, email, plain text environments.
Building Blocks
Box Characters:
┌ ─ ┐ Top corners & horizontal
│ │ Vertical sides
└ ─ ┘ Bottom corners
╭ ─ ╮ Rounded corners
╰ ─ ╯
╔ ═ ╗ Double border (emphasis)
╚ ═ ╝
Arrows:
→ ← ↑ ↓ Directional
↔ ↕ Bidirectional
⇒ ⇐ Bold
Connectors:
├ ┤ ┬ ┴ T-junctions
┼ Cross
Symbols:
✓ ✗ Check/X
★ ☆ Star
● ○ Circle
Example: Simple Flow
┌─────────┐ ┌──────────┐ ┌─────────┐
│ Start │ ──→ │ Process │ ──→ │ End │
└─────────┘ └──────────┘ └─────────┘
Example: Decision Tree
┌─────────┐
│ Valid? │
└────┬────┘
┌──┴──┐
Yes│ │No
↓ ↓
┌────────┐ ┌────────┐
│ Save │ │ Error │
└────────┘ └────────┘
Example: System Architecture
┌──────────────┐
│ Frontend │ (React)
└──────┬───────┘
│ HTTPS
↓
┌──────────────┐
│ Backend │ (Node.js)
└───┬──────┬───┘
│ │
↓ ↓
┌─────────┐ ┌──────────┐
│ DB │ │ Cache │
│(Postgres)│ │ (Redis) │
└─────────┘ └──────────┘
ASCII Tips
- Use consistent spacing between boxes
- Label arrows with annotations
- Keep boxes aligned vertically/horizontally
- Maximum ~80 chars width for readability
Format 2: Mermaid Diagrams
Best for: GitHub, Notion, Confluence, GitLab, Obsidian - anywhere Mermaid renders.
Supported Diagram Types
| Type | Syntax Start | Use Case |
|---|---|---|
| Flowchart | flowchart TD | Processes, user flows |
| Sequence | sequenceDiagram | API interactions, service calls |
| State | stateDiagram-v2 | Object lifecycles, statuses |
| User Journey | journey | Experience mapping with sentiment |
| C4 | C4Context | System architecture |
| Gantt | gantt | Project timelines, roadmaps |
| ERD | erDiagram | Database schemas |
Quick Examples
Flowchart:
flowchart TD
A[Start] --> B{Decision?}
B -->|Yes| C[Action A]
B -->|No| D[Action B]
Sequence Diagram:
sequenceDiagram
User->>API: Request
API->>Database: Query
Database-->>API: Result
API-->>User: Response
State Diagram:
stateDiagram-v2
[*] --> Idle
Idle --> Loading: submit
Loading --> Success: complete
Success --> [*]
Gantt Chart:
gantt
title Project Timeline
dateFormat YYYY-MM-DD
Task 1: t1, 2025-01-01, 7d
Task 2: t2, after t1, 5d
Mermaid Optimization Rules
- Keep labels concise (2-5 words max)
- Limit complexity (<15 nodes per diagram)
- Use
dateFormat YYYY-MM-DDfor Gantt - Use
after [task_id]for dependencies - Escape special characters with quotes
Reference Files
references/syntax-reference.md- Complete syntax for all typesreferences/optimization-rules.md- Rendering and styling guidelinesreferences/examples.md- Practice exercises and patterns
Process Steps
- Understand request - What is being visualized? Flow, architecture, timeline?
- Select format - Use auto-detection or explicit user preference (defaults to Mermaid)
- Gather inputs:
- Description of diagram
- Nodes/components to include
- Relationships/flows between them
- Generate diagram - Apply format-specific rules
- Validate output:
- ASCII: Aligned, readable monospace
- Mermaid: Valid syntax, renders correctly
- Deliver - Include in response or save to file
Quality Gates
- Format matches user preference or auto-selection
- All nodes/components from request are included
- Relationships/flows are correctly represented
- Diagram is readable and not overcrowded
- For Mermaid: Syntax is valid and follows optimization rules
- For ASCII: Proper alignment and box drawing characters
Related Skills
confluence-publishing: Publish Mermaid/ASCII diagrams to Confluenceui-design-guide: Design guidelines for visual consistency