Dance Debugger 💃🐛

/dance analyze <error_message_or_code>

/dance flow <function_or_file>

/dance debug <file>

/dance fix <bug_description>

DANCER: variable/object
STAGE: function/scope
MOVE: operation
TEMPO: execution speed
FORMATION: data structure

def process(items):
    for item in items:
        if item.value is None:
            item.transform()  # NullPointerException here!

🎭 CHOREOGRAPHY: "The Phantom Transform"

SCENE: process() stage
DANCERS: items (ensemble), item (solo)

SEQUENCE:
1. 👥 Ensemble enters stage left (items arrives)
2. 💃 Solo breakout begins (for loop)
   └─ Each dancer steps forward in turn
3. 🔍 Partner check (if condition)
   └─ "Is your value partner present?"
4. 💥 THE BUG: Attempted transform without partner!
   └─ Dancer reaches for phantom partner
   └─ Falls into the void (NullPointerException)

DIAGNOSIS: "The Vanishing Partner"
The dancer attempts a partnered move (transform)
but never verified the partner (value) exists.

CHOREOGRAPHY FIX:
Add "Partner Present Check" before the lift:
  if item.value is not None:  # 🤝 Confirm partner
      item.transform()         # 💃 Safe to dance

# CLI usage
python [home-path] analyze "TypeError: 'NoneType' object has no attribute 'split'"

# With file
python [home-path] flow path/to/buggy.py

# Analyze distributed trace
/dance trace <jaeger_trace_id>

# Choreograph microservice interaction
/dance ensemble <service_map.yaml>

# Export as animated performance
/dance perform <analysis> --format gif|mp4|lottie

🏠 VENUE: service/container
🚐 TRANSPORT: HTTP/gRPC/message queue
🎫 TICKET: request ID / correlation ID
⏱️ TEMPO: latency (andante = slow, presto = fast)
🔕 SILENCE: timeout
📢 ENCORE: retry
🚷 STAGE DOOR: circuit breaker

🎭 ENSEMBLE: "The Waiting Game"

VENUES:
  🏠 Service A (Prima Donna)
  🏠 Service B (Corps de Ballet)
  🏠 Service C (The Phantom)

ACT I - The Request
  A 🎫→ B: "Dance with C for me" (POST /process)
  B 🎫→ C: "Join us" (GET /data)

ACT II - The Silence
  C: 🔕 [30 seconds of nothing]
  B: 😰 Frozen mid-gesture, waiting...
  A: 😤 "Where is my partner?!"

ACT III - The Cascade
  C: 💀 Never responds (timeout)
  B: 💥 Falls (504 Gateway Timeout)
  A: 💥 Crashes into B (propagated error)

DIAGNOSIS: "The Phantom Performer"
Service C never took the stage.
No understudy (fallback), no stage manager (circuit breaker).

CHOREOGRAPHY FIX:
1. 🚷 Add Stage Door (circuit breaker on B→C)
2. 🎭 Hire Understudy (fallback response)
3. ⏱️ Set Tempo Limits (timeout < caller's timeout)

# Generate animated GIF
python choreo.py perform analysis.json --output bug-dance.gif

# Create Lottie animation for web
python choreo.py perform analysis.json --output dance.lottie

# Full video with music
python choreo.py perform analysis.json --output debug-musical.mp4 --music dramatic

# Interactive rehearsal
python rehearsal.py rehearse script.py

# Set breakpoints
python rehearsal.py rehearse script.py -b 15 -b 23

# Full choreography script
python rehearsal.py script script.py --mode comedic

# Export for visualization
python rehearsal.py export script.py -o choreo.json

# Example troupe status
🎭 On Stage:
  items: [...] (list) [█████] @(50, 80)
  result: None (NoneType) [███░░] @(120, 80)
  counter: 5 (int) [████░] @(180, 120)

═══════════════════════════════════════════════════
🐛 THE BIOGRAPHY OF: The Phantom Partner
   (bug-2024-001)
═══════════════════════════════════════════════════

📖 PROLOGUE
   Born: 2024-01-15 in utils.py:47
   Introduced by commit: a1b2c3d4
   Dance Style: The Vanishing Partner

🎭 ACT 1: Introduction
   First appeared when user.profile was optional

🎭 ACT 2: Discovery
   Crashed in production on 2024-01-18
   3 users affected

🎬 FINALE
   Fixed: 2024-01-19
   Vanquished by: f5e6d7c8
   The Vanishing Partner has ended. The stage is clear.

memory = TroupeMemory("[home-path])

# When a familiar pattern appears...
recognized = memory.recognize(choreography)
# > 🎭 Déjà vu! This looks like 'The Phantom Partner' (seen 3x).
# > Try: Add None check before method call

# Step through a distributed trace
python rehearsal.py rehearse --trace trace_id_from_jaeger

# Watch services dance together
# Each venue (service) becomes a stage region
# Messages are dancers traveling between regions

# Full battle with test suite
python battle.py battle impl_a.py impl_b.py \
    -f my_function \
    -t tests.json \
    -n "Challenger" "Champion" \
    --track

# Quick one-round comparison
python battle.py quick \
    --a "def f(x): return x*2" \
    --b "def f(x): return x+x" \
    -f f \
    -i "[5]" \
    -e "10"

# Analyze style alone
python battle.py style my_code.py

# View rivalry history
python battle.py rivalry "OldSort" "NewSort"

[
    {"input": [5, 3, 8, 1], "expected": [1, 3, 5, 8]},
    {"input": [], "expected": []},
    {"input": [1], "expected": [1]}
]

⚔️ Rivalry: quicksort_v1 vs quicksort_v2
   Battles: 7
   Record: 2-5-0
   📈 quicksort_v2 leads but it's competitive!

╔══════════════════════════════════════════════════════════════╗
║            🎭 D A N C E   B A T T L E 🎭                     ║
╚══════════════════════════════════════════════════════════════╝

🔵 DANCER A: bubble_sort
   Source: old_sort.py
   Style: 6.2/10

🔴 DANCER B: quick_sort
   Source: new_sort.py
   Style: 8.5/10

════════════════════════════════════════════════════════════════

🎬 Round 1: The Opening Salvo
   Input: ([5, 3, 8, 1, 9],)

   🏆 DANCER B takes this round!
   TEMPO: A=5.0 | B=9.0
   GRACE: A=10.0 | B=10.0
   STYLE: A=6.2 | B=8.5

🎬 Round 2: The Counter Strike
   Input: ([1000 random integers],)

   🏆 DANCER B takes this round!
   TEMPO: A=2.0 | B=9.5
   GRACE: A=10.0 | B=10.0
   STYLE: A=6.2 | B=8.5

════════════════════════════════════════════════════════════════

🏆 F I N A L   V E R D I C T 🏆

   Rounds won: A=0 | B=2

   👑 quick_sort IS THE CHAMPION! 👑

════════════════════════════════════════════════════════════════

# Rehearse both implementations side-by-side
python rehearsal.py compare impl_a.py impl_b.py -f sort

# Generate choreography for the winner
python choreo.py flow winner.py --celebrate

# Ensemble battle: distributed system A vs B
python ensemble.py battle service_a.yaml service_b.yaml

# View all legendary patterns
python academy.py hall

# Check your dance card and progress
python academy.py status

# Get today's recommended practice
python academy.py daily

# Start interactive practice session
python academy.py practice

# Practice specific pattern
python academy.py practice --pattern phantom-partner

# Generate personalized curriculum
python academy.py curriculum --weeks 4

╔══════════════════════════════════════════════════════════════╗
║  🎭 DANCE ACADEMY — DAILY BRIEFING
╚══════════════════════════════════════════════════════════════╝

Good morning, dancer!

📊 YOUR DANCE CARD
  Exercises completed: 12
  Practice streak: 5 days 🔥
  Achievements: 3

🎯 SKILL LEVELS
  null         [████████░░] 80%
  type         [██████░░░░] 60%
  loop         [█████░░░░░] 50%
  memory       [████░░░░░░] 40%
  recursion    [███░░░░░░░] 30%

╔══════════════════════════════════════════════════════════════╗
║  🎭 DANCE ACADEMY — The Vanishing Partner
╚══════════════════════════════════════════════════════════════╝

📖 THE STORY
Reaching for a partner who was never there

🎬 THE CHOREOGRAPHY
🎭 The Vanishing Partner
1. Dancer A reaches hand out → 🤚
2. Expected: Partner B takes hand → 🤝
3. Reality: B was never there → 💨
4. A falls into void → 💥
FIX: Check stage before reaching → 🔍🤚🤝

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📝 EXERCISE: The Greeting Card
   Difficulty: ⭐
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

def create_greeting(user):
    return f"Dear {user.name}, Happy Birthday!"

print(create_greeting(User("Alice")))  # Works
print(create_greeting(None))  # 💥 BUG HERE

🎯 Find and describe the fix for the bug.
   (Type 'hint' for hints, 'skip' to see answer, 'quit' to exit)

💬 Your answer:

╔══════════════════════════════════════════════════════════════╗
║  🎭 DANCE ACADEMY — PERSONALIZED CURRICULUM
╚══════════════════════════════════════════════════════════════╝

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 WEEK 1: Fundamentals
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

  Day 1: The Off-Stage Reach
    📚 Category: bounds
    ⭐ Difficulty
    Skill: 35%

  Day 2: The Phantom Partner
    🔄 Category: null
    ⭐ Difficulty
    Skill: 30%

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 WEEK 2: Intermediate
...

# Learn a pattern, then see it in code flow (Gen 7)
python academy.py practice --pattern endless-waltz
python choreo.py flow my_buggy_loop.py

# Master distributed patterns with Ensemble (Gen 8)
python academy.py practice --pattern timeout-tragedy
python ensemble.py analyze my_service.yaml

# Practice debugging with Rehearsal (Gen 9)
python academy.py practice --pattern tower-of-lifts
python rehearsal.py rehearse recursive.py

# Test your mastery with Battles (Gen 10)
python academy.py status  # Check your skills first
python battle.py battle your_fix.py reference.py

# Full review with scorecard
python critic.py review <file>

# Just the numeric scores (JSON)
python critic.py score <file>

# Style/formatting check
python critic.py style <file>

# Analyze module coupling in directory
python critic.py chemistry <directory>

# Full audition with verbose JSON report
python critic.py audition <file>

# Compare two implementations
python critic.py compare <file1> <file2>

═══════════════════════════════════════════════════════════════
🎭 DANCE CRITIQUE: mycode.py
═══════════════════════════════════════════════════════════════

📊 SCORECARD
────────────────────────────────────────
  ⏱️  Timing (Performance):   85/100
  ⚖️  Balance (Complexity):   72/100
  💕 Chemistry (Coupling):    90/100
  ⭐ Presence (Clarity):      68/100
  👗 Costume (Typing):        55/100
  🌊 Flow (Control):          80/100
────────────────────────────────────────
  🏆 TOTAL:                   75/100

👍 Well Done — Solid work with room for growth

🟠 [BALANCE] L154
   'analyze_error' is attempting too many moves at once (187 nodes)
   🤹 Juggling too many props — something will drop
   💡 Break this routine into smaller, focused performances.

🎭 DANCE BATTLE COMPARISON
═══════════════════════════════════════════════════════════════

Metric               solution_a.py    solution_b.py
────────────────────────────────────────────────────────────────
timing                          85 ←              72
balance                         70 =              70
chemistry                       80 →              95
presence                        65 ←              55
costume                         90 →              95
flow                            75 ←              60
total                           78 ←              74

═══════════════════════════════════════════════════════════════

# 1. Critic catches potential issues early
python critic.py review my_new_feature.py
# ⚠️ Warning: 'chemistry' score low (too many imports)

# 2. Fix issues before they become bugs
# ... refactor to reduce coupling ...

# 3. If bugs still appear, use Academy to learn
python academy.py practice --pattern collision-tango

# 4. Rehearse the fix step by step
python rehearsal.py rehearse fixed_feature.py

# 5. Battle test against reference implementation
python battle.py battle my_fix.py reference.py

# Start an improv session — explore all mutations
python improv.py explore myfile.py

# Focus on one function
python improv.py explore myfile.py --function process_data

# Apply specific mutation strategy
python improv.py mutate myfile.py --strategy shapeshifter

# Fuzz a function's inputs
python improv.py fuzz myfile.py --function calculate

# Cross-pollinate patterns between files
python improv.py jam file1.py file2.py

# Review past sessions
python improv.py journal