doctor
CommandRun one-shot environment diagnostics for Diagram Design readiness
Redraw a draw.io file as an editorial diagram at a chosen format, size, and detail level
> /plugin marketplace add cathrynlavery/diagram-design> /plugin install diagram-design@diagram-design
description: Redraw a draw.io file as an editorial diagram at a chosen format, size, and detail level argument-hint: <drawio-file> [--format=html|svg|png|html+png] [--size=<preset>] [--detail=faithful|balanced|simplified] [--audience=engineer|mixed|executive] [--type=<diagram-type>] [--page=N|NAME|all] [--variant=light|dark|full] [--output=<path>] allowed-tools: - Read - Write - Edit - Bash - Glob
Redraw the draw.io file at `$1` as a diagram in this skill's design system, following [`skills/diagram-design/references/import-drawio.md`](../skills/diagram-design/references/import-drawio.md) and [`skills/diagram-design/references/output-spec.md`](../skills/diagram-design/references/output-spec.md). Treat those references as the source of truth — don't reimplement the logic here.
Full argument string: `$ARGUMENTS`
Accepts `.drawio`, `.drawio.xml`, `.xml`, `.drawio.png`, and `.drawio.svg`.
[`SKILL.md` §3](../skills/diagram-design/SKILL.md).
1. **No file provided** → ask which `.drawio` file. Don't guess. 2. **Always locate the installed skill and run `<skill-dir>/scripts/drawio_extract.py` first.** Never assume the skill is under the current working directory, and never read a `.drawio` file directly — most are compressed, and the raw XML is noise. 3. **Extractor exits non-zero** → report its message verbatim and stop. 4. **Digest shows 0 nodes** → the source is image-only or encrypted. Say so; ask for the original file. Don't invent content. 5. **Multi-page file with no `--page`** → list the pages with their node/edge counts and ask which one. 6. **Requested detail level is impossible at the requested size** (e.g. `faithful` on a 40-node source at `slide-16x9`) → say so before drawing and propose overview + per-zone detail. 7. **`--detail=faithful` above 9 nodes** → zone the layout; above 24 nodes, split into overview + detail files. 8. **Never carry over source coordinates, colors, or fonts.** The output is a redraw in the project's `style-guide.md` skin. 9. Run the SKILL.md §9 taste gate and the `output-spec.md` §6 checklist before writing.
After writing the files, report the paths, sizes, the four dials used, and the fidelity ledger (what was merged, collapsed, or dropped).
Editorial diagram design for Claude Code, Codex, GitHub Copilot, Cursor, Factory Droid, Qoder, and Pi. 45 diagram types. Self-contained HTML + SVG. No shadows. No Mermaid slop.
Run one-shot environment diagnostics for Diagram Design readiness
Export a diagram-design HTML file to .svg and .png next to the source
Redraw an Excalidraw board as an editorial diagram at a chosen format, size, and detail level
Redraw Mermaid as an editorial diagram at a chosen format, size, and detail level
Redraw PlantUML sequence and class diagrams as an editorial diagram at a chosen format, size, and detail level
Save, load, inspect, update, reset, or delete diagram-design client profiles
Generate a concrete design system (tokens, style, type, UX) before building UI
Open a first-contribution PR (or bug issue) on nexu-io/open-design — works for non-coders too.
Strip the signatures that make a UI look AI-generated — flat hierarchy, no focal point, monotone layout, timid palettes, generic…
Head-to-head graded battle card between two sites — eight dimensions, bar-by-bar, verdict line.