how to vibe code
vibe coding
guide

How to Vibe Code: A Step-by-Step Guide for Beginners

By Ethan Halfhide · Updated

How to vibe code, step by step: choose a tool, plan before you prompt, build in small pieces, test every change, keep checkpoints and lock down security.

To vibe code, you describe the software you want in plain language, let an AI tool write and run the code, then test the result and steer it with follow-up prompts until it works. The skill is not typing code. It is writing clear requests, checking every change, and keeping a way to undo mistakes.

This guide walks through that workflow step by step: picking a tool, planning before you prompt, prompting in small pieces, testing, saving checkpoints, fixing bugs, and the security checks that matter before anyone else uses what you built.

What vibe coding means (and what it doesn't)

The term comes from AI researcher Andrej Karpathy, who described it in February 2025 as a style of coding "where you fully give in to the vibes, embrace exponentials, and forget that the code even exists."

Developer Simon Willison drew a useful line a few weeks later: vibe coding is building software with an AI model without reviewing the code it writes. Using AI to help you write code you then read and understand is AI-assisted programming, which is not the same thing. His advice was that vibe coding suits low-stakes projects and prototypes, and his own rule for anything serious is that he won't commit code he couldn't explain to someone else.

That distinction shapes everything below. You can vibe code a weekend tool freely. The closer a project gets to real users, real data or real money, the more of the review steps you should add back. For the background on the idea itself, see vibe coding explained.

Step 1: Pick the right kind of tool

Vibe coding tools fall into two groups, and the right one depends on whether you want to touch code at all.

Tool typeExamplesYou getBest for
Browser app buildersLovable, Bolt, Replit, v0A running app, hosting and often a database, all in the browserNon-developers, prototypes, quick web apps
AI code editors and agentsCursor, Claude Code, VS Code with GitHub CopilotAI that edits files in a real project on your machinePeople comfortable with a code editor and Git

Browser app builders are the easiest start. You type what you want, watch the app appear in a preview, and keep refining. Some publish a free tier and some do not. As of November 2026, Bolt's pricing page lists a free plan with a 300K token daily limit and 1M tokens per month, and a Pro plan at $25 per month. Lovable's Pro plan is $25 per month with 100 monthly credits. Replit's cheapest paid plan, Core, is $20 per month, or $18 per month billed annually. Our free vibe coding tools compared page covers what each free tier allows.

AI code editors and agents work on a normal codebase. They give you more control and make it easier to move the project somewhere else later, but you need to be able to run the project and read errors. Vibe coding with Claude Code shows what the terminal route looks like.

If you are unsure, start with a browser builder for your first project. Our ranking of the best vibe coding tools for beginners narrows it down, and the full list of vibe coding tools compared covers every option we track.

Step 2: Plan before you prompt

The most common beginner mistake is opening the tool and typing "build me an app like Airbnb." The AI will produce something, but you will spend the next hour undoing guesses it made.

Write a short plan first, even five lines in a notes app:

  • What it does: one sentence. "A page where my running club can sign up for weekend runs."
  • Who uses it: you only, a few friends, or the public. This decides how much security work you need later.
  • The screens: list them. "Sign-up form, list of upcoming runs, admin page to add runs."
  • The data: what gets saved. "Name, email, which run they picked."
  • What it is not: features you are skipping for now, like payments or logins.

Paste that plan into your first prompt. A clear spec gives the AI fewer gaps to fill with its own assumptions.

Step 3: Prompt in small steps

Build one piece at a time, and check each piece before you ask for the next.

A good first prompt sets up the skeleton:

Build a simple web app for a running club. It needs three pages: a sign-up form (name, email, run choice), a list of upcoming runs, and an admin page for adding runs. Keep the design clean and mobile friendly. Don't add user accounts yet.

Then add features one at a time:

On the upcoming runs page, sort runs by date and hide runs that have already happened.

Prompts that work well tend to:

  • Name the exact screen or part you want changed.
  • Describe the result, not the code. "When the form is submitted, show a thank-you message" beats "add an onSubmit handler."
  • Say what should not change. "Don't change the layout of the admin page."
  • Paste the exact error when something breaks, instead of describing it.

Avoid asking for five changes in one prompt. When something goes wrong, you will not know which change caused it.

Step 4: Test every change yourself

After each prompt, use the app the way a real person would. Click every button. Submit the form with an empty field. Try it on your phone. Reload the page and check the data is still there.

The AI often reports that a change is done. Treat that as a claim to check, not a fact. If you are vibe coding in the strict sense and not reading the code, your testing is the only review the code gets.

Step 5: Save checkpoints so you can undo

Sooner or later a prompt will break something that worked. The fix is being able to go back.

Most tools have a built-in way to do this. Replit's Agent creates checkpoints automatically at key milestones, and you can roll back to any of them with one click; restoring the development database is a separate option you have to select. Cursor's Agent creates local checkpoints before significant changes, but Cursor's docs say these are only for undoing Agent edits and that Git should be used for permanent version control.

Our advice: once a project matters to you, connect it to Git or GitHub and save a version every time something works. Checkpoints are a safety net. Version control is the real history.

Step 6: Fix bugs without going in circles

When something breaks, a few habits save a lot of time:

  1. Copy the full error from the screen or browser console and paste it into your prompt.
  2. Describe what you expected and what happened. "I clicked Save and expected the run to appear in the list. Nothing happened and the console shows this error."
  3. If two attempts fail, roll back to the last working checkpoint and ask for the change again with a clearer prompt. Repeated fix attempts on top of broken code tend to pile up new problems.
  4. Ask the AI to explain what it changed and why. Even if you don't read code, the explanation often shows where it misunderstood you.

Step 7: Check security before you share it

This is where vibe-coded apps most often go wrong, and it matters as soon as other people can use your app or you store anything about them.

  • Keep secrets out of the browser. Lovable's security docs put it plainly: API keys and other secrets cannot be stored safely in client-side code. Use your tool's secrets or environment variable feature, never paste keys into the code.
  • Lock down your database. Many app builders use Supabase for data. Supabase's docs say to enable Row Level Security on every table in an exposed schema, because a table without it is readable and writable by any role with a grant on it. Lovable's docs note that misconfigured RLS rules are a common cause of data leaks.
  • Run the built-in scan if there is one. Lovable runs a quick security scan automatically every time you publish and offers a deeper scan of your app's code.
  • Don't vibe code what you can't afford to get wrong. Payments, health data and anything regulated deserve a developer's review.

Our guide to the risks of vibe coding goes deeper on where these projects fail.

Step 8: Publish and keep iterating

Browser builders usually publish with one click to a hosted address. Editor-based projects need a host; your AI tool can walk you through deploying to one.

After launch, keep the same loop: one change, test it, save a version. When you are ready for a bigger project, our walkthrough on how to ship your first vibe-coded app covers taking an idea all the way to a live product.

Frequently asked questions

Can you vibe code for free?

Often, yes, within limits. As of November 2026, Bolt lists a free plan with a 300K token daily limit and 1M tokens per month. Free tiers on other tools have their own limits, and larger projects usually need a paid plan.

Do I need to know how to code to vibe code?

No, browser app builders are made for people who don't write code. Knowing some basics still helps, mainly reading error messages and understanding what a database is, and it becomes more important as a project grows.

What is the best tool to start vibe coding?

For a first project, a browser app builder such as Lovable, Bolt or Replit is the easiest start because hosting and setup are handled for you. If you already use a code editor, Cursor or Claude Code let you vibe code inside a normal project.

Is vibe coding safe?

It is safe for personal and low-stakes projects. For apps that store other people's data, the main risks are exposed API keys and databases without access rules, so check both before you share the app.

How is vibe coding different from coding with AI?

In vibe coding you accept the AI's code without reviewing it and judge the result only by whether it works. In AI-assisted programming you read and understand the code the AI writes. Simon Willison's March 2025 post makes this distinction.

How long does it take to learn vibe coding?

There is no fixed answer. You can usually get a simple page working in your first session, and the skills that take longer to learn are planning, writing clear prompts and testing properly.

What we don't know

  • Exact free-tier limits change often, and some pricing pages (Lovable's, for example) did not state a free credit amount when we checked. Check each tool's pricing page before you rely on a limit.
  • How well any tool handles your specific project. Results vary with the size of the app and how clearly it is described.

How this guide was put together

We based the workflow on the tools' own documentation, Supabase's security docs, and the published definitions from Andrej Karpathy and Simon Willison, all read on November 22, 2026. We did not test these tools for this article. Prices are as listed on each official pricing page in November 2026.

Sources

About the author
Ethan Halfhide

Ethan Halfhide is an AI technologist and educator who has taught more than a thousand founders to build apps with AI coding tools. He tracks Lovable, Cursor, Bolt, Replit and the apps people ship with them.