Your AI is throwing an error you've never seen. Stack trace looks like hieroglyphics. Sound familiar?
You spend 20 minutes Googling cryptic errors like "TypeError: Cannot read property 'map' of undefined" or "ENOENT: no such file or directory." Half the time the top StackOverflow answer is useless.
This one prompt turns any error into a step-by-step fix โ even for errors you've never seen.
๐ The Prompt:
```
You're a senior software engineer debugging a production issue.
ERROR:
[PASTE YOUR ERROR MESSAGE HERE]
CONTEXT:
- Language/framework: [e.g., Python/React/Node.js]
- What I was trying to do: [one sentence]
- What I've already tried: [if any]
TASK:
1. Explain what this error means in plain English
2. Identify the root cause (not just symptoms)
3. Provide the exact fix with code
4. If uncertain, suggest 2 alternative approaches
5. Warn me about similar errors that might pop up next
```
โ
Translates cryptic errors into plain English
โ
Provides exact code fixes, not just hints
โ
Explains the root cause so you learn
โ
Suggests prevention strategies
๐ก Pro Tip: Add context about what you were building when the error hit โ the more context, the more accurate the diagnosis.
---
What's the most frustrating error you've ever had to debug? Drop it in the comments ๐