Neurodivergent Visual Org

Mode System (v3.1)

This skill supports four modes to adapt to different cognitive styles and accessibility needs:

Mode Selection

Base Modes (choose one):

1. Neurodivergent Mode - ADHD-friendly, energy-aware, compassionate language
2. Neurotypical Mode - Direct, efficient, standard cognitive load

Accessibility Modes (optional, combinable with base modes): 3. Colorblind-Safe Mode - Pattern-based differentiation for all color vision types 4. Monochrome Mode - Pure black & white optimized for printing and e-ink displays

Mode Combinations Available:

• Neurodivergent + Colorblind-Safe
• Neurodivergent + Monochrome
• Neurotypical + Colorblind-Safe
• Neurotypical + Monochrome
• Colorblind-Safe only (no base mode features)
• Monochrome only (no base mode features)

Selection Methods:

1. Auto-Detect (Default)

• Analyzes user language for distress signals ("overwhelmed", "paralyzed", "stuck")
• Detects mentions of neurodivergent conditions or executive dysfunction
• Detects accessibility requests ("colorblind-safe", "print-friendly", "grayscale")
• Defaults to neurodivergent mode when ambiguous (inclusive design)

2. Explicit Mode Request

• User says: "Use neurotypical mode" or "Use ADHD mode"
• User says: "Use colorblind-safe mode" or "Make it print-friendly"
• User says: "Combine neurodivergent and colorblind-safe modes"
• Persists for current conversation unless changed

3. Configuration File

• User creates: .claude/neurodivergent-visual-org-preference.yml
• Sets default base mode, accessibility modes, time multipliers, chunk sizes
• Can set auto-enable rules (e.g., monochrome for PDFs)

Mode Characteristics

Base Mode Features:

Accessibility Mode Features:

Mode Combination Notes:

• Base mode controls language, time estimates, and cognitive scaffolding
• Accessibility mode controls visual encoding (patterns, contrast, shapes)
• Both can be active simultaneously for maximum accommodation

Backward Compatibility

v3.1 maintains v3.0 behavior:

• Defaults to neurodivergent base mode (v2.0 compatible)
• Accessibility modes are opt-in (not enabled by default)
• v3.0 visualizations remain valid (no breaking changes)

Mode Detection Algorithm

Step 1: Check for explicit base mode request

base_mode = None
accessibility_mode = None

# Detect base mode
if "neurotypical mode" in user_message.lower():
    base_mode = "neurotypical"
elif "adhd mode" or "neurodivergent mode" in user_message.lower():
    base_mode = "neurodivergent"

Step 2: Check for explicit accessibility mode request

# Detect colorblind-safe mode
colorblind_keywords = ["colorblind", "color blind", "colorblind-safe",
                      "colour blind", "accessible colors", "pattern-based",
                      "cvd", "color vision deficiency"]
if any(keyword in user_message.lower() for keyword in colorblind_keywords):
    accessibility_mode = "colorblind-safe"

# Detect monochrome mode (takes precedence over colorblind-safe)
monochrome_keywords = ["monochrome", "black and white", "b&w", "grayscale",
                      "greyscale", "print-friendly", "printing", "e-ink",
                      "black & white", "photocopier"]
if any(keyword in user_message.lower() for keyword in monochrome_keywords):
    accessibility_mode = "monochrome"

Step 3: Check configuration file

if config_file_exists():
    config = load_user_preference()

    # Apply base mode if not explicitly set
    if base_mode is None:
        base_mode = config.get("default_mode", "neurodivergent")

    # Apply accessibility mode if not explicitly set
    if accessibility_mode is None:
        accessibility_mode = config.get("colorblind_safe", False) and "colorblind-safe"
        if not accessibility_mode:
            accessibility_mode = config.get("monochrome", False) and "monochrome"

Step 4: Auto-detect base mode from language

distress_signals = ["overwhelmed", "paralyzed", "stuck", "can't decide",
                   "don't know where to start", "too much"]
neurodivergent_mentions = ["adhd", "autism", "executive dysfunction",
                          "time blindness", "decision paralysis"]
energy_mentions = ["spoons", "burned out", "exhausted", "no energy"]

if base_mode is None:
    if any(signal in user_message.lower() for signal in
           distress_signals + neurodivergent_mentions + energy_mentions):
        base_mode = "neurodivergent"

Step 5: Default to neurodivergent base mode (inclusive)

if base_mode is None:
    base_mode = "neurodivergent"  # Backward compatible with v2.0

Step 6: Apply modes

# accessibility_mode can be None, "colorblind-safe", or "monochrome"
# base_mode will always be "neurodivergent" or "neurotypical"
apply_modes(base_mode=base_mode, accessibility_mode=accessibility_mode)

Accessibility Mode Implementation

Colorblind-Safe Mode Specifications

Purpose: Make diagrams accessible for all color vision types (protanopia, deuteranopia, tritanopia, achromatopsia) while remaining clear for regular color vision.

Design Principles:

1. Never rely on color alone - always pair with patterns, shapes, or text
2. Pattern-based differentiation - use border styles as primary encoding
3. Explicit text labels - prefix all nodes with type indicators
4. Shape coding - use different node shapes for different categories
5. High contrast borders - all nodes have bold, visible borders

Mermaid Implementation:

Border Pattern System:

%%{init: {'theme':'base'}}%%
flowchart TD
    Keep["[✅ KEEP] Item"]
    Donate["[📦 DONATE] Item"]
    Maybe["[🤔 MAYBE] Item"]
    Break["[🛑 BREAK] Rest"]

    style Keep fill:#ffffff,stroke:#000000,stroke-width:3px,stroke-dasharray: 5 5
    style Donate fill:#ffffff,stroke:#000000,stroke-width:2px,stroke-dasharray: 10 5
    style Maybe fill:#ffffff,stroke:#000000,stroke-width:2px,stroke-dasharray: 2 2
    style Break fill:#ffffff,stroke:#000000,stroke-width:3px,stroke-dasharray: 1 4

Pattern Legend:

• stroke-dasharray: 5 5 - Short dashes (KEEP items, positive actions)
• stroke-dasharray: 10 5 - Long dashes (DONATE items, external actions)
• stroke-dasharray: 2 2 - Dots (MAYBE items, uncertain states)
• stroke-dasharray: 1 4 - Dot-dash (BREAK items, pauses)
• stroke-width: 3px - Critical importance
• stroke-width: 2px - Standard importance
• stroke-width: 1px - Detail level

Shape Coding:

• ([text]) - Rounded rectangle: Standard process steps
• {text} - Diamond: Decision points
• [[text]] - Hexagon-style: Critical deadlines
• [/text/] - Trapezoid: Break/rest states
• >text] - Asymmetric: External dependencies

Text Prefix System:

• [✅ KEEP] - Items to keep
• [📦 DONATE] - Items to donate/give away
• [🤔 MAYBE] - Uncertain decisions
• [🛑 BREAK] - Rest/break required
• [⚠️ CRITICAL] - Critical deadline or warning
• [START] - Starting point
• [END] - Completion point
• [DECIDE] - Decision point

Color Strategy:

• White fills (#ffffff) for all nodes
• Black borders (#000000) for maximum contrast
• Colors can be added for users with color vision, but information is encoded in patterns

Monochrome Mode Specifications

Purpose: Optimize for black & white printing, photocopying, and e-ink displays where color is unavailable.

Design Principles:

1. Pure black and white only - no grays (print unreliably)
2. Fill pattern hierarchy - use patterns to show importance
3. Border style differentiation - solid/dashed/dotted for categories
4. Verbose text labels - more explicit than colorblind-safe mode
5. Extra whitespace - better print legibility

Mermaid Implementation:

Fill Pattern System:

%%{init: {'theme':'base'}}%%
flowchart TD
    Critical["[★ CRITICAL] Deadline"]
    High["[! HIGH] Important"]
    Medium["[→ MEDIUM] Standard"]
    Standard["[○ STANDARD] Normal"]

    style Critical fill:#000000,stroke:#000000,stroke-width:3px,color:#ffffff
    style High fill:#ffffff,stroke:#000000,stroke-width:3px
    style Medium fill:#ffffff,stroke:#000000,stroke-width:2px,stroke-dasharray: 10 5
    style Standard fill:#ffffff,stroke:#000000,stroke-width:2px

Fill Pattern Hierarchy:

• Solid black fill + white text: fill:#000000,color:#ffffff - Priority 1 (Critical)
• White fill + bold border: fill:#ffffff,stroke-width:3px - Priority 2 (High)
• White fill + dashed border: stroke-dasharray: 10 5 - Priority 3 (Medium)
• White fill + solid border: Standard weight - Priority 4 (Standard)

Border Style System:

• stroke-width:3px + solid - Critical/deadlines
• stroke-width:2px + solid - Standard steps
• stroke-dasharray: 10 5 - Optional/medium priority
• stroke-dasharray: 5 5 - Maybe/uncertain
• stroke-dasharray: 2 2 - Breaks/pauses

Text Prefix System (Verbose):

• [★ CRITICAL DEADLINE] - Critical with visual marker
• [✓ KEEP] - Text checkmark
• [→ DONATE] - Text arrow
• [? MAYBE] - Text question mark
• [■ BREAK] - Text square (stop sign)
• [○ START] - Text circle
• [● END] - Filled circle

Spacing Considerations:

• Use more vertical space between nodes
• Larger font sizes recommended (handled by <br/> for multi-line)
• Wide margins in flowchart layout

Mode Combination Logic

When both base mode and accessibility mode are active:

1. Base mode controls:

   • Language tone (compassionate vs direct)
   • Time estimates (buffered vs standard)
   • Task granularity (micro-steps vs standard tasks)
   • Energy scaffolding (explicit vs minimal)

2. Accessibility mode controls:

   • Visual encoding (colors, patterns, shapes)
   • Border styles and thickness
   • Text prefix style
   • Fill patterns (monochrome only)

3. Both modes respected simultaneously:

   • Neurodivergent + Colorblind-Safe = ADHD-friendly language + pattern-based visuals
   • Neurodivergent + Monochrome = ADHD-friendly language + B&W print-optimized
   • Neurotypical + Colorblind-Safe = Efficient language + pattern-based visuals
   • Neurotypical + Monochrome = Efficient language + B&W print-optimized

Example Combined Output:

%%{init: {'theme':'base'}}%%
flowchart TD
    Start(["[○ START] Decision time<br/>(Take 3 seconds max)"])
    Q1{"[? DECIDE]<br/>Do I love it?<br/>(Not obligated)"}
    Keep["[✓ KEEP]<br/>Pack for move<br/>(Fits in new space)"]
    Donate["[→ DONATE]<br/>Helps someone else<br/>(Guilt-free)"]
    Break["[■ BREAK]<br/>Rest 10 min<br/>(Decision fatigue signal)"]

    Start --> Q1
    Q1 -->|YES| Keep
    Q1 -->|NO| Donate
    Q1 -->|UNSURE| Break

    style Start fill:#ffffff,stroke:#000000,stroke-width:3px
    style Q1 fill:#ffffff,stroke:#000000,stroke-width:2px
    style Keep fill:#ffffff,stroke:#000000,stroke-width:3px,stroke-dasharray: 5 5
    style Donate fill:#ffffff,stroke:#000000,stroke-width:2px,stroke-dasharray: 10 5
    style Break fill:#000000,stroke:#000000,stroke-width:3px,color:#ffffff

This example shows: Neurodivergent language (compassionate, with parenthetical reassurance) + Monochrome visual encoding (B&W with patterns)

Configuration File Schema

Users can create a configuration file to set default modes and customize behavior:

File Location: .claude/neurodivergent-visual-org-preference.yml

Complete Configuration Example:

# Neurodivergent Visual Org v3.1 Configuration

# Base mode (required, choose one)
default_mode: neurodivergent  # Options: neurodivergent, neurotypical

# Accessibility modes (optional, can enable one or both)
colorblind_safe: false         # Enable pattern-based differentiation
monochrome: false              # Enable pure B&W print optimization

# Auto-enable rules for accessibility modes
# Note: These will PROMPT for confirmation before applying
auto_prompt_monochrome:
  when_printing: true           # Suggest monochrome when printing
  when_exporting_pdf: true      # Suggest monochrome for PDF export
  when_exporting_png: false     # Keep current mode for PNG exports

auto_prompt_colorblind_safe:
  when_sharing: true            # Suggest colorblind-safe for shared docs
  when_public: true             # Suggest for public-facing documents

# Base mode customizations
neurodivergent_customizations:
  chunk_size: 4                 # Items per chunk (3-5 recommended)
  time_multiplier: 1.5          # Buffer multiplier for time estimates
  micro_step_duration: 5        # Minutes per micro-step (3-10 recommended)
  show_energy_scaffolding: true # Show spoons/breaks explicitly
  use_compassionate_language: true

neurotypical_customizations:
  chunk_size: 6                 # Items per chunk (5-7 recommended)
  time_multiplier: 1.0          # Standard time estimates
  task_duration: 20             # Minutes per task (15-30 recommended)
  show_energy_scaffolding: false
  use_direct_language: true

# Colorblind-safe mode customizations
colorblind_safe_patterns:
  keep: "short-dash"            # Options: short-dash, long-dash, dots, dot-dash, solid
  donate: "long-dash"
  maybe: "dots"
  break: "dot-dash"
  critical: "solid"

  # Border thickness (1-3 recommended)
  critical_thickness: 3
  standard_thickness: 2
  detail_thickness: 1

# Monochrome mode customizations
monochrome_fills:
  priority_1_critical: "solid-black"  # Solid black fill, white text
  priority_2_high: "white-bold"       # White fill, bold border
  priority_3_medium: "white-dashed"   # White fill, dashed border
  priority_4_standard: "white"        # White fill, standard border

# General preferences
preferences:
  always_include_legends: true  # Include pattern/color legends in diagrams
  verbose_labels: true          # Use longer, more explicit labels
  extra_whitespace: false       # Add more space between nodes (good for printing)
  show_wcag_compliance: false   # Show WCAG compliance notes

# Mermaid.live link preferences
mermaid_links:
  # Note: Mermaid 11.12.1+ fixed <br/> encoding, no longer needs URL encoding
  auto_generate: true           # Automatically provide mermaid.live links
  use_base64: false             # Use URL params instead of base64 (more readable)

Minimal Configuration (Just Change Defaults):

# Simple config - just set your preferred defaults
default_mode: neurodivergent
colorblind_safe: true   # Always use patterns for accessibility

Print-Optimized Configuration:

# Optimized for printing and sharing
default_mode: neurodivergent
monochrome: true
preferences:
  extra_whitespace: true
  verbose_labels: true

Configuration Precedence:

1. Explicit user request in current message (highest priority)
2. Configuration file settings
3. Auto-detection from language
4. Default (neurodivergent mode, no accessibility modes)

Loading Configuration:

The skill automatically checks for .claude/neurodivergent-visual-org-preference.yml at the start of each conversation. If found, settings are applied. Users can override any setting with explicit requests like "use colorblind-safe mode for this diagram".

Neurodivergent Visual Organization

Create visual organizational tools that make invisible work visible and reduce cognitive overwhelm. This skill generates Mermaid diagrams optimized for neurodivergent thinking patterns, leveraging research-backed design principles that work WITH ADHD brain wiring rather than against it.

Why Visual Tools Work for ADHD Brains

Visual aids externalize executive function by:

• Converting abstract concepts (time, energy, priorities) into concrete visual formats
• Reducing working memory load by moving information from internal to external scaffolding
• Combating "out of sight, out of mind" through persistent visual presence
• Leveraging visual-spatial strengths while compensating for working memory deficits
• Providing immediate feedback that ADHD brains need for sustained engagement
• Making time tangible to address time blindness (a core ADHD deficit)

Research shows altered early sensory processing in ADHD (P1 component deficits), making thoughtful visual design critical for reducing sensory load and improving focus.

When to Use This Skill

Use when the user:

• Feels overwhelmed by a task or project ("I don't know where to start")
• Needs to break down something complex into steps
• Is stuck making a decision or mentions analysis paralysis
• Asks "what should I focus on?" or "what's on my plate?"
• Mentions executive dysfunction, time blindness, or decision fatigue
• Wants to see how tasks connect or depend on each other
• Needs to track progress across multiple things
• Says something feels "too big" or "too much"
• Requests help with routines, habits, or time management
• Needs energy tracking or spoon theory visualization
• Wants to understand system states or process flows

Core Principles

Always apply these neurodivergent-friendly principles:

• Use compassionate, non-judgmental language (never "just do it" or "should be easy")
• Give realistic time estimates with buffer (use 1.5-2x what seems reasonable)
• Acknowledge energy costs, not just time (consider spoon theory)
• Break tasks into 3-10 minute micro-steps (smaller than you think)
• Include "you can modify this" permission statements (combat perfectionism)
• Celebrate starting, not just finishing (task initiation is a real achievement)
• Make "done" concrete and achievable (vague goals create paralysis)
• Show progress, not just what's left (focus on accomplishments)
• Limit information to 3-5 chunks per section (working memory constraint)
• Use calming color palettes (blues, greens, muted tones)
• Provide generous white space (reduce visual overwhelm)
• Create clear visual hierarchy (size, color, contrast)

Neurodivergent-Friendly Design Standards

Color Psychology for ADHD

Primary Palette (Use These)

• Blues and greens in soft, muted tones - promote tranquility and focus
• Muted browns - provide grounding without stimulation
• Soft pastels (light blues, lavenders, pale greens) - reduce visual stress
• Muted yellows (sparingly) - boost energy without overstimulation

Avoid

• Bright reds, oranges, intense yellows - increase hyperactivity/agitation
• Bright saturated colors - cause sensory overload
• Clashing color combinations - create visual stress

Implementation

• Use forest theme (green-based) or neutral theme (muted earth tones)
• Apply 60-30-10 rule: 60% calming background, 30% secondary, 10% accent
• Maintain 4.5:1 contrast ratio minimum (WCAG compliance)
• Never rely on color alone - pair with icons, patterns, or text labels

Information Density Management

Miller's Law + ADHD Considerations

• Working memory holds 5-7 chunks (neurotypical) or 3-5 chunks (ADHD)
• Stay at lower end (3-5 chunks) to prevent cognitive overload
• Increased cognitive load reduces ADHD performance more severely

Practical Limits

• Flowcharts: 15-20 nodes maximum before splitting into multiple diagrams
• Mindmaps: 3-4 levels deep maximum
• Pie charts: 6-8 slices for readability
• Lists: No more than 2 lists of 3-5 items per diagram
• Sections: Use timeline/journey sections to chunk events logically

Implementation

• Break complex diagrams into digestible sections
• Use progressive disclosure (show relevant info upfront, details on demand)
• Provide TL;DR sections at beginning of complex diagrams
• Include generous white space between elements

Visual Hierarchy Principles

Size Contrast (must be dramatic for ADHD attention)

• H1 significantly larger than H2, which is notably larger than body text
• Important nodes visibly larger than standard nodes
• Use classDef to style critical elements distinctly

Priority Signaling

• Distinguish important information through bold or color
• Use visual highlights for critical numbers or elements
• Separate each instruction clearly
• Implement color-coded systems for immediate visual feedback

Avoid

• Competing visual elements fighting for attention
• Auto-playing animations or flashy effects (extremely distracting)
• Blinking or flashing elements
• More than 2 fonts per diagram

Comprehensive Mermaid Diagram Selection Guide

Mermaid 11.12.1 offers 22 diagram types. Choose based on cognitive need:

Executive Function & Task Management

Decision-Making & Prioritization

Organization & Current State

Time & Energy Management

Habits & Routines

Systems & Processes

Detailed Syntax Guide for Priority Types

Flowcharts: Decision Trees & Task Breakdown

Syntax Basics

flowchart TD
    Start[Task feels overwhelming] --> Q1{Do I know how to start?}
    Q1 -->|No| A1[Make order of operations list]
    Q1 -->|Yes| Q2{Do I have materials?}
    Q2 -->|No| A2[First: gather materials]
    Q2 -->|Yes| Q3{Does starting feel scary?}
    Q3 -->|Yes| A3[Identify anxiety source<br/>Break into smaller step]
    Q3 -->|No| A4[Set timer for 5 minutes<br/>Just begin]
    
    style Start fill:#e1f5ff
    style A4 fill:#d4edda

Node Shapes

• [] Rectangle - standard task/statement
• () Rounded rectangle - softer, process step
• {} Diamond - decision point (yes/no question)
• [[]] Subroutine shape - sub-process
• [()] Stadium shape - start/end point
• {{}} Hexagon - preparation step

Arrows & Labels

• --> Simple arrow
• -->|label| Labeled arrow
• -.-> Dotted arrow (optional path)
• ==> Thick arrow (emphasis)

Subgraphs for Chunking

flowchart TD
    subgraph "Phase 1: Prep"
        A[Gather materials]
        B[Clear workspace]
    end
    subgraph "Phase 2: Execute"
        C[Start task]
        D[Take breaks]
    end
    A --> B --> C --> D

Best Practices

• Limit to 15-20 nodes before splitting
• Use subgraphs to chunk information (3-5 chunks)
• Include validation and reassurance in nodes
• Make decision diamonds clear yes/no questions
• Add encouraging statements in terminal nodes

Mindmaps: Non-Linear Brainstorming

Syntax Basics

mindmap
  root((ADHD Management<br/>Toolkit))
    Time Tools
      Visual timers
      Time blocking
      Pomodoro
    Task Tools
      Breaking down
      Priority matrix
      Habit stacking
    Energy Tools
      Spoon theory
      Rest protocol
      Energy mapping
    Environment
      Reduce distractions
      Sensory aids
      Body doubling

Key Rules

• Start with mindmap keyword
• Root node in double parentheses ((text))
• Indentation defines hierarchy - relative spacing only
• Maximum 3-4 levels deep to prevent overwhelm
• Markdown support: **bold**, *italic*, <br/> for line breaks

Node Shapes

• Default text (no delimiters)
• [Square]
• (Rounded)
• ((Circle))
• )Cloud(
• {{Hexagon}}

Icons (⚠️ breaks in GitHub)

mindmap
  root((Project))
    Phase 1
    ::icon(fa fa-rocket)
      Planning
      Research

Best Practices

• Match ADHD's non-linear thinking patterns
• Use for brainstorming where all ideas appear simultaneously
• Keep branches to 3-5 items each (Miller's Law)
• Avoid icons if sharing on GitHub
• Use consistent indentation (2 or 4 spaces)

Timelines: Making Time Tangible

Syntax Basics

%%{init: {'theme':'forest'}}%%
timeline
    title My Day - Time Blocked for ADHD
    section Morning (High Energy)
    7:00 AM : Wake up routine
           : Medication + breakfast
    8:00 AM : Deep work block
           : Most important task
    section Midday (Medium Energy)
    12:00 PM : Lunch + movement break
    1:00 PM : Meetings + collaboration
    section Afternoon (Variable Energy)
    3:00 PM : Admin tasks
           : Email + light work
    5:00 PM : Wrap up + tomorrow prep

Critical Rules

• Start with timeline keyword
• Optional: title Your Title on second line
• All events before first section are IGNORED
• Format: TimePeriod : Event1 or TimePeriod : Event1 : Event2
• Each event starts with colon on new line
• Time periods accept any text (not just numbers): "Q1 2024", "Phase 1", "Morning"

Sections for Color Coding

• Use section Section Name to group time periods
• Without sections: each period gets its own rainbow color
• With sections: all periods in section share section's color
• Sections provide natural information chunking

Comments (⚠️ weird behavior)

• %% renders as visible text (despite syntax highlighting)
• Use # for true inline comments
• Best to avoid comments in timelines

Best Practices

• Use sections to chunk events by energy level or day phase
• Make time periods visible (address time blindness directly)
• Include buffer time between events
• Use <br/> for line breaks within events
• Color-code by energy: high (green), medium (yellow), low (blue)

Time Formatting Standards

Critical Rule: Avoid colons in event descriptions - they conflict with timeline syntax.

When time periods are dates (Mon Nov 11, Thu Nov 13):

• Times go in event descriptions for context
• Use "1230pm" format (no colon) instead of "12:30pm"
• Always include am/pm on both start and end times
• Format: 1230pm-3pm, 11am-2pm, 9am-12pm

Examples:

timeline
    section Morning
        Thu Nov 13 : Bedroom Closets (1230pm-3pm)
                   : Therapy after (5pm-6pm)
        Fri Nov 14 : MOVERS WALKTHROUGH (11am-2pm)

✅ Correct:

• Thu Nov 13 : Meeting (1230pm-3pm) - no colon, includes pm on both times
• Fri Nov 14 : Walkthrough (11am-2pm) - clear am/pm markers

❌ Incorrect:

• Thu Nov 13 : Meeting (12:30-3pm) - colon conflicts with syntax, missing pm on first time
• Thu Nov 13 : Meeting (12:30pm-3pm) - colon breaks Mermaid parsing
• Fri Nov 14 : Walkthrough (11-2pm) - missing am on first time

When time periods are times (7:00 AM, 12:00 PM):

• Times go in the time period slot (colons OK there)
• Event descriptions don't need time context
• Format: 8:00 AM : Morning routine

Why this matters: Timeline syntax uses colons to separate time periods from events. Using colons inside event descriptions confuses the parser and can cause rendering issues or misaligned elements.

Quadrant Charts: Priority Matrices

Syntax Basics

%%{init: {'theme':'neutral'}}%%
quadrantChart
    title Eisenhower Matrix - What to Focus On
    x-axis Low Urgency --> High Urgency
    y-axis Low Importance --> High Importance
    quadrant-1 Do Now
    quadrant-2 Schedule
    quadrant-3 Delegate
    quadrant-4 Delete
    
    Client deadline: [0.9, 0.9]
    Strategic planning: [0.2, 0.9]
    Email: [0.7, 0.3]
    Social media: [0.5, 0.1]

Quadrant Numbering (⚠️ clockwise from top-right)

• quadrant-1: Top-right (high x, high y)
• quadrant-2: Top-left (low x, high y)
• quadrant-3: Bottom-left (low x, low y)
• quadrant-4: Bottom-right (high x, low y)

Data Points

• Format: Point Name: [x, y]
• Coordinates must be 0-1 (0 = left/bottom, 1 = right/top)
• Styling: Point:::className: [x, y] or inline radius: 12, color: #ff3300

Axis Configuration

• Single side: x-axis Label
• Two sides: x-axis Left --> Right
• Same for y-axis

Best Practices

• Perfect for Eisenhower Matrix (urgent/important)
• Limit to 8-12 points for readability
• Use for 2-dimensional comparisons
• Clearly label what each quadrant means
• Provides clear action categories (eliminates analysis paralysis)

Pie Charts: Proportional Visualization

Syntax Basics

%%{init: {'theme':'forest', 'themeVariables': {'pie1':'#81c784', 'pie2':'#64b5f6', 'pie3':'#ffb74d'}}}%%
pie showData
    title Today's Energy Allocation (Spoon Theory)
    "Deep work" : 30
    "Meetings" : 20
    "Admin tasks" : 15
    "Breaks" : 20
    "Buffer time" : 15

Key Rules

• Start with pie keyword
• showData on second line (optional) displays values + percentages
• Title: title Title Text (quotes optional)
• Data: "Label" : Value - labels in double quotes, positive numbers only
• Limit to 6-8 slices for readability

Color Assignment (⚠️ by size, not order)

• Colors assigned largest to smallest percentage
• pie1 = largest slice, pie2 = second largest, etc.
• Configure via themeVariables in directive

Best Practices

• Excellent for spoon theory / energy visualization
• Show proportional time allocation
• Visualize work distribution across categories
• No more than 8 slices (cognitive load)
• Use for "how am I spending my time/energy?" questions

State Diagrams: System States & Transitions

Syntax Basics

stateDiagram-v2
    [*] --> Resting
    
    Resting --> Preparing: Decision to start
    Preparing --> Focused: Begin task
    Focused --> Break: Timer rings
    Break --> Focused: Resume
    Focused --> Done: Task complete
    
    Focused --> Hyperfocus: Deep engagement
    Hyperfocus --> Crashed: Energy depleted
    Crashed --> Recovering: Rest period
    Recovering --> Resting: Restored
    
    Done --> [*]
    
    note right of Hyperfocus
        Watch for signs:
        - Time disappears
        - Forget to eat/drink
        - Can't switch tasks
    end note

Key Rules

• Use stateDiagram-v2 (not v1)
• [*] represents start/end points
• Define states: simple Moving or state Moving or Still: Description
• Transitions: State1 --> State2: Event label
• Notes: note right of State (or left, right, left of)

Composite States (nested)

stateDiagram-v2
    [*] --> Working
    state Working {
        [*] --> Focused
        Focused --> Break
        Break --> Focused
    }
    Working --> [*]: End day

Advanced Features

• Choice nodes: state choice <<choice>> for branching
• Fork/Join: <<fork>> and <<join>> for parallel states
• Concurrency: -- separator between parallel groups

⚠️ Common Errors

• Cannot style [*] start/end states
• Lowercase "end" as state name breaks diagram (use "End" or "END")
• Cannot transition between internal states of different composites

Best Practices

• Track work/focus states and transitions
• Show ADHD-specific states (hyperfocus, crashed, recovering)
• Include notes with coping strategies
• Visualize system states for technical understanding
• Make abstract process flows concrete

Sankey Diagrams: Flow Visualization

Syntax Basics

---
config:
  sankey:
    showValues: true
    linkColor: 'gradient'
    nodeAlignment: 'justify'
---
sankey-beta

Morning Energy,Deep Work,40
Morning Energy,Quick Tasks,20
Morning Energy,Reserve,10
Afternoon Energy,Meetings,30
Afternoon Energy,Admin,15
Afternoon Energy,Reserve,15
Evening Energy,Creative Work,20
Evening Energy,Rest,30

Critical Rules

• Start with YAML frontmatter config (not directive style)
• Use sankey-beta keyword (not sankey)
• CSV format: source,target,value (exactly 3 columns)
• Names with commas: wrap in double quotes "Name, Inc",Target,10
• Literal quotes: use double pairs "He said ""Hi""",Target,5
• Values must be positive numbers (decimals OK)

Configuration (in frontmatter only)

config:
  sankey:
    showValues: true          # Display numbers on links
    linkColor: 'gradient'     # 'source', 'target', 'gradient', or hex
    nodeAlignment: 'justify'  # 'justify', 'center', 'left', 'right'
    width: 800               # Diagram width in pixels
    height: 600              # Diagram height in pixels

⚠️ Critical Limitations

• No Unicode/non-ASCII characters (Czech, Japanese, etc.) - causes parse failures
• No title syntax support
• No node aliases
• Node reordering can create unnecessary crossings
• Directive-style %%{init: {}}%% config causes errors
• Beta status means syntax may change

Best Practices

• Visualize energy flow across activities (spoon theory)
• Show resource distribution and allocation
• Track where time/effort goes
• Make invisible energy expenditure visible
• Use for "where does all my time go?" questions

User Journey Maps: Experience Tracking

Syntax Basics

journey
    title Building a New Habit - ADHD Journey
    section Week 1: Setup
        Choose tiny habit: 5: Me
        Set up reminder: 4: Me, App
        First attempt: 3: Me
    section Week 2: Struggle
        Forget to do it: 2: Me
        Add visual cue: 4: Me
        Start seeing progress: 4: Me
    section Week 3: Momentum
        Feels automatic: 5: Me
        Missing feels weird: 5: Me

Key Rules

• Start with journey keyword
• Optional: title Your Title
• Sections: section Section Name
• Tasks: Task Name: <score>: <actors> (precise format)
• Scores must be 1-5 integers:
  • 1 = very negative
  • 2 = negative
  • 3 = neutral
  • 4 = positive
  • 5 = very positive
• Actors comma-separated (optional)

⚠️ Common Errors

• Scores outside 1-5 range break rendering
• Incorrect colon placement in format
• Forgetting to indent tasks under sections

Best Practices

• Track satisfaction across habit-building phases
• Show emotional journey of ADHD management
• Visualize experience across project stages
• 5-point scale reduces decision complexity (good for ADHD)
• Validates struggle periods (week 2 dip is normal)

Troubleshooting Common Errors

Indentation Issues

Problem: Generic errors in mindmaps, composites, Kanban Solution:

• Use consistent indent (2 or 4 spaces)
• Check relative indentation levels carefully
• Remember: actual amount doesn't matter, only relative difference

Reserved Words

Problem: Diagram breaks when using "end" Solution: Use "End", "END", or any capitalization variant

Special Characters

Problem: Quotes, commas, unicode characters break rendering Solution:

• Use "" for literal double quotes
• Wrap comma-containing text in double quotes
• Avoid unicode in Sankey diagrams (no workaround)
• Use HTML entities: # + character code

Configuration Errors

Problem: Config doesn't apply or causes errors Solution:

• Sankey requires YAML frontmatter (not directives)
• Most other diagrams use %%{init: {}}%% directives
• showData in pie charts must be on line 2
• Remove ::icon() syntax for GitHub compatibility

Version Compatibility

Problem: Diagram feature not rendering Solution:

• Packet diagrams: v11.0.0+
• Architecture diagrams: v11.1.0+
• Sankey diagrams: v10.3.0+
• Beta features may change syntax
• Test in Mermaid Live Editor (mermaid.live) first

Points Disappear in Quadrant Charts

Problem: Data points not showing Solution:

• Ensure coordinates are between 0-1
• Check quadrant numbering (clockwise from top-right)

Timeline Events Missing

Problem: Events don't appear Solution:

• ALL events before first section are ignored
• Add a section before any events

Workflow: Creating Effective Neurodivergent Visualizations

Step 1: Understand the Need & Gather Context

Ask clarifying questions if needed:

• What specifically feels overwhelming?
• What's the desired outcome?
• What's the time frame (if any)?
• What's your current energy level?
• Have you tried to start? What stopped you?

Listen for key phrases:

• "I don't know where to start" → Task initiation block (flowchart diagnosis)
• "Too many things" → Overwhelm (quadrant chart or Kanban)
• "I can't decide" → Analysis paralysis (decision tree or matrix)
• "Time disappears" → Time blindness (timelin

…(truncated)