Weekend tutorial

How to vibe code: build your first real app in one weekend

Updated November 17, 20269 min read

To learn how to vibe code, the fastest way is to build one small, real app from start to finish. In this tutorial you spend Saturday morning picking tools and writing a plan, Saturday afternoon getting a first version running, and Sunday fixing, testing and putting it online. You don't need to know any programming, and every prompt you need is written out for you to copy.

The project: a reading tracker for a book club

Vibe coding for beginners works best with a project that is small, useful to you, and easy to test. For this weekend we will build a reading tracker for a book club. Members can see the list of suggested books, add a new one, vote for the next book, and see when the next meeting is. You can swap in your own idea, as long as it is about this size.

Here is what you need before Saturday:

  • A computer. Windows or Mac both work. A browser is enough for some tools.
  • An AI account. Most tools need a paid plan from a company like Anthropic (Claude), OpenAI (ChatGPT) or Google, or a plan from the app builder itself. Prices change often, so check the provider's own pricing page.
  • About 10 hours spread across two days, with breaks.
  • A notes app to keep your plan and the prompts that worked.

Note

Vibe coding for non programmers is mostly a writing skill. If you can explain a problem clearly to a friend, you can explain it to an AI.

Saturday morning: choose your tools and write the plan

How to start vibe coding comes down to two choices this morning: a tool and a plan. There are two main kinds of tool. Pick one. You can switch later.

A browser app builder (Lovable, Bolt, Replit)

You want to see something in minutes, install nothing, and have hosting built in. Good for a first weekend.

An AI coding agent (Claude Code, Codex, Gemini CLI)

You want the project files on your own computer and full control. A coding agent is an AI that can create and change files on your computer by itself. It runs in a terminal (a text window where you type commands), which feels strange at first.

A coding agent inside VibeCodingDeck

You like the control of a coding agent but want plain English, buttons for save points and the app preview right next to the AI. VibeCodingDeck runs on Windows 10/11 and Apple-silicon Macs and uses the AI plan you already pay for.

If you choose Claude Code, follow the official setup page or our guide on how to use Claude Code. On a Windows PC, see Claude Code on Windows first.

Write the one-page plan

Spend 20 minutes on this. It saves hours later. Copy this into your notes app and fill it in:

WHAT: A reading tracker for my book club.
WHO: About 10 club members, on phones mostly.
MAIN THING THEY DO: Vote for the next book.
SCREENS: Book list, Add a book, Vote, Next meeting.
IT MUST REMEMBER: Books, who suggested them, votes, meeting date.
NOT IN VERSION ONE: Logins, emails, reviews, a phone app.

Tip

The "not in version one" line matters most. Every feature you cut today is a feature that can't break on Sunday.

Saturday afternoon: get version one running

Now you talk to the AI. This is vibe coding step by step: follow the steps in order and don't skip ahead, even if things go well.

  1. 1

    Ask for a plan, not code

    Paste your plan with the prompt below. The AI should reply with questions and a list of build steps.

  2. 2

    Answer its questions

    Keep answers short. If you don't know, say "pick the simplest option and tell me what you picked".

  3. 3

    Build step 1 only

    Ask it to build just the first step, usually the book list page, and then stop.

  4. 4

    Open it and look

    Ask how to open the app. In a coding agent you'll usually get a local address such as http://localhost:3000, which only works on your own computer. In a browser builder the preview appears on screen.

  5. 5

    Save a checkpoint

    As soon as something works, save it. This is your undo button for the rest of the weekend.

  6. 6

    Repeat for each screen

    Add a book, then voting, then the meeting date. One screen per request, test, save.

Your first prompt:

I'm not a developer. Here is the plan for a small web app:
[paste your plan]

Don't write any code yet. Please:
1. Suggest the simplest way to build this.
2. Split the work into small steps, one screen per step.
3. Ask me any questions you need answered.
Use plain English and explain any technical word you use.

When a step works, save it with a prompt like this. Coding agents use git (a tool that keeps a history of every saved version of your project). You don't need to learn git commands. Just ask:

That works. Please save a checkpoint with git
with a short note: "book list page working".

Tip

Claude Code has a plan mode that stops the AI from changing files while you agree on a plan. Our Claude Code plan mode guide shows how to use it. For more ready-made wording, see our vibe coding prompts.

Saturday evening: when the AI gets stuck

At some point today something will break. A page goes blank, or the vote button does nothing. This is normal and it is where most beginners give up, so here is what to do.

The AI can't see your screen. Tell it exactly what happened, in this shape:

Something is wrong.
What I did: I clicked Vote next to "The Hobbit".
What I expected: the vote count to go up by one.
What happened: nothing changed and the page froze.
Error message: [paste the whole thing if you see one]

Find the cause first and explain it simply. Then fix it.

If the fix doesn't work after two or three tries, stop asking for fixes. The AI is now guessing and each guess adds mess. Go back to your last checkpoint and ask for a different approach:

Let's stop. Go back to the last checkpoint.
Then tell me what you think went wrong and suggest a
different, simpler way to build the voting feature.

Watch out

Long chats make the AI forget earlier decisions. If you've been in one chat for hours, start a fresh one and paste a short summary of the project and where you are.

Sunday morning: test it like a picky club member

Today you try to break your own app. Real people will do strange things with it, so you should do them first. Work through this list and note anything odd:

  • Open it on your phone, not only the computer.
  • Add a book with a very long title, with an emoji, and with no title at all.
  • Vote twice for the same book. Should that be allowed?
  • Refresh the page. Are the votes still there?
  • Open it in a second browser. Do both show the same list?
  • Ask a friend to use it without your help and watch where they get confused.

Send each problem to the AI as its own message, using the bug report shape from yesterday. Test, then save a checkpoint after each fix. One fix per message keeps you in control.

You can also ask the AI to check its own work:

Review everything we built this weekend. Look for bugs,
anything that could lose the club's data, and anything
confusing for a first-time user. List problems worst first.
Don't change anything yet.

Sunday afternoon: publish it for the club

Publishing means putting the app on the internet so others can open it with a link. How you do it depends on your tool.

  1. 1

    Browser builders

    Lovable, Bolt and Replit each have a publish or deploy button. Press it and you get a public link.

  2. 2

    Coding agents

    A hosting service is a company that keeps your app online for others. Ask the AI: "Help me put this online. Suggest a hosting service with a simple setup and walk me through it one step at a time."

  3. 3

    Do a safety pass first

    Before you share the link, make sure no secret keys are visible and that strangers can't delete the club's data.

  4. 4

    Share and watch

    Send the link to two or three members first. Fix what they find, then send it to everyone.

Watch out

Our book club app has no logins, so anyone with the link can add or vote. That's fine for a club. It is not fine for anything with personal details or payments. Read the vibe coding security guide before you build that kind of app.

What to learn after your first vibe coded app

You now know how to start vibe coding. To get better, learn a little about the parts the AI keeps mentioning. You don't need to master them. Ask the AI to explain each one using your own app as the example.

  • Checkpoints and git: how to look at old versions and go back to one.
  • Error messages: how to find the important line in a long error.
  • Databases: where your app keeps its data and who is allowed to read it.
  • Secret keys: what they are and why they must stay out of your code.
  • Notes files: a file the AI reads at the start of every chat (CLAUDE.md in Claude Code, AGENTS.md in Codex). Put your project summary and rules there.

Then build a second app that is a little bigger. Many people add logins on their second project, which is a good moment to read our list of the best vibe coding tools and see if a different tool suits you better.

Is a vibe coding course worth paying for?

You can learn most of this for free by building, but a course helps if you like a teacher setting the pace. A few honest options:

  • Vibe Coding 101 with Replit by DeepLearning.AI is a beginner course of about an hour and a half, taught by two people from Replit. You build a website checker and a voting app with Replit's AI agent. When we checked in November 2026 it was free to watch for a limited time, and the graded quiz needed a paid PRO membership.
  • Claude Code in Action from Anthropic's own academy is a free course about Claude Code. It is aimed at people who already write some code, so take it after your first weekend, not before.
  • The official docs for whichever tool you picked are free and kept up to date, which many paid courses are not.

If you do pay for a vibe coding course, check that it covers testing, checkpoints and security, not only fast demos. Tools change every few months, so a course recorded long ago may show buttons that no longer exist.

Beginner questions about vibe coding

Can I learn vibe coding if I have never coded?

+

Yes. The skills that matter most are describing what you want clearly, testing carefully and building in small steps. You will pick up technical words as you go by asking the AI to explain them.

How long does it take to vibe code an app?

+

A small tool like the book club tracker fits in a weekend. Apps with logins, payments and lots of data usually take weeks, and most of that time goes into testing and fixing.

Is vibe coding free?

+

Some tools have free tiers with tight limits. Regular use usually needs a paid plan. Check each provider's pricing page, since prices change often.

What should my first vibe coding project be?

+

Something small that you or people you know will actually use, with one main feature. A finished small app teaches you more than a half-built big one.

Sources

Run up to 12 AI coding agents in one window.

Claude Code, Codex, Gemini, Grok and more, side by side. Windows and Mac. From $29 a month.

Get started

Keep reading