
Diagram Generator
Turn architecture, flows, and sequences into editable Mermaid, Graphviz, PlantUML, or SVG diagram source—and optionally render them locally—for specs and READMEs.
Install
npx skills add https://github.com/zhaoxuya520/reverse-skill --skill diagram-generatorWhat is this skill?
- Supports Mermaid, Graphviz DOT, PlantUML, and SVG as editable diagram formats
- Ships compact pattern templates for flowcharts, swimlane flows, architecture, and sequence diagrams
- Encourages adapting patterns instead of inventing fragile diagram syntax
- Optional local rendering workflow alongside source generation
- Covers decision nodes, subgraphs, async edges, and participant-style sequence flows
Adoption & trust: 1 installs on skills.sh; 1.3k GitHub stars; trending (+100% hot-view momentum).
Recommended Skills
Lark Doclarksuite/cli
Lark Wikilarksuite/cli
Opensource Guide Coachxixu-me/skills
Readme I18nxixu-me/skills
Doc Coauthoringanthropics/skills
Obsidian Markdownkepano/obsidian-skills
Journey fit
SKILL.md
READMESKILL.md - Diagram Generator
interface: display_name: "Diagram Generator" short_description: "Generate and render Mermaid, Graphviz, PlantUML, and SVG diagrams." # Diagram Generator Skill This skill helps AI assistants create editable diagrams in Mermaid, Graphviz DOT, PlantUML, and SVG, and optionally render them with local tools. # Diagram Patterns Use these compact patterns when generating diagram source. Prefer adapting the pattern instead of inventing complex syntax. ## Mermaid flowchart ```mermaid flowchart TD start([Start]) --> receive[Receive request] receive --> valid{Valid?} valid -- yes --> process[Process request] valid -- no --> fix[Ask for missing info] process --> finish([Finish]) ``` ## Mermaid swimlane-style flowchart ```mermaid flowchart LR subgraph customer[Customer] c1[Submit order] end subgraph app[Application] a1[Validate order] a2[Create invoice] end subgraph ops[Operations] o1[Review exception] end c1 --> a1 a1 -- valid --> a2 a1 -- invalid --> o1 ``` ## Mermaid architecture ```mermaid flowchart LR user[User] --> web[Web App] web --> api[API Service] api --> db[(Database)] api -. async .-> queue[[Queue]] queue --> worker[Worker] worker --> object_store[(Object Store)] ``` ## Mermaid sequence diagram ```mermaid sequenceDiagram actor User participant Web participant API database DB User->>Web: Submit request Web->>API: POST /request API->>DB: Save record DB-->>API: OK API-->>Web: 201 Created Web-->>User: Show confirmation ``` ## Mermaid ER diagram ```mermaid erDiagram CUSTOMER ||--o{ ORDER : places ORDER ||--|{ ORDER_ITEM : contains PRODUCT ||--o{ ORDER_ITEM : appears_in CUSTOMER { string id PK string email } ORDER { string id PK string customer_id FK datetime created_at } ``` ## Mermaid state diagram ```mermaid stateDiagram-v2 [*] --> Draft Draft --> Submitted: submit Submitted --> Approved: approve Submitted --> Rejected: reject Approved --> [*] Rejected --> Draft: revise ``` ## Mermaid class diagram ```mermaid classDiagram class User { +string id +string email +login() } class Order { +string id +decimal total +submit() } User "1" --> "0..*" Order : places ``` ## Mermaid gantt ```mermaid gantt title Delivery Plan dateFormat YYYY-MM-DD section Discovery Requirements :a1, 2026-01-01, 5d Design :after a1, 4d section Build Implementation :2026-01-10, 10d QA :2026-01-22, 5d ``` ## Mermaid mindmap ```mermaid mindmap root((Product Launch)) Research Customer interviews Market scan Build Prototype QA Go-to-market Pricing Campaign ``` ## Mermaid user journey ```mermaid journey title Trial Signup Journey section Discover Visit landing page: 4: User Compare pricing: 3: User section Activate Create account: 5: User Invite teammate: 4: User ``` ## Graphviz dependency graph ```dot digraph G { rankdir=LR; node [shape=box, style=rounded]; app -> api; api -> auth; api -> db; worker -> queue; worker -> db; } ``` ## Graphviz clustered architecture ```dot digraph G { rankdir=LR; compound=true; node [shape=box, style=rounded]; subgraph cluster_client { label="Client"; web; mobile; } subgraph cluster_platform { label="Platform"; api; worker; queue [shape=cylinder]; db [shape=cylinder]; } web -> api; mobile -> api; api -> db; api -> queue; queue -> worker; worker -> db; } ``` ## PlantUML sequence ```plantuml @startuml actor User participant Web participant API database DB User -> Web: Submit request Web -> API: POST /request API -> DB: Save record DB --> API: OK API --> Web: 201 Created Web --> User: Confirmation @enduml ``` ## PlantUML component architecture ```plantuml @startuml actor User rectangle "Client" { [Web App] } rectangle "Backend" { [API Service