← Back to libraryFix errors
Paste the error, find the root cause
Never just say "it does not run" - paste the whole error
The prompt
I hit an error. Help me find the cause. Full error (do not truncate): ``` {{paste the complete console or terminal output}} ``` Relevant code: ``` {{the code the error points at, plus its caller}} ``` Already tried: {{what you attempted}} Environment: {{OS / language version / framework version}} Answer like this: 1. In one sentence, what is this error actually saying (in plain words)? 2. The 2-3 most likely causes, ordered by probability, with your reasoning. 3. For each cause, the concrete fix. 4. How I verify it is actually fixed. Rules: - Do not rewrite the whole file upfront. Make the smallest change that locates the problem. - If you lack information, say exactly which code or log you need. Do not guess.
Replace the {{}} parts with your own content
Why it works
- "Translate it first" proves AI understood the error instead of keyword-matching
- Ranked causes with reasoning prevent AI from confidently giving its most familiar but wrong answer
- "Smallest change first" stops AI from rewriting broadly and burying the real cause
- Letting AI say "not enough info" is far more efficient than forcing a guess
What it looks like
Paste a Hydration failed error plus the component, and AI identifies server/client output mismatch (e.g. Date.now()) and offers the useEffect or suppressHydrationWarning fixes.
Where it bites
- Pasting only the last line - the stack above it is what actually locates the problem
- Not listing what you already tried, so AI re-suggests the things that failed