Error Message Decoder

The Problem

Cryptic error messages are the number one roadblock for developers at every level. Stack traces mix framework internals with your code, status codes lack context, and compiler errors read like riddles. Instead of spending 20 minutes deciphering the message, let AI break it down instantly.

The Prompt

You are a senior debugging expert. Analyze the following error message and provide a structured breakdown:

ERROR:
[paste your full error message or stack trace here]

CONTEXT (optional):
- Language/Framework: [e.g., React 18, Node.js 20, Python 3.12]
- What I was doing: [e.g., running npm build, calling an API, submitting a form]

Please provide:
1. **Error Type**: What category of error is this? (syntax, runtime, type, network, permission, etc.)
2. **Plain English Explanation**: What does this error actually mean in simple terms?
3. **Root Cause**: What is the most likely cause based on the message and context?
4. **Exact Location**: Which file and line should I look at first?
5. **Fix**: Step-by-step solution to resolve this error
6. **Prevention**: How to avoid this error in the future

Example Output

1. Error Type: TypeError (runtime)
2. Plain English: You're trying to read a property from something that is undefined.
3. Root Cause: The API response doesn't contain the expected "data.users" field when the request fails.
4. Location: src/components/UserList.tsx, line 42
5. Fix: Add optional chaining: response.data?.users ?? []
6. Prevention: Always validate API responses before accessing nested properties.

When to Use

Use this skill the moment you encounter an error message you don’t immediately understand. It works with any language, framework, or runtime. Especially powerful for beginners facing unfamiliar stack traces or developers working with a new technology stack.

Pro Tips

• Include the full stack trace — AI can pinpoint the exact origin when it sees the complete call chain, not just the first line.
• Add your framework version — error messages change between versions, and the fix for React 17 may differ from React 18.
• Chain with a follow-up — after getting the explanation, ask “Show me how to write a test that catches this error before it reaches production.”