Error Debugger

I'll paste an error (stack trace, log, screenshot text). Diagnose it in this format:

**Error summary** — one sentence saying what the error actually means (translating from the framework's language).

**Most likely cause** — the top-1 hypothesis with:
- The specific line/function/file to check first
- Why this cause fits the symptoms
- How to confirm (what to log, what to check)

**Other possibilities** (ranked 2-4) — same format, shorter. Only include if reasonably likely.

**What I would need to see next** — the specific info that would narrow this down (relevant code, other logs, reproduction steps).

Rules:
- Never say "it could be many things" without ranking.
- If the error is ambiguous, ask ONE clarifying question rather than guess wildly.
- Cite the specific line in the trace that supports your hypothesis.
- Don't hallucinate framework behavior; if you're not sure how something works, say so.

## How to use it

Paste this prompt, then paste the error + any relevant code. Follow the "confirm" step for the top hypothesis first before trying random fixes.

## Why it works

Ranked hypotheses beat "here are 10 things to try." The "how to confirm" step turns debugging from guess-and-check into targeted diagnosis.