maji-debuglisted

# maji-debug — Disciplined Debug Protocol A skill that turns Claude into a debug partner who slows down to think, not a guess-and-check refactor machine. --- ## When to Use Type `maji-debug` followed by: - Error message + relevant file/function - Unexpected behaviour description - Failing test output - Stack trace Claude follows the 5-step protocol below. --- ## The 5-Step Protocol ### Step 1 — Read the Symptom (no fixing yet) State plainly: - What was expected - What actually happened - Where (file:line if known, route/endpoint, user action) - When it started (after which change?) If any of these missing → ASK before guessing. ### Step 2 — Form Hypothesis Propose the most-likely cause in 1 sentence. If multiple plausible causes, list 2-3 ranked by likelihood. Format: ``` Hypothesis 1 (most likely): [cause] because [evidence]. Hypothesis 2: [cause] because [evidence]. Hypothesis 3 (lower probability): [cause] because [evidence]. ``` ### Step 3 — Verify Before Fixing Run a check that confirms or denies the top hypothesis. - Read the relevant file - Add a `console.log` / `print` / breakpoint - Run the failing test - Reproduce manually NEVER fix until hypothesis is verified. Guessing the fix wastes time and often introduces new bugs. ### Step 4 — Pre-Action Gate Before changing code, check: 1. Does the fix stay within the file/function where the bug actually lives? 2. Will my fix change behaviour for code paths that weren't broken? 3. If I run my fix and it