1---2name: mind-map3description: Use when the user needs to explore one central topic through associative branches, capture brainstorming, or organize an unconstrained idea space before choosing a structure.4---56# Mind map78## What / why910A mind map radiates from one central subject. It tells the story “what belongs around this idea?” rather than “what causes what?” Use it to externalize a messy topic, reveal themes, and identify next questions. Choose another skill when relationships need to be typed, ordered, causal, or exhaustive.1112## How to model1314- Put one unambiguous topic at the center; make branch labels nouns or short prompts.15- Keep one concept per node and use a stable depth (topic → theme → detail).16- Prefer parent-child containment. Do not imply sequence, ownership, or causality with an ordinary branch.17- Mark questions, examples, decisions, and unknowns distinctly; do not bury caveats in prose.1819## Styling and customization2021Use radial or left-to-right layout, short labels, whitespace, and restrained color. Reserve color for branch families or status, and use line weight sparingly. A bespoke style may use icons, but every visual distinction needs a legend or clear label.2223## Renderer choices2425Ask for the user’s renderer preference first. Mermaid supports mind maps and configurable themes/layouts; D2, Graphviz, PlantUML, and diagrams.net can express tree-like maps but do not guarantee a mind-map grammar. Use native layout where possible; do not force a flowchart and call it a mind map. diagram.zip has no dedicated semantic mind-map validator, so validate hierarchy and labels in the source.2627## Review2829Check exactly one center, readable branches without color, comparable sibling levels, and no connector implying an unsupported relationship. Confirm whether the map is exploratory or a final taxonomy.3031## Prior art3233See [references/prior-art.md](references/prior-art.md).