Vibe Code in Easy Mode

A Claude Code skill that activates plain-language mode for your entire coding session.

Every command gets explained before it runs. Every error gets translated into plain English. Every piece of code gets walked through section by section. Built for non-technical founders, first-time coders, and vibe coders who are building real things with AI assistance.

---

What happens when you turn it on

When you type /vibe-code-easy-mode, Claude immediately:

• Detects what kind of project you're in (Node.js, Python, Docker, etc.) and tells you what that means
• Shows you a step map before any multi-step task so you always know where you are
• Explains every terminal command before running it — what you're doing, where it happens, and why
• Translates every error message into plain English with a ranked list of causes and a specific fix to try first
• Walks through every piece of code section by section in plain sentences
• Adapts its vocabulary and style to match how you write — without sacrificing accuracy

---

Install

Copy this folder to your personal Claude Code skills directory.

Mac / Linux:

git clone https://github.com/YOUR_USERNAME/vibe-code-easy-mode
cp -r vibe-code-easy-mode ~/.claude/skills/

Windows (PowerShell):

git clone https://github.com/YOUR_USERNAME/vibe-code-easy-mode
Copy-Item -Recurse vibe-code-easy-mode "$env:USERPROFILE\.claude\skills\"

Then open any project in Claude Code and type:

/vibe-code-easy-mode

That's it. Easy mode is on for the rest of the session.

---

What's included

vibe-code-easy-mode/
├── SKILL.md                      Main skill — loads when you invoke it
└── references/
    ├── git-dictionary.md         Git commands in plain English (8 commands, full flow)
    ├── install-commands.md       npm, pip, bun, brew — what they do and when to use them
    ├── error-playbook.md         19 real errors translated to plain English with causes + fixes
    ├── supabase-guide.md         RLS, tables, auth, edge functions — no jargon
    └── environments-map.md       Local machine, GitHub, Vercel, VPS, Supabase — what each is

Reference files load on demand when they're relevant — not all at once. Token cost stays minimal.

---

The communication rules it enforces

1. Plain meaning before the technical name — what it does in the real world, then what it's called
2. Physical metaphors — Docker = sealed lunchbox, git push = sending to a warehouse, CORS = a permission slip
3. Knowledgeable friend tone — short sentences, contractions, no passive voice, validate before explaining
4. Mirror your style, not your imprecision — adapts vocabulary to match you; corrects wrong terms gently without repeating them

---

Error playbook coverage

Built from real build sessions, not hypothetical errors. Covers:

• CORS policy blocks (the www vs non-www trap, test vs live webhook URLs)
• Python: NameError, ImportError, SyntaxError, ValueError, ModuleNotFoundError
• Docker: container not found, pip install outside container
• Git: permission denied (SSH), remote already exists, failed to push
• Node/npm: command not found, module not found, ENOENT
• Supabase: schema permission denied, RLS blocking reads/writes
• Environment variables: undefined on Vercel, missing on VPS, case sensitivity

---

Contributing

Hit an error that isn't in the playbook? Open a PR with it in this format:

### [Error message or short name]
🔴 What it means in plain English
🧠 Most likely reasons (numbered, in order of frequency)
🔧 What to try first (specific command or step)

Add it to references/error-playbook.md under the right category.

---

Built with Claude Code · Follows the Agent Skills open standard