Files
claude-scientific-skills/scientific-skills/markdown-mermaid-writing/references/diagrams/mindmap.md
borealBytes 02e19e3df9 docs(references): port style guides, 24 diagram guides, and 9 templates from opencode
All content ported from borealBytes/opencode under Apache-2.0 license with
attribution headers prepended to each file.

- references/markdown_style_guide.md (~733 lines): full markdown formatting,
  citation, collapsible sections, emoji, Mermaid integration, and template
  selection guide
- references/mermaid_style_guide.md (~458 lines): full Mermaid standards —
  emoji set, classDef color palette, accessibility (accTitle/accDescr),
  theme neutrality (no %%{init}), and diagram type selection table
- references/diagrams/ (24 files): per-type exemplars, tips, and templates
  for all Mermaid diagram types
- templates/ (9 files): PR, issue, kanban, ADR, presentation, how-to,
  status report, research paper, project docs

Source: https://github.com/borealBytes/opencode
2026-02-19 18:25:20 -05:00

2.2 KiB
Raw Blame History

Mindmap

Back to Style Guide — Read the style guide first for emoji, color, and accessibility rules.

Syntax keyword: mindmap Best for: Brainstorming, concept organization, knowledge hierarchies, topic breakdown When NOT to use: Sequential processes (use Flowchart), timelines (use Timeline)

⚠️ Accessibility: Mindmaps do not support accTitle/accDescr. Always place a descriptive italic Markdown paragraph directly above the code block.


Exemplar Diagram

Mindmap showing a platform engineering team's key responsibility areas organized into infrastructure, developer experience, security, and observability domains:

mindmap
    root((🏗️ Platform Engineering))
        ☁️ Infrastructure
            Kubernetes clusters
            Service mesh
            Load balancing
            Auto-scaling
        🔧 Developer Experience
            CI/CD pipelines
            Local dev environments
            Internal CLI tools
            Documentation
        🔐 Security
            Secret management
            Network policies
            Vulnerability scanning
            Access control
        📊 Observability
            Metrics collection
            Log aggregation
            Distributed tracing
            Alerting rules

Tips

  • Keep to 34 main branches with 35 sub-items each
  • Use emoji on branch headers for visual distinction
  • Don't nest deeper than 3 levels
  • Root node uses (( )) for circle shape
  • Always pair with a Markdown text description above for screen readers

Template

Description of what this mindmap shows and the key categories it covers:

mindmap
    root((🎯 Central Concept))
        📋 Branch One
            Sub-item A
            Sub-item B
            Sub-item C
        🔧 Branch Two
            Sub-item D
            Sub-item E
        📊 Branch Three
            Sub-item F
            Sub-item G
            Sub-item H