soleri-systematic-debugginglisted

# Systematic Debugging **Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure. ## Phase 0: Search Before Investigating **BEFORE touching any code:** ``` YOUR_AGENT_core op:search_intelligent params: { query: "<bug or error message>" } YOUR_AGENT_core op:brain_strengths YOUR_AGENT_core op:memory_search params: { query: "<error or symptom>" } ``` If vault has a match — apply it directly. Then search web: exact error message, GitHub issues, Stack Overflow, official docs. Only if vault and web produce no answer, proceed to Phase 1. ## Start a Debug Loop ``` YOUR_AGENT_core op:loop_start params: { prompt: "Debug: <bug>", mode: "custom" } ``` ## The Four Phases ### Phase 1: Root Cause Investigation 1. Read error messages carefully 2. Reproduce consistently 3. Check recent changes 4. Gather evidence at component boundaries 5. Trace data flow backward through call stack Track each step with `op:loop_iterate`. ### Phase 2: Pattern Analysis Find working examples, compare against references (read completely), identify differences, understand dependencies. Use `op:search_intelligent` for comparison. ### Phase 3: Hypothesis and Testing Form single hypothesis, test minimally (one variable at a time), verify before continuing. If unsure — ask for help. ### Phase 4: Implementation 1. Create failing test (use test-driven-development skill) 2. Implement single fix (root cause only) 3. Verify fix 4. If < 3 attempts failed, return to