← ClaudeAtlas

drawio-chartslisted

Create, edit, and validate draw.io (diagrams.net) .drawio XML diagrams — flowcharts, system/network/cloud architecture diagrams, org charts, sequence diagrams, ER/database schema diagrams. Use whenever the user asks to create or modify a draw.io or diagrams.net file, a .drawio/.dio file, or wants an architecture, process, workflow, network, schema or hierarchy drawn as an editable diagram, even if they don't say "draw.io". Also use it to convert Mermaid diagrams (flowchart, sequence, class, state, ER) into editable draw.io diagrams, including replacing ```mermaid blocks in Markdown docs with .drawio.svg images that GitHub/GitLab display. Not for data charts (bar, line, pie, scatter plots of numbers).
raulkivi/drawio-charts · ★ 0 · Data & Documents · score 72
Install: claude install-skill raulkivi/drawio-charts
# draw.io Chart Creation Generate and edit `.drawio` files directly as XML — no draw.io application is required to produce a valid diagram. The XML format (`mxfile` / `mxGraphModel` / `mxCell`) is documented in full under `references/`; this file covers what's needed for the common case. ## Workflow 1. Work out the diagram type and the entities and relationships to show. Ask only if the content is unclear; infer the type from the request. 2. Open the matching example from the table under "Diagram types" and copy its patterns. Each one encodes the shapes, styles and nesting that type needs. 3. For a flowchart, state, class, ER or sequence diagram, write a graph spec and let `layout_drawio.py` place it (see "Layout"). Otherwise work out rows, columns and coordinates before writing any cells, then write the XML from the skeleton below: one `mxCell` per shape and one per connector. 4. Style consistently: the same kind of element gets the same shape and palette entry. 5. Run `python3 <skill-dir>/scripts/validate_drawio.py <file>` and fix every issue it reports. It checks ids, parents, edge endpoints, geometry and style separators, which are the mistakes that make draw.io drop cells or refuse to open the file. Then read through the Validation checklist for what a script can't judge. 6. Mention that the user can open the file in draw.io or the `hediet.vscode-drawio` VS Code extension to see it. Don't depend on that to verify correctness. **Running the scripts.** `<skill-dir>` is