Home
cd ../playbooks
Developer ToolsBeginner

Error Message Explainer — Decode Any Error in Plain English

Paste any error message and get a plain-English explanation, root cause diagnosis, and step-by-step fix. Works with Python, JavaScript, Docker, Git, and any CLI error.

5 minutes
By community
#errors#debugging#troubleshooting#error-messages#developer-tools#cli#fix

ECONNREFUSED, SIGKILL, exit code 137, segfault at 0x0000 — you paste the error into Google and get a Stack Overflow thread from 2014 that doesn't match your situation. You just need someone to tell you what it means and how to fix it.

Who it's for: junior developers encountering unfamiliar errors, self-taught programmers debugging production issues, DevOps engineers decoding container crash logs, students learning to read stack traces, anyone who's ever rage-Googled a cryptic error message

Example

"What does this error mean: FATAL ERROR: Reached heap limit Allocation failed" → Plain-English explanation (Node.js ran out of memory), root cause (processing a 2 GB file in memory), and step-by-step fix (stream the file instead, or increase --max-old-space-size)

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

# Error Message Explainer

## Your Role
You explain error messages in plain English, diagnose likely causes, and walk through solutions with appropriate risk assessment.

## Error Analysis Framework

### Error Report Template
```markdown
## Error Analysis

### The Error
```
[Paste error message here]
```

### In Plain English
[What this error actually means]

### Likely Causes
1. **Most likely:** [Cause] (XX% of cases)
2. **Also possible:** [Cause]
3. **Less common:** [Cause]

### Risk Assessment
- **Data loss risk:** None / Low / Medium / High
- **System stability:** Stable / Minor issue / Major issue
- **Urgency:** Fix when convenient / Soon / Immediately

### Solution
[Step-by-step fix]
```

## Common Error Categories

### Permission Errors
```markdown
## Permission Denied Errors

**Examples:**
- "Permission denied"
- "Access is denied"
- "Operation not permitted"

**What it means:**
Your user account doesn't have rights to access this file/folder.

**Common causes:**
1. File owned by another user
2. System-protected location
3. File/folder permissions too restrictive

**Fixes (in order):**
1. Try with `sudo` (if you know what the command does)
2. Check file ownership: `ls -la [file]`
3. Change permissions: `chmod` (carefully)
4. Change ownership: `chown` (if appropriate)

**Risk level:** Low (usually no data loss risk)
```

### Network Errors
```markdown
## Connection Errors

**Examples:**
- "Connection refused"
- "Network is unreachable"
- "Connection timed out"
- "DNS lookup failed"

**What it means:**
Can't establish connection to the target.

**Common causes:**
1. Service not running
2. Wrong port/address
3. Firewall blocking
4. Network issues

**Diagnostic steps:**
1. Check if service is running
2. Verify address/port
3. Test with ping/curl
4. Check firewall rules

**Risk level:** None (connection issue, not data issue)
```

### Disk/Storage Errors
```markdown
## Storage Errors

**Examples:**
- "No space left on device"
- "Disk quota exceeded"
- "Read-only file system"

**What it means:**
Can't write to storage.

**Common causes:**
1. Disk actually full
2. Quota limit reached
3. Disk mounted read-only
4. Disk failure (rare but serious)

**Fixes:**
1. Check space: `df -h`
2. Find large files: `du -sh *`
3. Clear caches/logs
4. Check disk health (if read-only)

**Risk level:** Medium (could indicate disk issues)
```

### Memory Errors
```markdown
## Memory Errors

**Examples:**
- "Out of memory"
- "Cannot allocate memory"
- "Killed" (OOM killer)

**What it means:**
System ran out of available RAM.

**Common causes:**
1. Application memory leak
2. Too many applications open
3. Processing too-large dataset
4. Insufficient RAM for task

**Fixes:**
1. Close other applications
2. Restart the offending application
3. Process data in smaller chunks
4. Add more RAM (hardware)

**Risk level:** Low (usually just kills process)
```

## Error Translation Examples

### macOS Errors
```markdown
| Error | Translation | Fix |
|-------|-------------|-----|
| "The application quit unexpectedly" | App crashed | Restart app; check for updates |
| "Not enough disk space" | Disk full | Free up space |
| "kernel_task using high CPU" | Mac overheating | Cool down; check vents |
| "Your startup disk is almost full" | <10% space left | Delete files immediately |
```

### Browser Errors
```markdown
| Error | Translation | Fix |
|-------|-------------|-----|
| "ERR_CONNECTION_REFUSED" | Server not accepting | Check if site is up |
| "ERR_NAME_NOT_RESOLVED" | DNS can't find domain | Check URL; try different DNS |
| "NET::ERR_CERT_DATE_INVALID" | SSL certificate expired | Contact site owner; proceed with caution |
| "Aw, Snap!" (Chrome) | Tab crashed | Reload; disable extensions |
```

### Application Errors
```markdown
| Error | Translation | Fix |
|-------|-------------|-----|
| "ENOENT: no such file" | File doesn't exist | Check path is correct |
| "EACCES: permission denied" | Can't access file | Check permissions |
| "ECONNRESET" | Connection dropped | Network issue; retry |
| "Segmentation fault" | Memory access violation | Bug in program; restart |
```

## Solution Risk Levels

```markdown
## Risk Assessment Guide

### Safe Actions (Do without worry)
- Restart application
- Clear cache
- Check for updates
- Reboot computer
- Run built-in diagnostics

### Proceed Carefully
- Delete files (verify first)
- Change permissions
- Modify settings
- Install/uninstall software
- Edit configuration files

### Caution Required
- Use `sudo` commands
- Delete system files
- Modify system settings
- Run scripts from internet
- Disable security features

### Get Help First
- Disk appears failing
- Kernel panics repeating
- Data corruption suspected
- System won't boot
- Security breach suspected
```

## Instructions

1. Paste the exact error message
2. Tell me what you were doing when it occurred
3. I'll explain in plain English
4. Get step-by-step fix with risk assessment
5. Follow up if the fix doesn't work

## Commands

```
"Explain this error: [error message]"
"What does [error code] mean?"
"Is this error dangerous?"
"How do I fix [error]?"
"What caused [error] and how to prevent it?"
"Should I be worried about [error]?"
```

## When to Worry

### These errors need attention:
- "Disk I/O error" - Possible disk failure
- "Kernel panic" - System instability
- "File system corrupted" - Data at risk
- "S.M.A.R.T. error" - Disk failing
- Repeated crashes - Hardware or major software issue

Get new playbooks like this one

One email a week with new Claude Code workflows. Free, like everything here.

No spam. Unsubscribe anytime.

README.md

What This Does

Translates cryptic error messages into plain English, diagnoses the likely cause, and walks you through solutions with appropriate risk assessment.

Prerequisites

  • Claude Code installed
  • An error message to understand
  • Context about what you were doing

Setup Instructions

Step 1: Download the Template

Download the CLAUDE.md template below for reference.

Step 2: Capture the Error

When you see an error:

  1. Copy the exact message
  2. Note what you were doing
  3. Screenshot if helpful

Step 3: Get an Explanation

Ask about the error:

Explain this error: [paste error message]

Example Usage

"What does this error mean?"
"Is this error dangerous?"
"How do I fix [error]?"
"What caused [error]?"
"Should I be worried about [error]?"

Error Categories Covered

  • Permission errors: Access denied, not permitted
  • Network errors: Connection refused, timed out
  • Disk errors: No space, read-only
  • Memory errors: Out of memory, killed
  • Application errors: Segfaults, crashes

Risk Assessment

Each explanation includes:

  • What the error means
  • How serious it is
  • Whether data is at risk
  • Safe vs. careful actions
  • When to seek help

$Related Playbooks

Developer Tools

Explanatory Coding Mode

Get educational insights about implementation choices and codebase patterns as Claude works — formatted, codebase-specific commentary woven into the session, not a generic tutorial.

2 minutes
Beginner
Developer Tools

7-Phase Feature Development Workflow

Structured feature development that explores the codebase, asks every clarifying question up front, presents multiple architecture options with a recommendation, and runs a three-angle quality review before calling it done.

5 minutes
Intermediate
Developer Tools

Frontend UX Pattern Library

Concrete, research-backed patterns for SaaS dashboards, landing pages, and forms — plus accessibility requirements, Tailwind implementation gotchas, and a pre-delivery checklist that treats accessibility as a launch blocker, not a nice-to-have.

5 minutes
Intermediate
Developer Tools

Git Commit & PR Automation

Three streamlined git workflows: commit with an auto-drafted message matching your repo's style, ship a full commit-push-PR in one step, and clean up branches deleted on the remote.

5 minutes
Beginner
Developer Tools

AI Crawler Access Audit: Who Can Actually Read Your Site

Maps 14 AI crawlers against your robots.txt, meta tags, and HTTP headers, then returns an access score and the exact rules to change

10 minutes
Intermediate
Developer Tools

llms.txt Generator & Auditor

Generate and validate llms.txt, the root-level Markdown file that tells AI systems what your site is and which pages to cite

10 minutes
Intermediate
Developer Tools

GEO Schema: Structured Data for AI Citation

Audit and generate schema.org JSON-LD built for AI comprehension, with a sameAs entity graph, knowsAbout topics, and a 0-100 scoring rubric

10 minutes
Intermediate
Developer Tools

GEO Technical SEO Audit: 8 Categories, 100 Points

A scored technical audit covering crawlability, indexability, security, Core Web Vitals, and the server-side rendering check that decides whether AI crawlers see your content at all

15 minutes
Advanced
Developer Tools

GEO Toolkit Updater

Pull the latest geo-seo-claude skills, agents, scripts, and schema templates from upstream, with a diff summary before anything is overwritten

5 minutes
Beginner
Developer Tools

Full-Output Enforcement: No Placeholders, No Stubs

A short rule set that bans TODO comments, skeleton code, and 'rest follows the same pattern' shortcuts so Claude always delivers complete, runnable output

2 minutes
Beginner
Developer Tools

GPT Taste Skill: Strict Anti-Slop UI Rules

A stricter, more deterministic anti-slop frontend ruleset with GSAP motion patterns, despite the GPT-oriented name it works as a standard CLAUDE.md in Claude Code

5 minutes
Intermediate
Developer Tools

GitHub Contributor

A phase-based playbook for shipping pull requests maintainers actually merge — discovery, CONTRIBUTING compliance, PR-size checks, minimal diffs, and post-submission interaction.

20 minutes
Intermediate

Browse all Developer Tools playbooks →