# Drawio
> Always use when the user asks to create, generate, draw, or design a diagram, flowchart, architecture diagram, ER diagram, sequence diagram, class diagram, network diagram, mockup, wireframe, UI sketch, draw.io/drawio/drawoi, .drawio files, or diagram export to PNG/SVG/PDF/JPG.
- Skill: `ethanolivertroy/drawio` (Agent Skill, multi-file: 7 files)
- Install (CLI): `npx skillmds@latest add ethanolivertroy/drawio`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ethanolivertroy/drawio/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- License: MIT
- Author: ethanolivertroy (https://skillmd.com/u/ethanolivertroy)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ethanolivertroy/drawio
---
# Draw.io Diagram Skill
Generate native draw.io diagrams as `.drawio` files. When requested, export them to PNG, SVG, or PDF with embedded diagram XML so the exported file remains editable in draw.io.
## Workflow
1. Determine the requested diagram type, filename, and output format.
2. Generate draw.io XML directly in `mxGraphModel` format.
3. Write the XML to a `.drawio` file in the current working directory.
4. Validate XML well-formedness and run the lightweight layout checker when possible.
5. Apply the visual quality rules in `references/layout-quality.md`: margins, spacing, explicit edge routing, no clipped actors, and no edge-label collisions.
6. Optionally post-process edge routing if the helper can run without installing anything.
7. If the user requested PNG/SVG/PDF/JPG, export with the draw.io Desktop CLI if available.
8. For image exports, visually self-review the rendered PNG/SVG/PDF when the environment allows reading or previewing it.
9. Open the exported result, or the `.drawio` source if no export was requested or export is unavailable.
10. If opening fails, print the absolute file path.
Use the scripts in this skill directory when helpful:
```bash
./scripts/check-drawio-layout.py diagram.drawio
./scripts/postprocess-drawio.sh diagram.drawio
./scripts/drawio-export.sh diagram.drawio png diagram.drawio.png
./scripts/open-result.sh diagram.drawio.png
```
When using scripts from another directory, call them with the absolute path to this skill directory. For package installs, the skill directory is usually inside Pi's package cache under `skills/drawio`.
## Choosing the output format
Infer the output format from the user's request.
Examples:
- `/skill:drawio create a flowchart` -> `flowchart.drawio`
- `/skill:drawio png flowchart for login` -> `login-flow.drawio.png`
- `/skill:drawio svg: ER diagram` -> `er-diagram.drawio.svg`
- `/skill:drawio pdf architecture overview` -> `architecture-overview.drawio.pdf`
- `/skill:drawio jpg homepage wireframe` -> `homepage-wireframe.drawio.jpg`
If no format is mentioned, create and open only the `.drawio` file.
### Supported export formats
| Format | Embed XML | Notes |
|--------|-----------|-------|
| `png` | Yes (`-e`) | Viewable everywhere, editable in draw.io |
| `svg` | Yes (`-e`) | Scalable, editable in draw.io |
| `pdf` | Yes (`-e`) | Printable, editable in draw.io |
| `jpg` | No | Lossy; no embedded XML support |
Use double extensions for exports: `name.drawio.png`, `name.drawio.svg`, `name.drawio.pdf`, or `name.drawio.jpg`.
After a successful PNG/SVG/PDF export, delete the intermediate `.drawio` file because the exported file embeds the diagram XML. Do not delete the `.drawio` file for JPG exports because JPG cannot embed editable diagram XML.
## File naming
- Use a descriptive filename based on the content.
- Use lowercase words separated by hyphens.
- Avoid spaces and punctuation.
- Preserve `.drawio` before the export extension.
Examples: `login-flow.drawio`, `database-schema.drawio.svg`, `network-topology.drawio.pdf`.
## XML format
A `.drawio` file is native mxGraphModel XML. Always generate XML directly. Do not save Mermaid, PlantUML, CSV, or pseudo-code when the user requested draw.io.
Every diagram must include the required root cells:
```xml
```
All normal diagram elements use `parent="1"` unless intentionally creating layers or containers.
### Required edge structure
Edges must not be self-closing. Every edge needs a geometry child:
```xml
```
## Visual layout quality rules
Good XML is not enough. The diagram must render cleanly.
Mandatory layout rules:
- Keep visible elements at least 40 px inside the page bounds.
- Never place actors, labels, or arrowheads partly off-canvas.
- Keep nodes away from container borders and swimlane headers.
- Use a grid with generous row/column spacing.
- Avoid edge labels by default; labels on edges often collide with nodes after draw.io routing.
- Prefer descriptive node text or separate text cells placed away from connectors.
- Use explicit orthogonal edge routing with `exitX`, `exitY`, `entryX`, `entryY`, and waypoints for non-trivial edges.
- Avoid arrows crossing through node text, other nodes, or container labels.
- For cloud architecture diagrams, put edge services on the top row, network/VPC in the middle, app/data tiers inside subnets, and regional managed services clearly inside the cloud boundary.
- After export, visually self-review the rendered image if possible and fix clipped content, label collisions, crossing arrows, or confusing containment before final response.
Run the bundled checker when possible:
```bash
./scripts/check-drawio-layout.py diagram.drawio
```
Then consult `references/layout-quality.md` for detailed rules and patterns.
## XML well-formedness rules
These rules are mandatory:
- Never include XML comments (``) in generated diagram XML.
- Escape attribute values: `&`, `<`, `>`, `"`.
- Use unique `id` values for all `mxCell` elements.
- Include `id="0"` and `id="1"` root cells.
- Give every vertex an `mxGeometry` child with `x`, `y`, `width`, `height`, and `as="geometry"`.
- Give every edge an `mxGeometry relative="1" as="geometry"` child.
- Prefer simple, valid styles over overly clever styles.
- Avoid double hyphens anywhere in XML text, especially if user-provided labels might later be copied into comments by tools.
Useful validation commands:
```bash
python3 - <<'PY'
import sys, xml.etree.ElementTree as ET
ET.parse(sys.argv[1])
print('XML OK')
PY diagram.drawio
```
## Draw.io CLI export
The draw.io Desktop app includes a command-line export interface. Prefer the bundled helper script because it handles macOS, Linux, and WSL2 detection:
```bash
./scripts/drawio-export.sh [output-file]
```
The helper uses:
```bash
drawio -x -f -e -b 10 -o