excalidraw-diagram-generator

Name: excalidraw-diagram-generator
Author: github

27kinstalls4.6kforks

How to install excalidraw-diagram-generator?

github/awesome-copilot/excalidraw-diagram-generator

$npx -y skills add github/awesome-copilot --skill excalidraw-diagram-generator

Installs into the current project.

Summary

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind

Files · 1

View on GitHub

SKILL.md

1	# Excalidraw Diagram Generator
2
3	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.
4
5	## When to Use This Skill
6
7	Use this skill when users request:
8
9	- "Create a diagram showing..."
10	- "Make a flowchart for..."
11	- "Visualize the process of..."
12	- "Draw the system architecture of..."
13	- "Generate a mind map about..."
14	- "Create an Excalidraw file for..."
15	- "Show the relationship between..."
16	- "Diagram the workflow of..."
17
18	Supported diagram types:
19	- 📊 Flowcharts: Sequential processes, workflows, decision trees
20	- 🔗 Relationship Diagrams: Entity relationships, system components, dependencies
21	- 🧠 Mind Maps: Concept hierarchies, brainstorming results, topic organization
22	- 🏗️ Architecture Diagrams: System design, module interactions, data flow
23	- 📈 Data Flow Diagrams (DFD): Data flow visualization, data transformation processes
24	- 🏊 Business Flow (Swimlane): Cross-functional workflows, actor-based process flows
25	- 📦 Class Diagrams: Object-oriented design, class structures and relationships
26	- 🔄 Sequence Diagrams: Object interactions over time, message flows
27	- 🗃️ ER Diagrams: Database entity relationships, data models
28
29	## Prerequisites
30
31	- Clear description of what should be visualized
32	- Identification of key entities, steps, or concepts
33	- Understanding of relationships or flow between elements
34
35	## Step-by-Step Workflow
36
37	### Step 1: Understand the Request
38
39	Analyze the user's description to determine:
40	1. Diagram type (flowchart, relationship, mind map, architecture)
41	2. Key elements (entities, steps, concepts)
42	3. Relationships (flow, connections, hierarchy)
43	4. Complexity (number of elements)
44
45	### Step 2: Choose the Appropriate Diagram Type
46
47	\| User Intent \| Diagram Type \| Example Keywords \|
48	\|-------------\|--------------\|------------------\|
49	\| Process flow, steps, procedures \| Flowchart \| "workflow", "process", "steps", "procedure" \|
50	\| Connections, dependencies, associations \| Relationship Diagram \| "relationship", "connections", "dependencies", "structure" \|
51	\| Concept hierarchy, brainstorming \| Mind Map \| "mind map", "concepts", "ideas", "breakdown" \|
52	\| System design, components \| Architecture Diagram \| "architecture", "system", "components", "modules" \|
53	\| Data flow, transformation processes \| Data Flow Diagram (DFD) \| "data flow", "data processing", "data transformation" \|
54	\| Cross-functional processes, actor responsibilities \| Business Flow (Swimlane) \| "business process", "swimlane", "actors", "responsibilities" \|
55	\| Object-oriented design, class structures \| Class Diagram \| "class", "inheritance", "OOP", "object model" \|
56	\| Interaction sequences, message flows \| Sequence Diagram \| "sequence", "interaction", "messages", "timeline" \|
57	\| Database design, entity relationships \| ER Diagram \| "database", "entity", "relationship", "data model" \|
58
59	### Step 3: Extract Structured Information
60
61	For Flowcharts:
62	- List of sequential steps
63	- Decision points (if any)
64	- Start and end points
65
66	For Relationship Diagrams:
67	- Entities/nodes (name + optional description)
68	- Relationships between entities (from → to, with label)
69
70	For Mind Maps:
71	- Central topic
72	- Main branches (3-6 recommended)
73	- Sub-topics for each branch (optional)
74
75	For Data Flow Diagrams (DFD):
76	- Data sources and destinations (external entities)
77	- Processes (data transformations)
78	- Data stores (databases, files)
79	- Data flows (arrows showing data movement from left-to-right or from top-left to bottom-right)
80	- Important: Do not represent process order, only data flow
81
82	For Business Flow (Swimlane):
83	- Actors/roles (departments, systems, people) - displayed as header columns
84	- Process lanes (vertical lanes under each actor)
85	- Process boxes (activities within each lane)
86	- Flow arrows (connecting process boxes, including cross-lane handoffs)
87
88	For Class Diagrams:
89	- Classes with names
90	- Attributes with visibility (+, -, #)
91	- Methods with visibility and parameters
92	- 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)
93	- Multiplicity notations (1, 0..1, 1.., )
94
95	For Sequence Diagrams:
96	- Objects/actors (arranged horizontally at top)
97	- Lifelines (vertical lines from each object)
98	- Messages

People who liked this also viewed

6 picks

Type

excalidraw-diagram-generator

27kinstalls4.6kforks

View on GitHub

How to install excalidraw-diagram-generator?

github/awesome-copilot/excalidraw-diagram-generator

$npx -y skills add github/awesome-copilot --skill excalidraw-diagram-generator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Excalidraw Diagram Generator
2
3	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.
4
5	## When to Use This Skill
6
7	Use this skill when users request:
8
9	- "Create a diagram showing..."
10	- "Make a flowchart for..."
11	- "Visualize the process of..."
12	- "Draw the system architecture of..."
13	- "Generate a mind map about..."
14	- "Create an Excalidraw file for..."
15	- "Show the relationship between..."
16	- "Diagram the workflow of..."
17
18	Supported diagram types:
19	- 📊 Flowcharts: Sequential processes, workflows, decision trees
20	- 🔗 Relationship Diagrams: Entity relationships, system components, dependencies
21	- 🧠 Mind Maps: Concept hierarchies, brainstorming results, topic organization
22	- 🏗️ Architecture Diagrams: System design, module interactions, data flow
23	- 📈 Data Flow Diagrams (DFD): Data flow visualization, data transformation processes
24	- 🏊 Business Flow (Swimlane): Cross-functional workflows, actor-based process flows
25	- 📦 Class Diagrams: Object-oriented design, class structures and relationships
26	- 🔄 Sequence Diagrams: Object interactions over time, message flows
27	- 🗃️ ER Diagrams: Database entity relationships, data models
28
29	## Prerequisites
30
31	- Clear description of what should be visualized
32	- Identification of key entities, steps, or concepts
33	- Understanding of relationships or flow between elements
34
35	## Step-by-Step Workflow
36
37	### Step 1: Understand the Request
38
39	Analyze the user's description to determine:
40	1. Diagram type (flowchart, relationship, mind map, architecture)
41	2. Key elements (entities, steps, concepts)
42	3. Relationships (flow, connections, hierarchy)
43	4. Complexity (number of elements)
44
45	### Step 2: Choose the Appropriate Diagram Type
46
47	\| User Intent \| Diagram Type \| Example Keywords \|
48	\|-------------\|--------------\|------------------\|
49	\| Process flow, steps, procedures \| Flowchart \| "workflow", "process", "steps", "procedure" \|
50	\| Connections, dependencies, associations \| Relationship Diagram \| "relationship", "connections", "dependencies", "structure" \|
51	\| Concept hierarchy, brainstorming \| Mind Map \| "mind map", "concepts", "ideas", "breakdown" \|
52	\| System design, components \| Architecture Diagram \| "architecture", "system", "components", "modules" \|
53	\| Data flow, transformation processes \| Data Flow Diagram (DFD) \| "data flow", "data processing", "data transformation" \|
54	\| Cross-functional processes, actor responsibilities \| Business Flow (Swimlane) \| "business process", "swimlane", "actors", "responsibilities" \|
55	\| Object-oriented design, class structures \| Class Diagram \| "class", "inheritance", "OOP", "object model" \|
56	\| Interaction sequences, message flows \| Sequence Diagram \| "sequence", "interaction", "messages", "timeline" \|
57	\| Database design, entity relationships \| ER Diagram \| "database", "entity", "relationship", "data model" \|
58
59	### Step 3: Extract Structured Information
60
61	For Flowcharts:
62	- List of sequential steps
63	- Decision points (if any)
64	- Start and end points
65
66	For Relationship Diagrams:
67	- Entities/nodes (name + optional description)
68	- Relationships between entities (from → to, with label)
69
70	For Mind Maps:
71	- Central topic
72	- Main branches (3-6 recommended)
73	- Sub-topics for each branch (optional)
74
75	For Data Flow Diagrams (DFD):
76	- Data sources and destinations (external entities)
77	- Processes (data transformations)
78	- Data stores (databases, files)
79	- Data flows (arrows showing data movement from left-to-right or from top-left to bottom-right)
80	- Important: Do not represent process order, only data flow
81
82	For Business Flow (Swimlane):
83	- Actors/roles (departments, systems, people) - displayed as header columns
84	- Process lanes (vertical lanes under each actor)
85	- Process boxes (activities within each lane)
86	- Flow arrows (connecting process boxes, including cross-lane handoffs)
87
88	For Class Diagrams:
89	- Classes with names
90	- Attributes with visibility (+, -, #)
91	- Methods with visibility and parameters
92	- 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)
93	- Multiplicity notations (1, 0..1, 1.., )
94
95	For Sequence Diagrams:
96	- Objects/actors (arranged horizontally at top)
97	- Lifelines (vertical lines from each object)
98	- Messages

People who liked this also viewed

6 picks

Type