agentleFS
nearthinknearthink/agent-skills/skills/excalidraw-diagram-generator/SKILL.md

excalidraw-diagram-generator

Skill0 starsChanged 8 months agoMITView on GitHub

Generates Excalidraw-format diagrams from natural language descriptions. Invoke when user asks to create diagrams, flowcharts, mind maps, architecture diagrams, or any visual representation.

12 other projects use a version of this, 11 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use receiving-code-review, executing-plans and 5 more.

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.
  • CloudflareSkill

    receiving-code-review

    Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

    Also in 5 projects that use this

  • OpenAISkill

    executing-plans

    Use when you have a written implementation plan to execute in a separate session with review checkpoints

    Also in 5 projects that use this

  • OpenAISkill

    requesting-code-review

    Use when completing tasks, implementing major features, or before merging to verify work meets requirements

    Also in 5 projects that use this

  • GoogleSkill

    improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

    Also in 7 projects that use this

  • VercelSkill

    remotion-best-practices

    Best practices for Remotion - Video creation in React

    Also in 3 projects that use this

  • VercelSkill

    web-design-guidelines

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".

    Also in 5 projects that use this

  • +1 more from openai

The file

We split this skill into the rules it gives an agent

9 rules. 7 are common, 2 are distinctive, and 0 are very specific to this project.

  • 7

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill when users request:

    line 12
  2. Common:

    Start and end points

    line 65
  3. Common:

    Create the .excalidraw file with appropriate elements:

    line 116
  4. Common:

    Important: All text elements must use fontFamily: 5 (Excalifont) for consistent visual appearance.

    line 133
  5. Distinctive:

    Start positions: Center important elements, use consistent spacing

    line 176
  6. Distinctive:

    If user request has too many elements:

    line 191
  7. Common:

    Create flowchart with 4 rectangles + 3 arrows

    line 212
  8. Common:

    Use timestamp + random string for unique IDs:

    line 264
  9. Common:

    Before delivering the diagram:

    line 294

“Common” is measured: kept by at least 6 in 10 of the 11 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

Excalidraw Diagram Generator

A skill for generating Excalidraw-format diagrams from natural language descriptions. This skill helps create visual representations of processes, systems, relationships, and ideas without manual drawing.

When to Use This Skill

Use this skill when users request:

  • "Create a diagram showing..."
  • "Make a flowchart for..."
  • "Visualize the process of..."
  • "Draw the system architecture of..."
  • "Generate a mind map about..."
  • "Create an Excalidraw file for..."
  • "Show the relationship between..."
  • "Diagram the workflow of..."

Supported Diagram Types

  • Flowcharts: Sequential processes, workflows, decision trees
  • Relationship Diagrams: Entity relationships, system components, dependencies
  • Mind Maps: Concept hierarchies, brainstorming results, topic organization
  • Architecture Diagrams: System design, module interactions, data flow
  • Data Flow Diagrams (DFD): Data flow visualization, data transformation processes
  • Business Flow (Swimlane): Cross-functional workflows, actor-based process flows
  • Class Diagrams: Object-oriented design, class structures and relationships
  • Sequence Diagrams: Object interactions over time, message flows
  • ER Diagrams: Database entity relationships, data models

Step-by-Step Workflow

Step 1: Understand the Request

Analyze the user's description to determine:

  • Diagram type (flowchart, relationship, mind map, architecture)
  • Key elements (entities, steps, concepts)
  • Relationships (flow, connections, hierarchy)
  • Complexity (number of elements)

Step 2: Choose the Appropriate Diagram Type

User IntentDiagram TypeExample Keywords
Process flow, steps, proceduresFlowchart"workflow", "process", "steps", "procedure"
Connections, dependencies, associationsRelationship Diagram"relationship", "connections", "dependencies", "structure"
Concept hierarchy, brainstormingMind Map"mind map", "concepts", "ideas", "breakdown"
System design, componentsArchitecture Diagram"architecture", "system", "components", "modules"
Data flow, transformation processesData Flow Diagram (DFD)"data flow", "data processing", "data transformation"
Cross-functional processes, actor responsibilitiesBusiness Flow (Swimlane)"business process", "swimlane", "actors", "responsibilities"
Object-oriented design, class structuresClass Diagram"class", "inheritance", "OOP", "object model"
Interaction sequences, message flowsSequence Diagram"sequence", "interaction", "messages", "timeline"
Database design, entity relationshipsER Diagram"database", "entity", "relationship", "data model"

Step 3: Extract Structured Information

For Flowcharts:

  • List of sequential steps
  • Decision points (if any)
  • Start and end points

For Relationship Diagrams:

  • Entities/nodes (name + optional description)
  • Relationships between entities (from -> to, with label)

For Mind Maps:

  • Central topic
  • Main branches (3-6 recommended)
  • Sub-topics for each branch (optional)

For Data Flow Diagrams (DFD):

  • Data sources and destinations (external entities)
  • Processes (data transformations)
  • Data stores (databases, files)
  • Data flows (arrows showing data movement from left-to-right or from top-left to bottom-right)
  • Important: Do not represent process order, only data flow

For Business Flow (Swimlane):

  • Actors/roles (departments, systems, people) - displayed as header columns
  • Process lanes (vertical lanes under each actor)
  • Process boxes (activities within each lane)
  • Flow arrows (connecting process boxes, including cross-lane handoffs)

For Class Diagrams:

  • Classes with names
  • Attributes with visibility (+, -, #)
  • Methods with visibility and parameters
  • Relationships: inheritance (solid line + white triangle), implementation (dashed line + white triangle), association (solid line), dependency (dashed line), aggregation (solid line + white diamond), composition (solid line + filled diamond)
  • Multiplicity notations (1, 0..1, 1..*, *)

For Sequence Diagrams:

  • Objects/actors (arranged horizontally at top)
  • Lifelines (vertical lines from each object)
  • Messages (horizontal arrows between lifelines)
  • Synchronous messages (solid arrow), asynchronous messages (dashed arrow)
  • Return values (dashed arrows)
  • Activation boxes (rectangles on lifelines during execution)
  • Time flows from top to bottom

For ER Diagrams:

  • Entities (rectangles with entity names)
  • Attributes (listed inside entities)
  • Primary keys (underlined or marked with PK)
  • Foreign keys (marked with FK)
  • Relationships (lines connecting entities)
  • Cardinality: 1:1 (one-to-one), 1:N (one-to-many), N:M (many-to-many)
  • Junction/associative entities for many-to-many relationships (dashed rectangles)

Step 4: Generate the Excalidraw JSON

Create the .excalidraw file with appropriate elements:

Available element types:

  • rectangle: Boxes for entities, steps, concepts
  • ellipse: Alternative shapes for emphasis
  • diamond: Decision points
  • arrow: Directional connections
  • text: Labels and annotations

Key properties to set:

  • Position: x, y coordinates
  • Size: width, height
  • Style: strokeColor, backgroundColor, fillStyle
  • Font: fontFamily: 5 (Excalifont - required for all text elements)
  • Text: Embedded text for labels
  • Connections: points array for arrows

Important: All text elements must use fontFamily: 5 (Excalifont) for consistent visual appearance.

Step 5: Format the Output

Structure the complete Excalidraw file:

{
  "type": "excalidraw",
  "version": 2,
  "source": "https://excalidraw.com",
  "elements": [
    // Array of diagram elements
  ],
  "appState": {
    "viewBackgroundColor": "#ffffff",
    "gridSize": 20
  },
  "files": {}
}

Step 6: Save and Provide Instructions

  • Save as <descriptive-name>.excalidraw
  • Inform user how to open:

Best Practices

Element Count Guidelines

Diagram TypeRecommended CountMaximum
Flowchart steps3-1015
Relationship entities3-812
Mind map branches4-68
Mind map sub-topics per branch2-46

Layout Tips

  • Start positions: Center important elements, use consistent spacing
  • Spacing:
    • Horizontal gap: 200-300px between elements
    • Vertical gap: 100-150px between rows
  • Colors: Use consistent color scheme
    • Primary elements: Light blue (#a5d8ff)
    • Secondary elements: Light green (#b2f2bb)
    • Important/Central: Yellow (#ffd43b)
    • Alerts/Warnings: Light red (#ffc9c9)
  • Text sizing: 16-24px for readability
  • Font: Always use fontFamily: 5 (Excalifont) for all text elements
  • Arrow style: Use straight arrows for simple flows, curved for complex relationships

Complexity Management

If user request has too many elements:

  1. Suggest breaking into multiple diagrams
  2. Focus on main elements first
  3. Offer to create detailed sub-diagrams

Example response: "Your request includes 15 components. For clarity, I recommend:

  1. High-level architecture diagram (6 main components)
  2. Detailed diagram for each subsystem

Would you like me to start with the high-level view?"

Example Prompts and Responses

Example 1: Simple Flowchart

User: "Create a flowchart for user registration"

Agent generates:

  • Extract steps: "Enter email" -> "Verify email" -> "Set password" -> "Complete"
  • Create flowchart with 4 rectangles + 3 arrows
  • Save as user-registration-flow.excalidraw

Example 2: Relationship Diagram

User: "Diagram the relationship between User, Post, and Comment entities"

Agent generates:

  • Entities: User, Post, Comment
  • Relationships: User -> Post ("creates"), User -> Comment ("writes"), Post -> Comment ("contains")
  • Save as user-content-relationships.excalidraw

Example 3: Mind Map

User: "Mind map about machine learning concepts"

Agent generates:

  • Center: "Machine Learning"
  • Branches: Supervised Learning, Unsupervised Learning, Reinforcement Learning, Deep Learning
  • Sub-topics under each branch
  • Save as machine-learning-mindmap.excalidraw

Troubleshooting

IssueSolution
Elements overlapIncrease spacing between coordinates
Text doesn't fit in boxesIncrease box width or reduce font size
Too many elementsBreak into multiple diagrams
Unclear layoutUse grid layout (rows/columns) or radial layout (mind maps)
Colors inconsistentDefine color palette upfront based on element types

Advanced Techniques

Grid Layout (for Relationship Diagrams)

const columns = Math.ceil(Math.sqrt(entityCount));
const x = startX + (index % columns) * horizontalGap;
const y = startY + Math.floor(index / columns) * verticalGap;

Radial Layout (for Mind Maps)

const angle = (2 * Math.PI * index) / branchCount;
const x = centerX + radius * Math.cos(angle);
const y = centerY + radius * Math.sin(angle);

Auto-generated IDs

Use timestamp + random string for unique IDs:

const id = Date.now().toString(36) + Math.random().toString(36).substr(2);

Output Format

Always provide:

  • Complete .excalidraw JSON file
  • Summary of what was created
  • Element count
  • Instructions for opening/editing

Example summary:

Created: user-workflow.excalidraw
Type: Flowchart
Elements: 7 rectangles, 6 arrows, 1 title text
Total: 14 elements

To view:
1. Visit https://excalidraw.com
2. Drag and drop user-workflow.excalidraw
3. Or use File -> Open in Excalidraw VS Code extension

Validation Checklist

Before delivering the diagram:

  • All elements have unique IDs
  • Coordinates prevent overlapping
  • Text is readable (font size 16+)
  • All text elements use fontFamily: 5 (Excalifont)
  • Arrows connect logically
  • Colors follow consistent scheme
  • File is valid JSON
  • Element count is reasonable (<20 for clarity)

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.