agentleFS
tam159tam159/next-role/.claude/skills/drawio-skill/SKILL.md

drawio-skill

Skill67 starsChanged 16 days agoMITView on GitHub

Create and edit draw.io/diagrams.net diagrams as editable `.drawio` files. Covers architecture, UML/ERD/sequence, BPMN, network, and swimlane views authored from a description or converted from code, IaC, SQL, and API schemas, plus sync, query, test, review, export, and publish of existing diagrams. Use when the user asks for draw.io/diagrams.net or an editable diagram; prefer Mermaid/PlantUML when diagrams-as-code is enough.

18 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use find-skills.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • VercelSkill

    find-skills

    Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

18 rules. 0 are common, 7 are distinctive, and 11 are very specific to this project.

  • 0

    Common

    Most of the 17 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 11

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run from this skill directory, or replace scripts/ with the absolute path to this skill's scripts directory:

    line 45
  2. Very specific:

    When semantic metadata or an architecture policy is in scope, also run diagramctl.py test.

    line 85
  3. Very specific:

    When the drawio binary is unavailable or a visual check is inconclusive, verify the renderer's own DOM instead (--dump-dom on the viewer …

    line 91
  4. Distinctive:

    After approval, create final requested formats and report both editable source and export paths.

    line 99
  5. Very specific:

    Do not combine --width and -s.

    line 120
  6. Very specific:

    If the CLI crashes in a macOS sandbox, try one permitted escalated run, then use encode_drawio_url.py or deliver XML.

    line 123
  7. Very specific:

    Use stable semantic IDs and never reuse reserved IDs 0 or 1.

    line 128
  8. Very specific:

    Every edge requires <mxGeometry relative="1" as="geometry"/>.

    line 129
  9. Very specific:

    Keep provenance, data-model-id, semantic properties, manual geometry, and manual styles intact unless the user requests otherwise.

    line 132
  10. Distinctive:

    When reconciling, retain removals as reviewable faded elements by default.

    line 134
  11. Very specific:

    Multi-Page Separation: When the scope spans multiple major views (e.g., deployment, data paths, execution, authentication), use a separate …

    line 155
  12. Distinctive:

    Optimized Spacing: Start with edge-to-edge gaps of 150–200 px between sequential stages and 100–120 px between parallel nodes.

    line 163
  13. Distinctive:

    Container Padding: Start with 40–60 px between container borders and child nodes, reserving extra space for titles and connector routes.

    line 166
  14. Very specific:

    Node Sizing: Use consistent dimensions for comparable service boxes (e.g., 160 × 90 px), expanding for labels.

    line 168
  15. Very specific:

    Cloud Services: When the user names a cloud provider (e.g., "in AWS"), prefer suitable services and matching available icons …

    line 174
  16. Distinctive:

    Consistent Visual Language: Use the user's preferred page or example as the visual reference for all views.

    line 177
  17. Distinctive:

    Icons in Flow Views: Prefer labeled icon-and-text service cards connected by concise, optionally numbered actions.

    line 181
  18. Distinctive:

    Keep application roles distinct from their hosting services, and preserve sequence/state notation when needed.

    line 184

“Common” is measured: kept by at least 6 in 10 of the 17 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Draw.io Architecture Studio

Produce editable .drawio artifacts, not flattened pictures. The preferred entrypoint is scripts/diagramctl.py, which unifies generation, incremental sync, multi-view projection, semantic queries/tests/reviews, failure analysis, and accessible publishing over a shared Diagram IR.

Choose the workflow

RequestRoute
Natural-language diagram with precise stylingRead references/diagram-types.md, then references/xml-authoring.md and author XML
Standard flowchart/mindmap/gantt/timeline/etc. with no special stylingIf draw.io >=30, read references/mermaid-authoring.md and convert Mermaid to native .drawio
Large graph (~15+ nodes) that needs automatic layoutUse autolayout.py; read references/autolayout.md before passing any --layout value
Code, Terraform, K8s, compose, SQL, OpenAPI, AsyncAPI, or CI sourceUse diagramctl.py build; read references/diagram-ir.md
Protocol Buffers schema (.proto)Use protoimports.py or diagramctl.py build; read references/toolbox.md
GraphQL SDL schema (.graphql/.gql) or introspection JSONUse graphqlerd.py or diagramctl.py build; read references/toolbox.md
Running cluster/stack/cloud (actual state, not declared config)Read references/live-infra.md, then use tfstate.py, dockerimports.py, or k8simports.py -
Update a generated diagram without losing manual layoutUse diagramctl.py sync; read references/diagram-ir.md
Executive/system/deployment/data-flow/security viewsUse diagramctl.py views; read references/diagram-ir.md
Query, architecture policy, review, what-if, or guided walkthroughRead references/semantic-workflows.md
MCP host (Claude Desktop, Cursor, VS Code, Codex) should call these workflowsRegister scripts/diagramctl_mcp.py; read references/mcp.md
Prompt phrasing for a diagram type or semantic workflowRead references/cookbook.md
Enforce architecture rules or visual diffs in GitHub Actions CIRead references/ci-gate.md
Rendered before/after/diff images as a PR review commentUse prdiff.py; read references/pr-bot.md
Existing .drawio to HTML/PPTX/Mermaid/Markdown/animation/runbookRead references/toolbox.md; diagramctl.py transform exposes the existing tools
Pipeline, journey, or subsystem map drawn as a metro/subway mapUse tubemap.py; read references/tubemap.md
Shape, cloud/vendor, AI, or Databricks iconRead references/shapes.md or references/databricks.md; never guess shape names
Learn/apply/manage a visual styleRead references/style-presets.md
Extract a reusable style from an existing diagram or themeRead references/style-extraction.md
Existing image to editable diagram (screenshot, whiteboard photo, legacy PNG)Read references/derasterize.md
Export/platform problemRead references/troubleshooting.md; for access/network questions read references/security.md

Unified CLI

Run from this skill directory, or replace scripts/ with the absolute path to this skill's scripts directory:

python3 scripts/diagramctl.py doctor
python3 scripts/diagramctl.py build model.json --from ir -o architecture.drawio
python3 scripts/diagramctl.py build ./infra --from terraform --group \
  --ir-output architecture.ir.json -o architecture.drawio
python3 scripts/diagramctl.py sync architecture.drawio ./infra --from terraform \
  -o architecture.next.drawio
python3 scripts/diagramctl.py views architecture.ir.json \
  --views executive,system,deployment,dataflow,security -o views.drawio
python3 scripts/diagramctl.py test architecture.drawio --rules policy.yml
python3 scripts/diagramctl.py review architecture.drawio -o review.md
python3 scripts/diagramctl.py query architecture.drawio --from internet --to orders-db
python3 scripts/diagramctl.py whatif architecture.ir.json --fail kafka \
  --drawio kafka-failure.drawio -o impact.json
python3 scripts/diagramctl.py story architecture.ir.json -o walkthrough.html

doctor does not launch GUI tools unless --probe is passed. Core semantic commands are offline and stdlib-only.

Creation workflow

  1. Infer the diagram type, audience, scope, output format, and location from the request. Ask only when a missing choice materially changes the result; default to PNG plus .drawio in the working directory.
  2. Select the authoring route from the table above. For a data-backed diagram, prefer Diagram IR and preserve provenance. For a large graph, use an importer or autolayout.py; do not hand-place more than roughly fifteen nodes.
  3. Resolve an explicitly named style preset, or the user's default preset, as documented in references/style-presets.md. Structural diagram conventions and visual presets compose; they do not replace each other.
  4. Generate the .drawio, then run structural validation:

    python3 scripts/validate.py diagram.drawio --score

    When semantic metadata or an architecture policy is in scope, also run diagramctl.py test. Do not present inferred semantic findings as verified runtime facts.

  5. Export a draft PNG without embedded XML and inspect it visually. Fix obvious overlap, clipping, disconnected edges, edge-through-node routing, stacked edges, and unreadable labels. Stop automatic vision repair after two rounds. When the drawio binary is unavailable or a visual check is inconclusive, verify the renderer's own DOM instead (--dump-dom on the viewer URL, see references/troubleshooting.md): read each edge's <path> segments and label anchor coordinates directly — vision alone both misses geometry defects and hallucinates new ones.
  6. Show the draft and apply targeted edits. Preserve existing geometry for local changes. Use sync for source-backed changes and write a reviewable output; use --prune only when deletion was requested.
  7. After approval, create final requested formats and report both editable source and export paths.

Export invariants

Resolve the available binary once (drawio, draw.io, the macOS app path, or the Windows executable) and use that exact binary for the run.

# Draft for visual inspection: never use -e here
drawio -x -f png --width 2000 -o diagram.png diagram.drawio

# Final editable PNG
drawio -x -f png -e -s 2 -o diagram.drawio.png diagram.drawio
python3 scripts/repair_png.py diagram.drawio.png

# Final editable SVG/PDF
drawio -x -f svg -e --embed-svg-images -o diagram.svg diagram.drawio
drawio -x -f pdf -e -o diagram.pdf diagram.drawio

Do not combine --width and -s. Embedded PNG exports require repair_png.py; draft PNGs used by vision must not use -e. On Linux headless, follow references/troubleshooting.md rather than improvising Electron flags. If the CLI crashes in a macOS sandbox, try one permitted escalated run, then use encode_drawio_url.py or deliver XML; do not repeatedly launch it.

Editing and identity

  • Use stable semantic IDs and never reuse reserved IDs 0 or 1.
  • Every edge requires <mxGeometry relative="1" as="geometry"/>.
  • For a local edit, change the matching cell only; for a global direction change, regenerate/re-layout the page.
  • Keep provenance, data-model-id, semantic properties, manual geometry, and manual styles intact unless the user requests otherwise.
  • When reconciling, retain removals as reviewable faded elements by default.
  • For edges stacked at a boundary, run edgeports.py; add waypoints when an edge still crosses an unrelated shape. There is no CLI-only edge rerouter that preserves node positions.

Quality and trust

An attractive diagram can still be wrong. Prefer source-backed relationships, show provenance where useful, distinguish exact extraction from AI inference, and keep architecture review findings framed as prompts. Story HTML must remain self-contained, keyboard usable, and include a text alternative. Never include secrets in node properties or provenance because they are embedded in outputs.

For all focused scripts and composition patterns, read references/toolbox.md; load only the task-specific reference needed for the current request.

Architectural Views & Spatial Constraints

Apply these defaults to new architecture views; honor the requested scope, diagram conventions, and style preset. Preserve existing geometry for local edits.

  1. Multi-Page Separation: When the scope spans multiple major views (e.g., deployment, data paths, execution, authentication), use a separate page/tab for each. Keep a focused diagram on one page; use diagramctl.py views for IR-backed multi-view output.
  2. Self-Contained Pages: Include enough context and labeled relationships to understand each page independently. Use orthogonal connectors (edgeStyle=orthogonalEdgeStyle;rounded=1;) where diagram conventions allow; use arrowheads only when the relationship is directional.
  3. Optimized Spacing: Start with edge-to-edge gaps of 150–200 px between sequential stages and 100–120 px between parallel nodes. Adjust for labels, routing, and compactness; avoid overlaps and excessive empty space.
  4. Container Padding: Start with 40–60 px between container borders and child nodes, reserving extra space for titles and connector routes.
  5. Node Sizing: Use consistent dimensions for comparable service boxes (e.g., 160 × 90 px), expanding for labels. Preserve vendor icon dimensions and aspect ratios from references/shapes.md.
  6. Coordinate Planning: Plan grouping and routing before generation. For small, hand-authored views, calculate coordinates explicitly; for larger graphs, use the importer or automatic-layout workflow above, then inspect the result.
  7. Cloud Services: When the user names a cloud provider (e.g., "in AWS"), prefer suitable services and matching available icons (references/shapes.md) across all relevant pages; preserve source-backed facts and label proposals.
  8. Consistent Visual Language: Use the user's preferred page or example as the visual reference for all views. Reuse component names, icons, colors, and card styling across deployment, data, execution, streaming, and authentication pages; adapt layout to each view without repeating the entire deployment topology.
  9. Icons in Flow Views: Prefer labeled icon-and-text service cards connected by concise, optionally numbered actions. Reuse each service's icon wherever it appears; use accurate generic symbols when no matching vendor icon exists. Keep application roles distinct from their hosting services, and preserve sequence/state notation when needed. Inspect every page for this consistency.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.