DON'T PANIC -- A practical guide to AI-assisted development
DON'T PANIC
In many of the more relaxed civilizations on the Outer Eastern Rim of the Galaxy, the Hitch-Hiker's Guide to Vibe Engineering has already supplanted the great Encyclopedia Galactica as the standard repository of all knowledge and wisdom, for though it has many omissions and contains much that is apocryphal, or at least wildly inaccurate, it scores over the older, more pedestrian work in two important respects.
First, it is slightly cheaper; and secondly it has the words DON'T PANIC inscribed in large friendly letters on its cover.
In February 2025, Andrej Karpathy coined the term:
"There's a new kind of coding I call 'vibe coding', where you fully give in to the vibes, embrace exponentials, and forget that the code even exists."
VIBE ENGINEERING (n.): The deliberate practice of building software through AI collaboration—describing intent, reviewing output, and iterating toward working systems. Distinguished from "vibe coding" by the emphasis on engineering: understanding what you build, owning what you ship, and knowing the difference between a prototype and production.
The Guide's entry on Vibe Engineering begins:
"Vibe Engineering is the second-best way to write software in the known universe. The best way, of course, is to have someone else do it entirely while you sip Pan Galactic Gargle Blasters. Since most developers cannot afford infinite monkeys or infinitely patient colleagues, Vibe Engineering represents a reasonable compromise."
Note: We call it "engineering" deliberately. Whether that's accurate is addressed in Chapter 0.
| Chapter | Title | Summary |
|---|---|---|
| 0 | The Great Debate | Is this real engineering? Both sides examined |
| Chapter | Title | Summary |
|---|---|---|
| 1 | DON'T PANIC | Getting started without losing your mind |
| 2 | The Towel Principle | Version control as your essential survival tool |
| 3 | 42 | Dealing with ambiguity and asking the right questions |
| 4 | The Babel Fish Problem | Communication with AI and its failure modes |
| Chapter | Title | Summary |
|---|---|---|
| 5 | Mostly Harmless | Risk assessment and when to vibe freely |
| 6 | The Total Perspective Vortex | Understanding AI's true limitations |
| 7 | The Restaurant at the End of the Sprint | Planning, iteration, and shipping |
| 8 | So Long, and Thanks for All the Code | Knowing when to stop and ship |
| Chapter | Title | Summary |
|---|---|---|
| 9 | The Disaster Area | When vibed MVPs meet production reality |
Short, occasionally accurate entries on specific topics.
| Entry | Risk Level | Description |
|---|---|---|
| Prompts | 🟢 Mostly Harmless | The anatomy of effective prompts |
| Context Windows | 🟡 Caution Advised | Managing AI's limited memory |
| Hallucinations | 🔴 DANGER | When AI makes things up |
| Code Review | 🟢 Essential | Reviewing AI-generated code |
| Accept All | 🟡 Context-Dependent | When to accept without reading |
| Testing | 🟢 Essential | Verifying AI code works |
| MVP Sanity Check | 🟠 Danger | The 4-question diagnostic for shipped MVPs |
This Guide uses a four-tier system inspired by the original Guide's planetary ratings:
- 🟢 Mostly Harmless - If it breaks, nothing bad happens
- 🟡 Caution Advised - Annoying but recoverable failures
- 🟠 Danger - Real problems occur if this fails
- 🔴 Here Be Dragons - Catastrophic consequences possible
Match your vibe level to your risk level.
Before you proceed, ask yourself:
- Can you debug it? If the AI-generated code breaks, can you fix it?
- Can you explain it? Could you walk someone through what the code does?
- Can you extend it? When requirements change, can you modify it?
- Can you own it? Are you willing to be responsible for this in production?
If you answered "no" to most of these, that's okay—for prototypes. For production, keep reading.
[ ] I know what I'm building
[ ] I know the constraints
[ ] I know what "done" looks like
"Fully give in to the vibes" ←——————→ "Read every line"
↑ ↑
Prototypes Production
- Context is currency - Specific beats terrific
- Verify before trust - The AI can't test itself
- Ship before perfect - Done is better than ideal
This Guide draws wisdom from:
- Andrej Karpathy's "Vibe Coding" Tweet - The origin of the term
- Vibe Coding: Mistakes and Tradeoffs (Manning) - Practical guidance on AI-assisted development
- Douglas Adams' The Hitchhiker's Guide to the Galaxy - The format and philosophy
- DON'T PANIC
- Start with Chapter 0 if you're skeptical, or Chapter 1 if you're ready to build
- Read the chapters in order (or don't—it's your life)
- Reference the Field Guide entries as needed
- Make mistakes
- Learn from them
- DON'T PANIC
This Guide is a living document, much like the original. Contributions are welcome from all sentient beings, and some non-sentient ones (we're looking at you, CI bots).
The Guide has, in various editions, suggested that:
- AI models understand what they're doing (they don't)
- Generated code is always correct (it isn't)
- You can skip testing (please don't)
The editors apologize for any confusion, destruction of production databases, or existential crises that may have resulted.
Share and Enjoy!
"Share and Enjoy" is the company motto of the Sirius Cybernetics Corporation, whose complaints division now covers most of the known universe. This is also good advice for Vibe Engineering—share your prompts, enjoy the process, and file bugs when things inevitably go wrong.
This Guide is dedicated to Douglas Adams, who taught us that the universe is not only queerer than we suppose, but queerer than we CAN suppose. The same is true of large language models.
— The Editors
This repository is part of a growing family of open-source toolkits for Claude Code.
- LibreUIUX-Claude-Code — UI/UX development (152 agents, 70 plugins, 76 commands, 74 skills)
- LibreArch-Claude-Code — Software architecture and system design
- LibreCopy-Claude-Code — Technical writing and documentation engineering
- LibreDevOps-Claude-Code — DevOps engineering and infrastructure automation
- LibreEmbed-Claude-Code — Embedded systems, firmware, and IoT development
- LibreFinTech-Claude-Code — Financial technology development
- LibreGEO-Claude-Code — AI-search optimization (ChatGPT, Perplexity, Gemini, Google AI Overviews)
- LibreGameDev-Claude-Code — Game development across Godot, Unity, Unreal
- LibreMLOps-Claude-Code — ML engineering and AI operations
- LibreMobileDev-Claude-Code — Mobile app development (Flutter, React Native, native iOS, native Android)
- LibreSecOps-Claude-Code — Security operations
- vibe-engineer-skills — Direct AI codegen well (hypothesis → scope → validate → reject working-but-wrong)
- markdown-discipline-skills — Strip AI-slop from markdown (no em dashes, no marketing fluff)
- shell-safety-skills —
set -euo pipefaildiscipline + 15 failure-mode examples - commit-standard-skills — Ormus Commit Standard v1.0 + commit-msg hook + commitlint
- unwoke-skills — Strip AI theater (ten sins to eliminate, symmetric engagement)
- python-conventions-skills — Modern Python 3.11+ (types, pathlib, async, ruff, mypy, uv)
- typescript-conventions-skills — TypeScript strict mode, discriminated unions, Result types
- hermetic-laws-skills — Seven Hermetic Principles applied to engineering
- riper-workflow-skills — Research / Innovate / Plan / Execute / Review systematic dev
- six-day-cycle-skills — Sustainable shipping cadence with mandatory rest
- token-optimization-skills — Claude Code token + context optimization
- osint-skills — OSINT research methodology (multi-wave investigative spiral)
- calcinate-skills — Stage 1 of the Magnum Opus (burn project bloat)
- claude-md-overhaul-skills — Audit CLAUDE.md and MEMORY.md against caps
- session-handoff-skills — Session handoff + pickup discipline
- naming-skills — Product naming methodology (mine the brand's vocabulary)
- magnum-opus-skills — Seven-stage alchemy applied to project transformation
- andrej-karpathy-skills — the canonical single-file CLAUDE.md pattern (fork of jiayuan_jy's original)
Star the family, not just one — that's how the suite stays coherent.