Reference
A reference for vibe coding
Vibe coding is the practice of building software by describing requirements in natural language and letting an AI generate and iterate the code.
The developer steers this process by defining intent and reviewing results rather than writing every line of code manually.
This reference covers the definition of vibe coding, the tool landscape, and the trade-offs regarding risk, cost, and ownership. All claims on this site are tied to sources you can check.
Contents
The six parts of this reference
01
What vibe coding is
Definitions of vibe coding and its origins in software development.
02
How it works
The mechanics of prompting, context, model interaction and code review loops.
03
The tool landscape
A survey of the current tools and platforms used for vibe coding.
04
Best practices
Working practices that help achieve reliable results when building with AI.
05
Risks and limits
The failure modes, security vulnerabilities and maintenance challenges of this approach.
06
For businesses
How companies can adopt vibe coding while managing team and project requirements.
Unfamiliar with a term? Read the glossary. Definitions of the technical vocabulary used throughout this site.
Latest writing
Recent notes
How to write a clear prompt for an AI coding tool
A clear prompt states the goal, the stack it has to fit into, the constraints it must respect, and how you will know it worked. Here is how to write one, with before and after examples and the parts that belong in a rules file rather than the prompt.
Why this blog exists
This blog features short, specific pieces answering questions about vibe coding. We post only when there is something worth saying, not on a schedule.