diagramming
Generate Excalidraw diagrams. Use when creating flowcharts, ER diagrams, sequence diagrams, block diagrams, or any .excalidraw files.
When & Why to Use This Skill
This Claude skill automates the generation of professional Excalidraw diagrams, enabling users to create flowcharts, ER diagrams, and sequence diagrams through simple text prompts. By producing valid .excalidraw JSON files with precise layout logic and styling, it streamlines the visual documentation process for developers and architects.
Use Cases
- System Architecture: Automatically generate sequence diagrams and block diagrams to visualize complex software interactions and microservices infrastructure.
- Database Modeling: Create detailed Entity-Relationship (ER) diagrams to map out data structures, primary keys, and table relationships during the design phase.
- Workflow Visualization: Design clear, professional flowcharts to document business logic, user journeys, or CI/CD pipeline processes.
- Technical Documentation: Enhance project READMEs and internal wikis by generating high-quality, editable visual assets that improve team communication and onboarding.
| name | diagramming |
|---|---|
| description | Generate Excalidraw diagrams. Use when creating flowcharts, ER diagrams, sequence diagrams, block diagrams, or any .excalidraw files. |
Diagramming with Excalidraw
Generate valid .excalidraw JSON files.
File Format
{
"type": "excalidraw",
"version": 2,
"source": "https://excalidraw.com",
"elements": [],
"appState": {
"viewBackgroundColor": "#ffffff"
},
"files": {}
}
| Field | Type | Description |
|---|---|---|
type |
string | Always "excalidraw" |
version |
number | Schema version (currently 2) |
source |
string | Origin URL |
elements |
array | All diagram elements |
appState |
object | Canvas settings (background, etc.) |
files |
object | Binary files keyed by fileId (images) |
Workflow
- Plan - Choose diagram type, layout, colors
- Generate - Create elements with proper structure
- Validate - Check bindings and structure before writing
Validation Checklist
Before writing a diagram, verify:
Bindings
- Arrows connecting shapes have both
startBindingandendBindingset - Arrow
x,ysits at the source shape's edge, not floating in space - Shapes list connected arrows in their
boundElements(bidirectional) - Text labels have
containerIdpointing to their container - Containers have
boundElementsreferencing their text
Polygons
- Polygon labels use
groupIds(notcontainerId) - Text positioned manually at polygon center
- Polygons cannot have arrow bindings - bind to grouped text label instead
- Polygon's
boundElementsmust benull
Layout
- Elements don't overlap unexpectedly
- Arrows route around shapes, not through them
- Minimum 40px between sibling elements
- All IDs are unique
- Label text matches actual names (verify spelling)
Text
- Use standard font sizes: S (16), M (20), L (28), XL (36)
- Bound text: set
containerId,textAlign: "center",verticalAlign: "middle" - Position bound text at container center; Excalidraw adjusts automatically
Frames (presentations only)
- Frames are slides/artboards, not for grouping elements in a single diagram
Reference Index
Load references progressively based on need:
Elements
| Reference | Load When |
|---|---|
| shapes.md | Using rectangles, diamonds, ellipses |
| text.md | Adding labels, fonts, text styling |
| linear.md | Creating arrows, lines, bindings |
| freedraw.md | Hand-drawn paths |
| images.md | Embedding images |
| frames.md | Slides/artboards for presentations |
| polygons.md | Custom polygon shapes |
Styling
| Reference | Load When |
|---|---|
| fill-stroke.md | Fill patterns, strokes |
| colors.md | Color palette selection |
| positioning.md | Layout, alignment, spacing |
| grouping.md | Groups, z-ordering |