DEV Community

Bobi
Bobi

Posted on

Vibe coding for beginners: your first session, step by step

Vibe coding for beginners: your first session, step by step

"Vibe coding" means building software by talking to an AI in plain language and letting it write the code. You describe, it builds, you check. You don't need to know a programming language.

That sounds like magic, and for the first hour it feels like it. Then most beginners hit the same wall: the app half works, every fix breaks something else, and they quit. This post is about getting past that wall on your first try.

What you actually do when you vibe code

Your job changes from "writer of code" to "person in charge". You:

  • decide what gets built (the AI won't say no to a bad idea)
  • describe each piece clearly
  • test what it made, like a user would
  • report problems back in plain words

The AI types. You steer. Most problems come from steering, not from the AI.

Before you open any tool: write one paragraph

Answer this in three or four sentences:

Who is this for, what one thing does it help them do, and what do they see on the screen when it worked?

Example: "A page for my running club. Members type their name and today's distance. Everyone sees a list of this week's runs, longest first."

If you can't write that paragraph, you're not ready to prompt yet. That's normal. Shrink the idea until you can.

Pick a beginner-friendly tool

For a first session, use a browser-based builder (Lovable, Bolt or Replit). Nothing to install, and you see the app update as you talk. Coding assistants like Claude Code or Cursor are great later, once you want to own the files.

Whatever you pick, stay with it for the whole project. Switching tools when things get hard just restarts the hard part.

Your first prompt

Paste your paragraph, then add this:

Build only the first screen for now.
Keep it simple: one page, clean layout, no login.
Before you start, ask me any questions about anything that's unclear.
Enter fullscreen mode Exit fullscreen mode

The "ask me questions" line is the most useful sentence in vibe coding. The questions show you what you forgot to decide.

The loop: one small change at a time

After the first screen exists, every request follows the same loop:

  1. Ask for one change ("add a button that saves the run").
  2. Click through the app and try it.
  3. If it works, move on. If not, report it.

Beginners ask for five things in one message. The AI does four, breaks one, and now you don't know which change caused it. One change per message feels slow, but it's faster overall.

When something breaks

Something will break. This is the moment that decides whether you finish.

Copy the exact error (or describe exactly what you saw), then send:

This happened: [paste the error or describe it].
Explain in plain words what went wrong, then fix only that.
Don't change anything else.
Enter fullscreen mode Exit fullscreen mode

"Don't change anything else" stops the AI from "improving" parts that were working.

If the same bug comes back three times, stop. Ask it to undo the last change, or describe that one piece again from scratch in fewer words.

Five habits that separate finished apps from abandoned ones

  • Test after every change. Not after ten.
  • Say what you see, not what you think the cause is. "The list is empty after I save" beats "the database is broken".
  • Keep a "later" list. Logins, payments, dark mode, notifications: later. They roughly triple the work.
  • Publish early. Use the tool's publish or deploy button in your first session. Hosting problems are easier to fix while the app is tiny.
  • Stop while it works. End each session on a working version, so the next one starts from solid ground.

What "done" looks like for a first app

Not perfect. Done means:

  • it has a link that opens on your phone
  • it does its one job
  • one real person used it without you explaining

That's a real app. Everything after that is improvement.

The short version

  1. One paragraph: who, what, what they see.
  2. One beginner tool, kept for the whole project.
  3. First prompt ends with "ask me questions first".
  4. One change per message, test every time.
  5. Errors: plain words, fix only that.
  6. Publish in the first session.

If you want the whole path laid out for one weekend, with copy-paste prompts and what to do when you get stuck, I wrote a 42-page guide: Live by Sunday.

Top comments (0)