zhukang
1c7abd81d1
- 310 registry:skill items, 1528 files, 7 categories (hub tags) - registry.json generated by @kortix/registry buildRegistry - nested SKILL.md in sn-da-* renamed SUBSKILL.md (no phantom skills) - provenance + licenses: SOURCES.md
2.2 KiB
2.2 KiB
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 3–4 main branches with 3–5 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