The short definition
Vibe coding is the practice of building software by describing what you want
to an AI agent and steering the result — instead of writing every line yourself. You provide
intent, context and judgment; the agent provides the typing.
The code still ships. The conversation changed.
Where the term comes from
Andrej Karpathy coined the term in February 2025,
describing a way of coding where you give in to the vibes, forget that the code even
exists, and talk to the model in a continuous loop of request and result. What started as
a personal observation became the name of an entire way of working — and eventually of an
industry shift.
How it actually works
A vibe coding session is a loop, not a chat:
- Describe — one concrete request, with constraints and success criteria.
- Generate — the agent writes the code (and often runs it).
- Verify — you read the diff and test the behavior.
- Checkpoint — commit, then ask for the next step.
The quality of the output tracks the quality of the loop. That's why the practice has
grown its own discipline: context files, specs, verification loops and delegation
patterns.
How to start
[01] Pick one small idea
A tool you'd actually use. Small scope is what keeps the loop fast and the vibe alive.
write the spec first ↗
[02] Choose your agent
Editor-native, terminal-native or browser-native — they share the same skills, so start anywhere.
browse the directory ↗
[03] Learn the loop
Describe, generate, read the diff, verify, commit. Small steps beat giant leaps.
read the tips ↗
[04] Build in company
Jams and meetups compress months of solo trial-and-error into a weekend.
join an event ↗
FAQ
Do I need to know how to code?
No — but you need to know how to describe what you want. Non-coders ship real apps every day by directing agents. Coding knowledge helps you review what you accept, which is why our tips emphasize reading diffs.
Is vibe coding just prompting?
Prompting is one input. The practice also includes context engineering (conventions files), iteration rhythm, verification loops and delegation — everything that turns a chat into shipped software.
Which tool should I start with?
Pick one that matches where you already work: Cursor if you live in an editor, Claude Code if you delegate from the terminal, Replit or Bolt if you want zero setup. Our resources directory breaks down the options.
Can vibe coding produce production software?
Yes, when verification is part of the loop: tests the agent can run, diffs a human reviews, and checkpoints to roll back. Teams that skip those steps ship prototypes; teams that keep them ship products.
Who coined the term?
Andrej Karpathy, in February 2025, to describe coding in a state of flow — talking to the model, seeing results instantly, and steering more than typing.