Reference · Glossary
Vibe coding
Last updated
Building software mostly by describing what you want in natural language and letting an AI agent write and run the code, staying at the level of intent ("make the button save state") rather than editing syntax yourself.
#When to use
Prototypes, personal tools, and throwaway scripts where speed matters more than deeply understanding every generated line — and where a bug just means asking the agent to fix it.
#When not to
Production systems, anything handling money/health/legal data, or code you'll need to maintain long-term without AI help — read and understand what shipped, don't just accept it because it ran.
#Example
Describing "a page that lists my tasks, lets me check them off, and saves to local storage" and iterating only through follow-up prompts, never opening the generated files directly — fine for a weekend project, risky for a business.