What Is Vibe Coding? Meaning, Examples and How to Start

Vibe coding is building software by describing what you want to an AI in everyday language and letting it write the code, judging the result by whether it works rather than by reading the code. AI researcher Andrej Karpathy coined the term in February 2025. It now covers everything from a shop owner making a landing page in a browser tool to a developer handing a whole feature to an AI agent.

Where the term came from

Karpathy was an early engineer at OpenAI and later led AI work at Tesla. In his post, he described accepting the AI's changes without reading them, to the point where you "forget that the code even exists". He framed it as fine for throwaway weekend projects, not as a way to build serious software.

The phrase spread fast. Within months it meant almost any AI-built software, and Collins named it Word of the Year in November 2025.

How vibe coding works

The engine is a large language model (LLM), an AI trained on huge amounts of text and code that predicts what should come next. Modern tools wrap it in an agent: an AI that can take actions such as creating files and running commands, check the result, and keep going until the task is done.

Our guide to what an AI agent is explains how that differs from a chatbot. In practice, a vibe coding session follows the same loop every time.

A first request might be: "A page where customers enter the number of rooms and see a price for a deep clean." A typical follow-up: "Make the total update as they type, and add a button to request a booking."

The skills it actually takes

You don't need to learn a programming language, but you do need four habits that most people already use when they brief a designer or a contractor.

• Describing outcomes. Say what the visitor should be able to do, not how the code should work.
• Giving feedback like a client. "The button is hard to find on a phone" beats "make it better".
• Testing on purpose. Try the wrong inputs, the empty form and the small screen, not just the happy path.
• Knowing when to stop. If the AI fails at the same fix twice, ask it to explain the problem before it tries again.

Vibe coding vs traditional coding vs no-code

No-code builders such as Wix or Squarespace are still a good choice for a standard site you'll rarely change. Vibe coding earns its place when you need something the blocks can't do, or you want code you own.

What vibe coding is good for

The common thread: if it breaks, the damage is small and you'll notice quickly.

Where it goes wrong

Even professional developers are wary of AI-written code. In Stack Overflow's 2025 Developer Survey, most respondents use AI tools, yet more of them distrust the accuracy of AI output than trust it.

• Nearly-right code. It runs, looks finished and fails on the case nobody tested.
• Invisible security gaps. Code can work perfectly while leaving customer data open to strangers.
• Hidden fragility. In bigger projects, each change can break something unrelated.
• Upkeep. Software needs updates, and someone has to notice when they're due.
• Cost loops. Credit-based tools charge for every attempt, including the failed fixes.

The rule of thumb: the more a mistake would cost in money, data or reputation, the more review you need. Real incidents and a full safety checklist are in is vibe coding bad.

The main types of vibe coding tools

If you want to understand the agent option first, read what Claude Code is. Prices and picks by user type are in the best vibe coding tools.

How to vibe code responsibly as a non-developer

1. Start where mistakes are cheap. Pick a project where a bug is an annoyance, not a disaster.
2. Ask for a plan before code. Approve the approach first, then let the AI build.
3. Keep a way back. Save a version with Git or your tool's history after every working step.
4. Keep secrets out of prompts. Never paste passwords, API keys or customer records into a chat.
5. Test like a customer. Use a real phone and try wrong inputs, not just the happy path.
6. Get a review when money or data is involved. A few hours of a developer's time costs less than a leak.

A first project for this week

A small internal tool is the best first project, because you already know exactly what "right" looks like. This prompt builds a price calculator and works in Claude Code or any browser builder:

Build a simple price calculator for my [TYPE OF BUSINESS] as a single
web page. Inputs: [WHAT THE CUSTOMER CHOOSES].
My prices: [YOUR PRICE LIST].
Show the total as the inputs change. Ask me about anything unclear
before you build, and never invent a price.

Test it against three recent real jobs. Your first few follow-ups will usually look something like this:

When the totals match what you actually charged, you've vibe coded something useful.

For a full website session, follow how to vibe code a website. For more ideas sorted by job, see Claude Code for non-developers.

What to do next

Pick one small, low-stakes tool you'd use this week and build it with the prompt above. Keep notes on where the AI misunderstood you, because that is the skill you're really learning.

When you're ready for a customer-facing project, the Builders course teaches the full process of planning, building and launching websites with AI.