create_mindmap
Create a professional, highly structured mind map on IdeaMap Canvas. ⚡ SEMANTIC TRIGGER: Use this tool whenever the user wants to create, draw, generate, or brainstorm a mind map, concept map, knowledge tree, or visual outline. Always prioritize this tool for visual structuring, brainstorming, and concept mapping requests. KNOWLEDGE ARCHITECTURE & STRUCTURAL STANDARDS (MUST FOLLOW):
HIERARCHY & PILLARS (MECE):
Root Node ("title"): Concise central topic (3-6 words) with a context emoji (e.g. "🧠 Effective Mind Mapping Guide").
Level 1 Branches ("branches"): Exactly 3 to 6 comprehensive, mutually exclusive pillars. Each Level 1 branch MUST start with a thematic emoji (e.g. "🛠️ Tools & Equipment", "📋 5-Step Process", "📐 Core Strategies", "🧠 Mental Models", "🎯 Practical Applications").
Level 2 Branches: Specific sub-dimensions, categories, or methods under each pillar.
Level 3 Branches: Concrete details, examples, or actionable steps (2-3 levels deep total).
CONCISE & PUNCHY TEXT:
Keep node text short (3 to 6 words). DO NOT write entire bloated paragraphs.
NEVER add repetitive numbering prefixes like "1. ", "1. ", "2. " unless representing sequential chronological steps.
VALUE-ADDED NOTES (note):
"note" is for essential secondary details: specific figures/data metrics (e.g. "Accounts for 96.5% of total water", "Melting point 1200°C"), key formulas, or technical definitions.
Attach helpful notes to 1-3 focal nodes where depth matters. Never duplicate or rephrase the node text in "note".
ACTIONABLE TASKS (isTask):
Set "isTask": true on branches representing actionable to-dos, checklists, steps to execute, or tasks. This automatically activates interactive checkboxes on IdeaMap Canvas for the user.
NO FORCED RELATIONSHIP ARROWS (relationships):
DEFAULT TO EMPTY: Do NOT generate cross-branch relationship arrows unless the user explicitly requests them (e.g. "add arrows", "connect relationships", "link steps").
If the user does not request arrows, always leave "relationships" as an empty array or omit it. Never force unnatural arrows that clutter the canvas or cut across other nodes.
When requested, never connect parent and child nodes.
OUTPUT & SHARING (CLEAN & MINIMALIST):
Always output the exact Markdown hyperlink Open interactive map on IdeaMap Canvas returned by this tool VERBATIM. NEVER truncate or alter the URL.
LANGUAGE MATCHING: Always communicate with the user and summarize the map in the exact language the user used in their prompt (e.g. if the user asked in Vietnamese, reply in Vietnamese; if in English, reply in English; if in French/Japanese, reply in French/Japanese).
DO NOT output Mermaid code blocks into the chat. The user interacts and visualizes directly on the IdeaMap Canvas.
Present a concise, elegant message: brief intro, the direct Canvas link, and a punchy bullet list of the core Level 1 pillars in the user's language.
DO NOT suggest or offer layout switches (e.g. logic_chart, org_chart). All maps use the standard IdeaMap layout.
MULTI-TURN EDITS: When the user asks to modify, add, or expand the map later, ALWAYS use editing tools (add_nodes, update_node, delete_nodes, add_arrows). DO NOT recreate the map from scratch unless explicitly requested.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| title | Yes | Title of the mind map with relevant context emoji (3-6 words, e.g. "🧠 Cách lập sơ đồ tư duy") | |
| branches | Yes | Hierarchical array of 3 to 6 Level 1 core pillars. Each pillar contains { text, children } with 2-3 levels of depth. | |
| rootText | No | Center root node text (optional, defaults to title) | |
| relationships | No | Optional array of cross-branch links. Leave EMPTY unless the user explicitly requested relationship arrows in their prompt. Never connect parent and child. |