Obsidian Canvas Creator
Transform text content into structured Obsidian Canvas files with support for MindMap and freeform layouts.
When to Use This Skill
- User requests to create a canvas, mind map, or visual diagram from text
- User wants to organize information spatially
- User mentions "Obsidian Canvas" or similar visualization tools
- Converting structured content (articles, notes, outlines) into visual format
Core Workflow
1. Analyze Content
Read and understand the input content:
- Identify main topics and hierarchical relationships
- Extract key points, facts, and supporting details
- Note any existing structure (headings, lists, sections)
2. Determine Layout Type
Ask user to choose or infer from context:
MindMap Layout:
- Radial structure from center
- Parent-child relationships
- Clear hierarchy
- Good for: brainstorming, topic exploration, hierarchical content
Freeform Layout:
- Custom positioning
- Flexible relationships
- Multiple connection types
- Good for: complex networks, non-hierarchical content, custom arrangements
3. Plan Structure
For MindMap:
- Identify central concept (root node)
- Map primary branches (main topics)
- Organize secondary branches (subtopics)
- Position leaf nodes (details)
For Freeform:
- Group related concepts
- Identify connection patterns
- Plan spatial zones
- Consider visual flow
4. Generate Canvas
Create JSON following the Canvas specification:
Node Creation:
- Assign unique 8-12 character hex IDs
- Set appropriate dimensions based on content length
- Apply consistent color schemes
- Ensure no coordinate overlaps
Edge Creation:
- Connect parent-child relationships
- Use appropriate arrow styles
- Add labels for complex relationships
- Choose line styles (straight for hierarchy, curved for cross-references)
Grouping (Optional):
- Create visual containers for related nodes
- Use subtle background colors
- Add descriptive labels
5. Apply Layout Algorithm
MindMap Layout Calculations:
Refer to references/layout-algorithms.md for detailed algorithms. Key principles:
- Center root at (0, 0)
- Distribute primary nodes radially
- Space secondary nodes based on sibling count
- Maintain minimum spacing: 320px horizontal, 200px vertical
Freeform Layout Principles:
- Start with logical groupings
- Position groups with clear separation
- Connect across groups with curved edges
- Balance visual weight across canvas
6. Validate and Output
Before outputting:
Validation Checklist:
- All nodes have unique IDs
- No coordinate overlaps (check distance > node dimensions + spacing)
- All edges reference valid node IDs
- Groups (if any) have labels
- Colors use consistent format (hex or preset numbers)
- JSON is properly escaped (Chinese quotes: 『』 for double, 「」 for single)
Output Format:
- Complete, valid JSON Canvas file
- No additional explanation text
- Directly importable into Obsidian
Node Sizing Guidelines
Text Length-Based Sizing:
- Short text (<30 chars): 220 × 100 px
- Medium text (30-60 chars): 260 × 120 px
- Long text (60-100 chars): 320 × 140 px
- Very long text (>100 chars): 320 × 180 px
Color Schemes
Preset Colors (Recommended):
"1" - Red (warnings, important)
"2" - Orange (action items)
"3" - Yellow (questions, notes)
"4" - Green (positive, completed)
"5" - Cyan (information, details)
"6" - Purple (concepts, abstract)
Custom Hex Colors:
Use for brand consistency or specific themes. Always use uppercase format: "#4A90E2"
Critical Rules
Quote Handling:
- Chinese double quotes → 『』
- Chinese single quotes → 「」
- English double quotes →
\"
ID Generation:
- 8-12 character random hex strings
- Must be unique across all nodes and edges
Z-Index Order:
- Output groups first (bottom layer)
- Then subgroups
- Finally text/link nodes (top layer)
Spacing Requirements:
- Minimum horizontal: 320px between node centers
- Minimum vertical: 200px between node centers
- Account for node dimensions when calculating
JSON Structure:
- Top level contains only
nodes and edges arrays
- No extra wrapping objects
- No comments in output
Examples
Simple MindMap Request
User: "Create a mind map about solar system planets"
Process:
- Identify center: "Solar System"
- Primary branches: Inner Planets, Outer Planets, Dwarf Planets
- Secondary nodes: Individual planets with key facts
- Apply radial layout
- Generate JSON with proper spacing
Freeform Content Request
User: "Turn this article into a canvas" + [article text]
Process:
- Extract article structure (intro, body sections, conclusion)
- Identify key concepts and relationships
- Group related sections spatially
- Connect with labeled edges
- Apply freeform layout with clear zones
Reference Documents
- Canvas Specification:
references/canvas-spec.md - Complete JSON Canvas format specification
- Layout Algorithms:
references/layout-algorithms.md - Detailed positioning algorithms for both layout types
Load these references when:
- Need specification details for edge cases
- Implementing complex layout calculations
- Troubleshooting validation errors
Tips for Quality Canvases
- Keep text concise: Each node should be scannable (<2 lines preferred)
- Use hierarchy: Group by importance and relationship
- Balance the canvas: Distribute nodes to avoid clustering
- Strategic colors: Use colors to encode meaning, not just decoration
- Meaningful connections: Only add edges that clarify relationships
- Test in Obsidian: Verify the output opens correctly
Common Pitfalls to Avoid
- Overlapping nodes (always check distances)
- Inconsistent quote escaping (breaks JSON parsing)
- Missing group labels (causes sidebar navigation issues)
- Too much text in nodes (use file nodes for long content)
- Duplicate IDs (each must be unique)
- Unconnected nodes (unless intentional islands)
1---2name: obsidian-canvas-creator3description: Create Obsidian Canvas files from text content, supporting both MindMap and freeform layouts. Use this skill when users want to visualize content as an interactive canvas, create mind maps, or organize information spatially in Obsidian format.4---5
6# Obsidian Canvas Creator
7
8Transform text content into structured Obsidian Canvas files with support for MindMap and freeform layouts.
9
10## When to Use This Skill
11
12- User requests to create a canvas, mind map, or visual diagram from text
13- User wants to organize information spatially
14- User mentions "Obsidian Canvas" or similar visualization tools
15- Converting structured content (articles, notes, outlines) into visual format
16
17## Core Workflow
18
19### 1. Analyze Content
20
21Read and understand the input content:
22- Identify main topics and hierarchical relationships
23- Extract key points, facts, and supporting details
24- Note any existing structure (headings, lists, sections)
25
26### 2. Determine Layout Type
27
28Ask user to choose or infer from context:
29
30**MindMap Layout:**
31- Radial structure from center
32- Parent-child relationships
33- Clear hierarchy
34- Good for: brainstorming, topic exploration, hierarchical content
35
36**Freeform Layout:**
37- Custom positioning
38- Flexible relationships
39- Multiple connection types
40- Good for: complex networks, non-hierarchical content, custom arrangements
41
42### 3. Plan Structure
43
44**For MindMap:**
45- Identify central concept (root node)
46- Map primary branches (main topics)
47- Organize secondary branches (subtopics)
48- Position leaf nodes (details)
49
50**For Freeform:**
51- Group related concepts
52- Identify connection patterns
53- Plan spatial zones
54- Consider visual flow
55
56### 4. Generate Canvas
57
58Create JSON following the Canvas specification:
59
60**Node Creation:**
61- Assign unique 8-12 character hex IDs
62- Set appropriate dimensions based on content length
63- Apply consistent color schemes
64- Ensure no coordinate overlaps
65
66**Edge Creation:**
67- Connect parent-child relationships
68- Use appropriate arrow styles
69- Add labels for complex relationships
70- Choose line styles (straight for hierarchy, curved for cross-references)
71
72**Grouping (Optional):**
73- Create visual containers for related nodes
74- Use subtle background colors
75- Add descriptive labels
76
77### 5. Apply Layout Algorithm
78
79**MindMap Layout Calculations:**
80
81Refer to `references/layout-algorithms.md` for detailed algorithms. Key principles:
82
83- Center root at (0, 0)
84- Distribute primary nodes radially
85- Space secondary nodes based on sibling count
86- Maintain minimum spacing: 320px horizontal, 200px vertical
87
88**Freeform Layout Principles:**
89
90- Start with logical groupings
91- Position groups with clear separation
92- Connect across groups with curved edges
93- Balance visual weight across canvas
94
95### 6. Validate and Output
96
97Before outputting:
98
99**Validation Checklist:**
100- All nodes have unique IDs
101- No coordinate overlaps (check distance > node dimensions + spacing)
102- All edges reference valid node IDs
103- Groups (if any) have labels
104- Colors use consistent format (hex or preset numbers)
105- JSON is properly escaped (Chinese quotes: 『』 for double, 「」 for single)
106
107**Output Format:**
108- Complete, valid JSON Canvas file
109- No additional explanation text
110- Directly importable into Obsidian
111
112## Node Sizing Guidelines
113
114**Text Length-Based Sizing:**
115- Short text (<30 chars): 220 × 100 px
116- Medium text (30-60 chars): 260 × 120 px
117- Long text (60-100 chars): 320 × 140 px
118- Very long text (>100 chars): 320 × 180 px
119
120## Color Schemes
121
122**Preset Colors (Recommended):**
123- `"1"` - Red (warnings, important)
124- `"2"` - Orange (action items)
125- `"3"` - Yellow (questions, notes)
126- `"4"` - Green (positive, completed)
127- `"5"` - Cyan (information, details)
128- `"6"` - Purple (concepts, abstract)
129
130**Custom Hex Colors:**
131Use for brand consistency or specific themes. Always use uppercase format: `"#4A90E2"`
132
133## Critical Rules
134
1351. **Quote Handling:**
136 - Chinese double quotes → 『』
137 - Chinese single quotes → 「」
138 - English double quotes → `\"`
139
1402. **ID Generation:**
141 - 8-12 character random hex strings
142 - Must be unique across all nodes and edges
143
1443. **Z-Index Order:**
145 - Output groups first (bottom layer)
146 - Then subgroups
147 - Finally text/link nodes (top layer)
148
1494. **Spacing Requirements:**
150 - Minimum horizontal: 320px between node centers
151 - Minimum vertical: 200px between node centers
152 - Account for node dimensions when calculating
153
1545. **JSON Structure:**
155 - Top level contains only `nodes` and `edges` arrays
156 - No extra wrapping objects
157 - No comments in output
158
159## Examples
160
161### Simple MindMap Request
162User: "Create a mind map about solar system planets"
163
164Process:
1651. Identify center: "Solar System"
1662. Primary branches: Inner Planets, Outer Planets, Dwarf Planets
1673. Secondary nodes: Individual planets with key facts
1684. Apply radial layout
1695. Generate JSON with proper spacing
170
171### Freeform Content Request
172User: "Turn this article into a canvas" + [article text]
173
174Process:
1751. Extract article structure (intro, body sections, conclusion)
1762. Identify key concepts and relationships
1773. Group related sections spatially
1784. Connect with labeled edges
1795. Apply freeform layout with clear zones
180
181## Reference Documents
182
183- **Canvas Specification**: `references/canvas-spec.md` - Complete JSON Canvas format specification
184- **Layout Algorithms**: `references/layout-algorithms.md` - Detailed positioning algorithms for both layout types
185
186Load these references when:
187- Need specification details for edge cases
188- Implementing complex layout calculations
189- Troubleshooting validation errors
190
191## Tips for Quality Canvases
192
1931. **Keep text concise**: Each node should be scannable (<2 lines preferred)
1942. **Use hierarchy**: Group by importance and relationship
1953. **Balance the canvas**: Distribute nodes to avoid clustering
1964. **Strategic colors**: Use colors to encode meaning, not just decoration
1975. **Meaningful connections**: Only add edges that clarify relationships
1986. **Test in Obsidian**: Verify the output opens correctly
199
200## Common Pitfalls to Avoid
201
202- Overlapping nodes (always check distances)
203- Inconsistent quote escaping (breaks JSON parsing)
204- Missing group labels (causes sidebar navigation issues)
205- Too much text in nodes (use file nodes for long content)
206- Duplicate IDs (each must be unique)
207- Unconnected nodes (unless intentional islands)