From inputs/requirements.md, create a system diagram
Output Formats
Extension
Description
When to Use
*.drawio
Native format
Recommended
*.drawio.svg
SVG + metadata
Markdown/Web
*.drawio.png
PNG + metadata
Image with edit
Output: outputs/
If the user asks for an editable diagram, make *.drawio the primary deliverable. Do not let a plain SVG or preview artifact become the file the user is expected to edit.
When the deliverable is headed for print, gate it on the Monochrome Print Profile and the Pre-delivery Geometry Sweep in style-guide.md before any visual review.
Limits
Limit
Value
Manifest revision
2
SVG revision
2
Total timeout
45min
Cloud Icons
Use Cloud Icons Reference. Azure diagrams must use verified img/lib/azure2/**/*.svg image paths, retain short service labels, and fall back to neutral boxes only when an icon is missing or misleading.
Enable Azure/AWS shapes (+ More Shapes → Azure / AWS)
Text overlaps near outer frame
Inset top callout 16–24px, increase height, wrap to 3–4 lines; review at actual embed width
Done Criteria
.drawio or .drawio.svg file generated
Diagram opens correctly in VS Code Draw.io extension
If an editable .drawio.svg is part of the delivery, it was exported with --embed-diagram and contains mxfile
All nodes and edges visible
User-facing links point to the editable .drawio when editability is expected
Decision flows avoid long return/merge lines that bundle branch outputs back into one sink
Quality gate score ≥ 85
If diagram is referenced from documentation, both editable source and embeddable image are provided
Render review completed at the target embed width: no text overlap, clipping, or border collisions, no edges overlapping on one line, no edge endpoint buried inside a filled box, no label riding on a box or another label, no node outside the page
After any edge or label layout change, re-export the delivery asset for the target medium (SVG for web, PNG or the final PDF for print) and inspect it; structural validation alone does not prove visual routing quality
