AI Agent Hub
Back to skills
Diagram Builder Pro icon

Diagram Builder Pro

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please install @user_60120345/diagram-builder-pro according to https://skillhub.cn/install/skillhub.md.

About this skill

Problem

Text-only descriptions are often not clear enough for architecture reviews, design docs, or troubleshooting notes. Engineers need to quickly express system architecture, microservices, network topology, workflows, sequence flows, state machines, or ER diagrams, but hand-written SVG often requires repeated tuning for colors, spacing, arrow direction, and clipping.

Capabilities and Workflow

The skill supports two output modes:
- Inline visualization: load styling rules with read_me, then render a fixed viewBox 0 0 680 SVG/HTML fragment using show_widget for immediate review in conversation.
- Mermaid code blocks: generate syntax such as flowchart, sequenceDiagram, stateDiagram-v2, and erDiagram for embedding in Markdown documents.
It follows layout conventions such as layered grouping, marker direction, refX/refY alignment, legend placement, and readable Chinese labels.

Boundaries

It is best used for solution sketches and technical explanatory diagrams. Keep a single diagram under 20 nodes, and split complex systems into focused views. It does not replace formal UML modeling tools, and critical component relationships still need human validation.

Use Cases

  • Sketch a layered cloud-native architecture with API Gateway, service mesh, and databases during design review.
  • Organize request paths from services to the data layer into a sequence diagram for system design documents.
  • Draw approval flows, exception branches, and role swimlanes as a Mermaid diagram for embedded documentation.
  • Quickly render component dependencies and request paths as inline SVG during incident discussion.

Best For

  • Backend engineers who need to sketch microservice architecture with API Gateway, service mesh, and databases during design reviews.
  • System architects who need to embed sequence diagrams, state machines, and ER diagrams in technical design documents.
  • SREs who need component dependency and request path diagrams to explain fault impact during incident reviews.
  • Technical product managers who need workflow and swimlane diagrams to align with engineering on approval branches and roles.