drawio
Skill10 starsChanged 4 months agoMITView on GitHub
Create draw.io overview diagrams with consistent visual style and shape mappings for BCE, package-by-layer, package-by-feature, and hexagonal Java architectures. Use when asked to create, generate, or edit draw.io diagrams, architecture diagrams, component diagrams, or visual overviews of systems and modules. Triggers on "draw.io", "drawio", "create a diagram", "architecture diagram", "component diagram", or requests to visualize high-level system structure. Not for sequence diagrams or class diagrams.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- h-wata/claude-skillstheir own version, first seen Nov 8, 2026
- shreeve1/Claude-Coworktheir own version, first seen Nov 1, 2026
- MakiDevelop/claude-skillstheir own version, first seen Nov 1, 2026
- jackzhaojin/ai-builder-kittheir own version, first seen Nov 1, 2026
- rysk-tanaka/skillstheir own version, first seen Oct 31, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
Used with
Projects with it also use excalidraw and handoff.
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.
lookfreeSkillexcalidraw
Generate architecture diagrams as .excalidraw files from codebase analysis. Use when the user asks to create architecture diagrams, system diagrams, visualize codebase structure, or generate excalidraw files.
Also in 3 projects that use this
MicrosoftSkillhandoff
Compact the current conversation into a handoff document for another agent to pick up.
Also in 4 projects that use this
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- github/awesome-copilot★ 41ksame name
- sparklabx/drawio-ai-kit★ 657same name
- Chanw-research/claude-code-paper-writing★ 42same name
- scarr05/claude-skills-pub★ 16same name
- roeyw5/claude-code-guide★ 9same name
- akiojin/skills★ 8same name
- MakiDevelop/claude-skills★ 3same name
- norandom/Skills★ 3same name
- ikkeseb/skills★ 2same name
- jablonkai/skills★ 2same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- conventional-commitSkill
- diagramsSkill
- java-conventionsSkill
- java-distillerSkill
- mermaidSkill
- microprofile-serverSkill
- migrate-to-bceSkill
- quarkus-jnosqlSkill
- sdd4j-bceSkill
- sdd4j-ears-testsSkill
- sdd4j-hexagonalSkill
- sdd4j-package-by-featureSkill
- sdd4j-package-by-layerSkill
- sdd4jSkill
- slddSkill
- spring-boot-serverSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 7 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
7
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
when invoked via diagrams, use the architecture it detected — the router is architecture-neutral
- Distinctive: line 18
no clear architecture → use the Default mapping
- Distinctive: line 19
never mix mappings inside one diagram
- Distinctive: line 52
Use when no architecture mapping applies.
- Distinctive: line 133
avoid crossing lines where possible
- Very specific: line 134
use container shapes (container=1;) for subsystem, layer, or module grouping
- Very specific: line 135
if a node blends into its container's fill (e.g.
- Very specific: line 136
default node size: width=160;height=60.
- Distinctive: line 140
use short, descriptive names
- Distinctive: line 141
avoid technical jargon unless domain-specific
- Distinctive: line 144
do not use italic font
“Common” is measured: kept by at least 6 in 10 of the 19 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.
Files
Draw.io Overview Diagrams
Generate valid draw.io XML and save as <name>.drawio using the Write tool.
Mapping Selection
- pick the shape mapping matching the architecture the user named or the composed skill implies:
- BCE business components, or
sdd4j-bcein context → BCE mapping - technical layer packages, or
sdd4j-package-by-layerin context → Package By Layer mapping - feature/capability packages, or
sdd4j-package-by-featurein context → Package By Feature mapping - ports-and-adapters layout, or
sdd4j-hexagonalin context → Hexagonal mapping
- BCE business components, or
- when invoked via
diagrams, use the architecture it detected — the router is architecture-neutral - no clear architecture → use the Default mapping
- never mix mappings inside one diagram
Lines
- rounded routing:
edgeStyle=orthogonalEdgeStyle;rounded=1; - black stroke:
strokeColor=#000000; - arrow at target:
endArrow=block;endFill=1; - async/optional dependencies: add
dashed=1; - label without shadow:
shadow=0;on the label cell - when an edge crosses container boundaries (source or target is nested in a container), pin explicit
exitX/exitYon the source andentryX/entryYon the target so the orthogonal router does not take ugly paths; when multiple edges share a target, give each a distinct entry point to prevent overlap
Style
- all nodes:
rounded=1;whiteSpace=wrap;html=1;shadow=1; - corner radius:
arcSize=10; - font:
fontColor=#000000;fontSize=13;fontStyle=0; - grouping: container with title bar (
container=1;collapsible=0;verticalAlign=top;), fill#f5f5f5, border#666666
Palette
Colors carry the same meaning across all mappings — and match the mermaid skill, so mixed-format diagrams stay visually consistent:
| Color | Fill | Border | Meaning |
| Blue | #dae8fc | #6c8ebf | capability / business component |
| Green | #d5e8d4 | #82b366 | entrypoint / boundary |
| Purple | #e1d5e7 | #9673a6 | application / control |
| Yellow | #fff2cc | #d6b656 | domain / entity |
| Gray | #f5f5f5 | #666666 | infrastructure / shared / grouping container |
| Dashed yellow | #fff2cc | #d6b656 dashed | external service |
Default Mapping
Use when no architecture mapping applies.
| Element | Shape | Fill | Border |
| Component | rounded rectangle | #dae8fc | #6c8ebf |
| Grouping | container with title bar | #f5f5f5 | #666666 |
| External service | rounded rectangle, dashed=1 | #fff2cc | #d6b656 |
BCE Mapping
| Element | Shape | Fill | Border |
| Business Component (BC) | rounded rectangle | #dae8fc | #6c8ebf |
| Subsystem container | container with title bar | #f5f5f5 | #666666 |
| External service | rounded rectangle, dashed=1 | #fff2cc | #d6b656 |
| Boundary layer | rounded rectangle | #d5e8d4 | #82b366 |
| Control layer | rounded rectangle | #e1d5e7 | #9673a6 |
| Entity layer | rounded rectangle | #fff2cc | #d6b656 |
BCE Robustness Icons (built-in)
Drawio ships with the Jacobson BCE icons. Use these — never reconstruct them from primitives (lines + ellipses + triangles).
- Boundary Object:
shape=umlBoundary;whiteSpace=wrap;html=1; - Control Object:
ellipse;shape=umlControl;whiteSpace=wrap;html=1; - Entity Object:
ellipse;shape=umlEntity;whiteSpace=wrap;html=1;
Color them by adding fillColor=#ffffff;strokeColor=<layer-border>;. Typical icon size: width=30;height=32. These icons are BCE-specific — do not use them in other mappings.
Package By Layer Mapping
Layers are containers; nodes are the capability's classes inside each layer.
| Element | Shape | Fill | Border |
| Capability (spec contract) | rounded rectangle | #dae8fc | #6c8ebf |
| Layer grouping | container with title bar | #f5f5f5 | #666666 |
| Entrypoint (controller, resource, handler, listener, CLI) | rounded rectangle | #d5e8d4 | #82b366 |
| Application operation (service, use case) | rounded rectangle | #e1d5e7 | #9673a6 |
| Domain/model type (entity, model, DTO) | rounded rectangle | #fff2cc | #d6b656 |
| Infrastructure (repository, client, adapter) | rounded rectangle | #f5f5f5 | #666666 |
| External service | rounded rectangle, dashed=1 | #fff2cc | #d6b656 |
Package By Feature Mapping
Nodes are feature packages; containers group by module or base package. Drawing inside a feature package reuses the element styles from the Package By Layer mapping.
| Element | Shape | Fill | Border |
| Feature package (capability) | rounded rectangle | #dae8fc | #6c8ebf |
| Module grouping | container with title bar | #f5f5f5 | #666666 |
| Shared package (declared exception) | rounded rectangle, dashed=1 | #f5f5f5 | #666666 |
| External service | rounded rectangle, dashed=1 | #fff2cc | #d6b656 |
Hexagonal (Ports & Adapters) Mapping
Nodes are adapters, ports, use cases, and domain types. Lay out driving side left, driven side right; the hexagon boundary is a shape=hexagon container (container=1) holding ports, use cases, and domain when expanding a component, or a plain shape=hexagon node per capability in system view. Edges show call flow through ports — interface indirection is elided.
| Element | Shape | Fill | Border |
| Capability core | shape=hexagon (node, or container=1 boundary) | #dae8fc | #6c8ebf |
| Driving adapter (REST resource, consumer, CLI, scheduler) | rounded rectangle | #d5e8d4 | #82b366 |
| Inbound port (use case interface) | rounded rectangle | #e1d5e7 | #9673a6 |
| Use case / application service | rounded rectangle | #e1d5e7 | #9673a6 |
| Domain type | rounded rectangle | #fff2cc | #d6b656 |
| Outbound port | rounded rectangle | #e1d5e7 | #9673a6 |
| Driven adapter (persistence, client, publisher) | rounded rectangle | #f5f5f5 | #666666 |
| External service | rounded rectangle, dashed=1 | #fff2cc | #d6b656 |
Content
- visualize only high-level concepts and modules
- show dependencies between components as directed arrows
- omit implementation details, classes, and methods
- group related components visually
- limit diagram to essential relationships
Layout
- arrange components in logical flow (top-to-bottom or left-to-right)
- consistent spacing: 40px between nodes, 20px padding inside containers
- avoid crossing lines where possible
- use container shapes (
container=1;) for subsystem, layer, or module grouping - if a node blends into its container's fill (e.g. gray infrastructure inside a gray layer container), set
fillColor=noneon the container - default node size:
width=160;height=60;
Labels
- use short, descriptive names
- avoid technical jargon unless domain-specific
- label arrows only when relationship type is ambiguous
- black font color for all labels
- do not use italic font
- connection labels must be without shadow
- connection labels must use
fontSize=16;
XML Structure
Minimal skeleton — every .drawio file must follow this hierarchy:
<mxfile>
<diagram name="Overview" id="diag1">
<mxGraphModel dx="1024" dy="768" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
<root>
<mxCell id="0"/>
<mxCell id="1" parent="0"/>
<!-- nodes and edges here, parent="1" -->
</root>
</mxGraphModel>
</diagram>
</mxfile>Example — Minimal 2-Node BCE Diagram
<mxfile>
<diagram name="Overview" id="d1">
<mxGraphModel dx="1024" dy="768" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1169" pageHeight="827" math="0" shadow="0">
<root>
<mxCell id="0"/>
<mxCell id="1" parent="0"/>
<mxCell id="2" value="Orders" style="rounded=1;whiteSpace=wrap;html=1;shadow=1;arcSize=10;fillColor=#dae8fc;strokeColor=#6c8ebf;fontColor=#000000;fontSize=13;fontStyle=0;" vertex="1" parent="1">
<mxGeometry x="100" y="200" width="160" height="60" as="geometry"/>
</mxCell>
<mxCell id="3" value="Payments" style="rounded=1;whiteSpace=wrap;html=1;shadow=1;arcSize=10;fillColor=#dae8fc;strokeColor=#6c8ebf;fontColor=#000000;fontSize=13;fontStyle=0;" vertex="1" parent="1">
<mxGeometry x="380" y="200" width="160" height="60" as="geometry"/>
</mxCell>
<mxCell id="4" value="charges" style="edgeStyle=orthogonalEdgeStyle;rounded=1;orthogonalLoop=1;strokeColor=#000000;fontColor=#000000;fontSize=16;fontStyle=0;endArrow=block;endFill=1;shadow=0;" edge="1" source="2" target="3" parent="1">
<mxGeometry relative="1" as="geometry"/>
</mxCell>
</root>
</mxGraphModel>
</diagram>
</mxfile>File Output
- save as
<name>.drawiousing the Write tool - see
references/example-bce.drawio,references/example-layered.drawio,references/example-feature.drawio, andreferences/example-hexagonal.drawiofor complete per-mapping examples
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

