Developer education / Open source
Vibe Coders Tech Manual
What to know before AI-generated code meets production.
Visit github.com (opens in a new tab)
[ 01 ]The project
AI coding tools make it easy to get a feature working on your own machine. The Vibe Coders Tech Manual covers what changes when that code meets real traffic, concurrent users, failures and attackers: race conditions, transactions, idempotency, caching, queues, migrations, distributed consistency and observability, each explained in plain language.
A dedicated security part covers the gaps that most often turn a vibe-coded app into a breach: broken access control, row-level security, secrets in client bundles, injection, sessions, CORS, supply-chain risk, security headers and prompt injection. It closes with a pre-ship checklist and review prompts to paste into a coding assistant.
[ 02 ]What it does
- 01
50 engineering concepts
Grouped into seven areas, from database reliability to observability, each with why it matters in production.
- 02
15 security essentials
Access control, row-level security, secrets, injection, sessions, CORS, supply chain and prompt injection.
- 03
A pre-ship checklist
Reliability and security items to copy into an issue tracker before launch.
- 04
Prompts for your AI tool
Ten review prompts that make a coding assistant check its own work for these failure modes.
One company at a time