Draw.io Diagram Expert

.drawio

references/

When to Use

• Users explicitly request

  draw.io

  ,

  diagrams.net

  , or

  .drawio

  files
• Users request to generate flowcharts, architecture diagrams, sequence diagrams, ER diagrams, state machine diagrams, or mind maps
• Users want to export diagrams as PNG/SVG/PDF
• Users need illustrations for technical articles, tutorials, or system design documents
• Users provide an article and hope to extract multiple technical diagrams into a single draw.io file

• Users only want Mermaid code and don't need

  .drawio

  files
• Users require bitmap illustrations, posters, or whiteboard-style body illustrations instead of structured diagrams
• Users are only discussing diagram ideas and don't want to actually generate files yet

Reference Routing

references/style-spec.md

references/xml-and-layout.md

references/export-and-files.md

references/use-cases.md

Core Rules

• By default, first generate the native

  .drawio

  file, then decide whether to export based on user requirements.
• If users explicitly request export to PNG/SVG/PDF, still keep the

  .drawio

  file as the source file unless users explicitly request deletion.
• When outputting diagrams, prioritize clear information structure first, then visual consistency; do not sacrifice readability for "good looks".
• Use plain text for

  mxCell.value

  in diagrams by default, avoid embedding HTML tags.
• Keep connection labels short; prioritize placing long descriptions inside nodes or in side note nodes.
• Avoid explaining basic concepts if possible; reserve context for constraints that truly affect drawing results.

Diagram Type Selection

• Process steps, decision branches, algorithm logic: Flowchart
• Module relationships, service dependencies, deployment layers: Architecture diagram
• Service calls, message interactions, sequential processes: Sequence diagram
• Entities, fields, primary/foreign key relationships: ER diagram
• Lifecycle, state transitions, event-driven processes: State machine diagram
• Concept sorting, knowledge organization, hierarchical expansion: Mind map

Workflow

1. Identify Task Mode

• Single diagram generation
• Single diagram generation and export
• Multiple diagrams generation from one article
• Modify existing

  .drawio

  file

2. Collect Minimum Necessary Input

• Diagram topic
• Target diagram type
• Key nodes / modules / entities / steps
• Relationships between nodes
• Whether export is needed, and the export format

3. Read Corresponding Reference Materials

• Read

  references/style-spec.md

  when unified visual style is required
• Read

  references/xml-and-layout.md

  when generating XML or judging layout
• Read

  references/export-and-files.md

  when exporting or naming files
• Read

  references/use-cases.md

  when showing users common prompts or article illustration modes

4. Plan First, Then Generate

• Which diagram type to adopt
• Whether the page is a single diagram or multiple

  diagram pages

• How to layout node groups
• Which connections need labels and which don't

5. Generate

.drawio

File

1. Title
2. Containers / Groups
3. Core nodes
4. Connections
5. Labels and side notes

6. Export or Open

• Execute export only when users request it
• By default, deliver

  .drawio

  file when users only request generation
• If

  drawio

  CLI is not available locally, clearly inform users that automatic export is not possible, but the

  .drawio

  file has been generated

Multi-Diagram Article Mode

• First extract 2-6 structures from the article that are most worth diagramming
• Each structure corresponds to an independent

  diagram page

• The main file name defaults to match the article file name
• Page names use lowercase English with hyphens
• Avoid squeezing all knowledge points of the entire article into one large diagram

references/use-cases.md

Verification Checklist

• Whether the diagram type matches the task
• Whether main nodes are complete and relationships are drawn correctly
• Whether connection directions and semantics are clearly stated
• Whether text is concise and not overcrowded
• Whether HTML tags are mixed into

  mxCell.value

• Whether export file names comply with naming specifications
• If it's a multi-page file, whether page names are clear and consistent

Failure Handling

• If user requirements are too vague, first present the inferred diagram structure, then explain your assumptions
• If export fails, retain the

  .drawio

  file, report the failure reason and manually executable export commands
• If the content requested by users is more suitable for Mermaid or image illustrations, clearly explain and suggest using a more appropriate method

Output Requirements

• Default to return the generated file path
• If export is executed, return both the generated and exported file paths
• If there are assumptions, deletions, or structural adjustments, explain in one sentence