What is vibe coding? A beginner's guide
Vibe coding means building software by describing what you want in plain English and letting an AI write the code. You test the result, say what to change, and repeat until it works. This guide explains what it is, where the name came from, what you can realistically build, and where it goes wrong.
Where the term came from
The phrase was coined by the AI researcher Andrej Karpathy in February 2025. He described a way of working where you "fully give in to the vibes" and barely look at the code at all: you talk to the AI, accept its changes, paste in any error messages, and keep going. The name stuck because it captured something new. For the first time, people with no programming background could get working software out of a conversation. Collins Dictionary later named "vibe coding" its Word of the Year for 2025.
Since then the meaning has widened. Today most people use "vibe coding" for any approach where AI writes most of the code and a person steers it, from a weekend hobby project to a real business tool. Some purists reserve the term for the "don't read the code" style. For beginners the distinction matters less than the habit underneath it: you are the director, the AI is the builder, and you are responsible for what ships.
How vibe coding works, step by step
- Describe it. You explain who the thing is for, what it needs to do and how it should look. The clearer the brief, the better the first version.
- The AI builds a first version. A chat assistant such as ChatGPT, Claude or Grok can write a single web page you can open in a browser. A coding agent such as OpenAI Codex, Claude Code or Cursor can work across a whole project folder, create files, run commands and fix its own errors.
- You test it. Click every button. Fill in every form. Try it on your phone. Most of the skill in vibe coding is noticing what is wrong and describing it precisely.
- You ask for changes in small steps. "Make the header smaller and move the phone number into it" works far better than "make it better".
- You publish it. Static sites can go live free on hosts such as Cloudflare Pages or GitHub Pages, on your own domain.
What you can realistically build as a beginner
With patience and a clear brief, a complete beginner can build:
- A fast, good-looking website for a business, club or portfolio.
- A landing page with a contact or enquiry form.
- Calculators, quote tools and quizzes.
- Simple trackers for habits, budgets, stock or jobs.
- A booking or appointment app with a database behind it.
- Internal tools, such as a basic CRM to track customers and follow-ups.
Apps with user logins, payments and emails are also within reach, but they take more care, because mistakes there can leak data or lose money. Using established services such as Clerk for logins, Stripe for payments and Resend for email means the AI is wiring together trusted building blocks rather than inventing security from scratch.
What vibe coding is not
It's not magic, and it's not "press a button, get an app". Honest limits worth knowing before you start:
- AI makes confident mistakes. It can write code that looks right and doesn't work, or works in one browser and breaks in another. You have to test.
- Big vague requests fail. "Build me Airbnb" produces a mess. Small, specific steps produce working software.
- Security is still your job. AI tools sometimes put secret keys where the public can see them, or skip checks on who can see which data. You need a short checklist and the habit of asking the AI to review its own work.
- Projects get harder as they grow. Past a certain size, the AI loses track of how everything fits together unless you keep notes, use version control (GitHub) and work in small, saved steps.
- Usage limits are real. Paid plans have weekly or daily caps, and a long session with a coding agent can use them up quickly.
Do you need to learn to code at all?
You don't need to learn a programming language before you start. You do need to learn a handful of ideas: what a file and a folder are in a project, the difference between the front end (what people see) and the back end (where data lives), what an API key is and why it must stay secret, and how to read an error message well enough to paste it back to the AI. These take days, not years, and you pick them up naturally while building.
Many people find they start reading the code after a few projects. Not because they have to, but because they get curious. That's a bonus, not an entry requirement.
Which tools do vibe coders use?
There are two broad kinds:
- Chat assistants (ChatGPT, Claude, Grok): great for planning, writing a brief, explaining errors and producing single-page sites you can copy and paste.
- Coding agents (OpenAI Codex, Claude Code, Cursor and similar): they work inside a real project, edit many files at once and can run and test the code. This is where proper apps get built.
Most of them have a free tier you can learn on, and a paid plan of roughly £8 to £30 a month once you're building seriously. We compare them in Grok vs ChatGPT vs Claude for building apps, and break down the full budget in how much it costs to build an app with AI in the UK.
A simple first project
If you want to try vibe coding tonight, start with a one-page website for something you know well: your hobby, your side business or a local club. Write five sentences describing it, ask ChatGPT, Claude or Grok to "build a single HTML file with the CSS inside it" from that description, save the result as index.html and open it in your browser. Then improve it one request at a time. Our step-by-step walkthrough, how to build a website with ChatGPT or Codex with no coding, takes you from that first file to a live site on your own domain.
The single biggest lever on quality is how you ask. Read how to write prompts for building apps before you go much further.
The short version
Vibe coding lets ordinary people build real websites and apps by describing them to an AI. It works best in small steps, with clear briefs and honest testing. It doesn't replace care or judgement, but it does remove the old barrier of having to learn to code first. If you can explain what you want and notice when something is wrong, you can build things that used to need a developer.