The Vibe Coder's Bible

The Mnemosyne Research Institute

The Vibe Coder's Bible

A trust-but-verify field manual for AI-assisted development and AI-native application design.

Vibe coding is real. So is the responsibility that comes with it. This book teaches one discipline for two jobs: building software with a model, and building software around one. Let models propose aggressively — then use tests, schemas, sandboxes, permissions, CI, Git, and provenance to decide what becomes real, whether the output is a code diff or a live runtime action.

Core Doctrine

Vibe coding lowers the cost of generation. It does not lower the cost of responsibility.

AI does not make detail unnecessary. AI makes detail affordable.

AI-assisted development treats the model as a faster way to write deterministic software. AI-native engineering treats deterministic software as the control structure that makes a stochastic model trustworthy.

Trust AI to propose. Verify before commit.

The model creates possibilities. Constraints decide which possibilities belong in the system.

Mixed output must be routed.

The repo is the memory.

Tests are reflexes. Schemas are contracts. Git is the time machine.

Probability is not authority. Plausibility is not admission.

Design systems where hallucination can exist, but cannot silently become truth.

All doctrine cards →

Manuscript

42/42 chapters written

Hierarchy of AI Controls

Control Build-Time and Runtime Equivalent
Elimination Remove access to secrets, production databases, destructive commands, model-owned computation
Substitution Replace raw access with typed tools, task runners, safe APIs, bounded action vocabularies
Engineering controls Tests, schemas, type systems, CI, sandboxes — and runtime validators, permission checks, legality engines
Administrative controls PR templates, checklists, review policy, release process, incident and rejection review
PPE Prompt instructions, manual vigilance, style preferences