mindmap-builder

# Mindmap Builder

## Overview

Create hierarchical mindmaps by generating specific structured JSON content. Automatically handles common syntax pitfalls (list syntax conflicts) to ensure diagrams render correctly in TriliumNext Note / Trilium Note.

## Critical Syntax Rules

* **Rule 1: Unique IDs**: Every node in the `nodeData` hierarchy must have a unique `id` string (e.g., "root", "sub1", "sub2").
* **Rule 2: Strict JSON Format**: Content must be valid, parseable JSON. No trailing commas.
* **Rule 3: Children Arrays**: Leaf nodes must have an empty `children: []` array.
* **Rule 4: Text Content**: Node `topic` must be plain text. Avoid Markdown or HTML tags inside the JSON strings.
* **Rule 5: Direction Integer**: `direction` must be `0` (left) or `1` (right). Do not use strings like "left".
* **Rule 6: Root Node Integrity**: There must be exactly one top-level object containing the `root` ID.


## Cognitive Load Management

### Miller's Rule (7±2) - Core Limits
* **Max Children per Node**: 5-7 children (never exceed 9)
* **Max Depth**: 3-4 levels maximum (beyond 4 creates cognitive overload)
* **Node Topics**: 1-4 words optimal, max 6 words, 25 characters maximum
* **Total Nodes**: 20-40 nodes for standard complexity
* **Visual Colors**: Max 5-6 distinct colors to prevent confusion


## Visual Styles
* **minimal**: Clean, high contrast, reduced visual noise
* **professional**: Business-friendly with subtle colors
* **colorful**: Vibrant, engaging colors for learning/creativity
* **academic**: Structured, formal appearance

---

## Layout Selection Guidelines

### ⚠️ Critical Layout Choice Decision

**AVOID RADIAL (Two-sided) LAYOUTS** in most cases. Radial layouts often create:
- **Visual Chaos**: Intersecting lines and crossing branches
- **Cognitive Overload**: Eye doesn't know where to start or follow
- **Poor Readability**: Text overlaps and navigation confusion
- **Lost Hierarchy**: Can't distinguish main from sub-concepts

### When to Use Each Layout

###