draw.io Diagrams
Use this when editability matters. The canonical source should be .drawio, not only a rendered PNG.
Workflow
- Clarify diagram type, audience, paper/report context, and required output formats.
- Create or edit
.drawioXML as the source artifact. - Keep labels short and domain-specific.
- Use stable layout: left-to-right for pipelines, top-to-bottom for stages, grouped regions for modules.
- If exporting is requested, prefer SVG or PDF with embedded draw.io XML when supported so the figure remains editable.
- Validate by reopening or inspecting XML structure when possible.
Output Policy
- For manuscripts: deliver
.drawioplus SVG/PDF export. - For README/docs: deliver
.drawioplus SVG or PNG. - For early brainstorming: consider
excalidraw-diagramsinstead. - For DSL-native architecture diagrams: consider
d2-diagrams,plantuml-diagrams, ormarkdown-mermaid-writing.
Boundaries
- Do not make only a screenshot when the user asked for editable diagrams.
- Do not rely on draw.io desktop CLI unless it is installed or the user accepts that dependency.
- Do not embed hidden assumptions in diagram labels; use notes or captions for uncertainty.