What It Means
The term covers a wide range. At one end, an owner with no programming background builds a booking tool in Lovable, Bolt or Replit over a weekend. At the other, an experienced developer lets an assistant in Cursor or Claude write a feature and only skims it. What they share is that nobody has read the code with the care a developer would give their own.
Why It Matters
Vibe coding has made it possible for people who could never have hired a developer to build tools that fit their business exactly. That is a real gain.
The catch is that AI output looks more finished than it is. It does what you asked for on the examples you tried, and it is confidently wrong in places that look identical to the places where it is right, the same behaviour behind AI hallucination. For a personal project that hardly matters. Once a vibe-coded app holds customer details, takes payments or runs without supervision, the gaps become the business’s problem, and our article on who is responsible for software built with AI explains why.
Example
A salon owner asks an AI tool for an online booking page that texts customers a reminder. It works the first time, so it goes live. Nobody notices that the key for the texting service is visible in the page’s code, until a large bill arrives from messages the salon never sent. Reading the code would have caught it in minutes. Our guide on getting a vibe-coded app ready for real users lists the checks an owner can run, and our AI Sign-Off service is the developer review for when those checks aren’t enough.
More terms are in the glossary.