Mindmap File Format
.mindmap files are standard markdown that Nimbalyst renders as an interactive mindmap. You can create and edit them directly -- no special tools needed.
Syntax
Tree structure
| Syntax |
Mindmap level |
# Heading |
Root node (exactly one per file) |
## Heading |
Depth 1 branches |
### Heading |
Depth 2 branches |
- List item |
Deeper nodes (indentation = depth) |
- Nested item |
2 spaces per indent level |
Headings define the top 3 levels. Below that, indented list items handle arbitrary nesting.
Notes
Blockquotes immediately after a node become that node's note:
## Branch Name
> This note is attached to "Branch Name".
> It can span multiple lines.
Metadata
Inline {key: value} at the end of a node line:
- Task name {color: green, status: todo, tags: frontend, urgent}
Supported keys:
color: default, red, orange, yellow, green, blue, purple, pinkstatus: none, idea, question, todo, in-progress, donetags: comma-separated listlink: one related workspace document, URL, or tracker item; tracker items use a canonical link such as nimbalyst://NIM-123pinned: true when a manual canvas position should survive hybrid layoutx, y: pinned canvas coordinates (written automatically by the editor)
Frontmatter
YAML frontmatter stores the document title:
---
title: My Mindmap
---
Complete example
---
title: Project Plan
layout: balanced
---
# Project Plan
> High-level roadmap for Q2.
## Research {color: blue}
- User interviews {status: done}
- Competitive analysis {status: in-progress}
- Feature comparison
- Pricing analysis
## Design {color: purple}
### Wireframes
- Homepage {status: done}
- Dashboard {tags: priority}
### Prototypes
- Interactive prototype {status: todo}
## Engineering {color: green, link: nimbalyst://NIM-123}
- API design
> RESTful endpoints for the core product.
- Authentication
- Data models
- Frontend
- Component library
- State management
Rules
- Exactly one
# heading (the root node)
## and ### for the top levels, then - lists for deeper nesting- 2 spaces per indent level for list items
- Metadata
{...} goes at the end of the node line, not on a separate line
- Notes
> ... go on the line(s) immediately after the node they belong to
- Blank lines between sections improve readability but are optional
- The file extension is
.mindmap (not .md)
- Frontmatter
layout may be balanced or right
1---2name: mindmap-format3description: How to create, read, and edit .mindmap files. Use this skill when the user asks to create a mindmap, brainstorm visually, map out ideas, or when working with existing .mindmap files.4---56# Mindmap File Format78`.mindmap` files are standard markdown that Nimbalyst renders as an interactive mindmap. You can create and edit them directly -- no special tools needed.910## Syntax1112### Tree structure1314| Syntax | Mindmap level |15|--------|--------------|16| `# Heading` | Root node (exactly one per file) |17| `## Heading` | Depth 1 branches |18| `### Heading` | Depth 2 branches |19| `- List item` | Deeper nodes (indentation = depth) |20| ` - Nested item` | 2 spaces per indent level |2122Headings define the top 3 levels. Below that, indented list items handle arbitrary nesting.2324### Notes2526Blockquotes immediately after a node become that node's note:2728```markdown29## Branch Name30> This note is attached to "Branch Name".31> It can span multiple lines.32```3334### Metadata3536Inline `{key: value}` at the end of a node line:3738```markdown39- Task name {color: green, status: todo, tags: frontend, urgent}40```4142Supported keys:43- `color`: default, red, orange, yellow, green, blue, purple, pink44- `status`: none, idea, question, todo, in-progress, done45- `tags`: comma-separated list46- `link`: one related workspace document, URL, or tracker item; tracker items use a canonical link such as `nimbalyst://NIM-123`47- `pinned`: `true` when a manual canvas position should survive hybrid layout48- `x`, `y`: pinned canvas coordinates (written automatically by the editor)4950### Frontmatter5152YAML frontmatter stores the document title:5354```yaml55---56title: My Mindmap57---58```5960## Complete example6162```markdown63---64title: Project Plan65layout: balanced66---6768# Project Plan69> High-level roadmap for Q2.7071## Research {color: blue}72- User interviews {status: done}73- Competitive analysis {status: in-progress}74 - Feature comparison75 - Pricing analysis7677## Design {color: purple}7879### Wireframes80- Homepage {status: done}81- Dashboard {tags: priority}8283### Prototypes84- Interactive prototype {status: todo}8586## Engineering {color: green, link: nimbalyst://NIM-123}87- API design88 > RESTful endpoints for the core product.89 - Authentication90 - Data models91- Frontend92 - Component library93 - State management94```9596## Rules97981. Exactly one `#` heading (the root node)992. `##` and `###` for the top levels, then `-` lists for deeper nesting1003. 2 spaces per indent level for list items1014. Metadata `{...}` goes at the end of the node line, not on a separate line1025. Notes `> ...` go on the line(s) immediately after the node they belong to1036. Blank lines between sections improve readability but are optional1047. The file extension is `.mindmap` (not `.md`)1058. Frontmatter `layout` may be `balanced` or `right`
nimbalyst