Keep the good vibes going

Build the habits that keep a vibe-coded project healthy: small commits, one task per session, a pre-deploy check, controlled costs, and knowing when to call in a professional.

You've built something real. Projects like this rarely fail in one dramatic moment; they decay. Rules get forgotten, packages go out of date, a quick fix skips a check, and six months later nobody knows how anything works. A few habits keep that from happening, and none of them takes long.

Habits for every change

One task per session. Start fresh, state the task, finish it, commit.
Plan, then build for anything bigger than a small fix.
Check in the browser, at phone size, before you accept a change.
Commit each good change with a message that says what changed and why.
Ask “explain this” whenever a change surprises you. A few minutes of asking each week adds up to real understanding.

Each habit shrinks the time between a mistake and its discovery. A wrong guess caught in the plan costs a sentence; caught in the diff, a minute; caught by a customer next month, an afternoon of detective work and some of their trust. Agents make vibe coding fast because they type quickly, but it only stays fast if you catch problems early.

Before every deploy

Pre-deploy check0 / 5

Sort itExercise 1 of 3

How often should you do each of these?

Card 1 of 7

Open the live site on your phone

Keep costs under control

Free and cheap plans come with limits: daily credits on most builders, a weekly pool shared by Cursor and Grok on The X Subscription, usage limits on Claude and ChatGPT plans. Long, messy sessions burn through them; short, focused ones don't. When you hit a limit, pause and come back after it resets before you think about upgrading. And if you ever connect a paid API, for example to add an AI feature, set a spending limit with the provider first and keep the key on a server.

Quick checkExercise 2 of 3

Your site has run for three months without changes. What's the most useful thing to do this month?

Learn a little code along the way

You don't have to become a programmer, but recognizing a few patterns makes you a far better reviewer. Once a week, pick one file and ask the agent to walk you through it: “Explain app.js section by section, as if I've never coded.” Then turn it around: “Quiz me with three questions about how app.js works.” After a month of this, you'll spot a suspicious change in a diff without being told.

When your tools change

They will. Windsurf has been renamed Devin Desktop, and in 2026 Firebase Studio closed to new users and Google moved individual users from Gemini CLI to Antigravity CLI. Your project survives all of that because it lives in plain files and git, with its rules in AGENTS.md. Switching tools means installing the new one, opening the same folder, and asking it to read the instruction file.

Know when to call a professional

Careful vibe coding covers a lot: personal projects, small-business sites, internal tools. Some things deserve an experienced developer's review before real people rely on them: handling card payments yourself instead of through a payment provider's hosted checkout, storing health, financial or children's data, anything with legal obligations, and anything where a bug could hurt someone. That's not failure. It's the same judgment that has you hire an electrician for the wiring even after you've painted the walls yourself.

You make the callExercise 3 of 3

A friend's big idea

A friend who runs a small physiotherapy clinic asks you to vibe code a booking app where patients describe their injuries and pay a deposit.

What do you say?

Check your understanding

Q1. You hit your plan's daily limit halfway through a change. What's usually the best move?

Q2. Which project most needs an experienced developer's review before real people use it?

· Work through the 3 remaining exercises above (stuck? each one can show you the answer).

· Score 100% on the quiz.

Vocabulary in this lesson

ToolA named capability the harness lets the model invoke, such as reading a file, running a shell command or fetching a page.Vibe codingBuilding software by describing what you want to an agent and judging the result rather than reading every line of code.AgentA model wired to tools and a loop: it reads, acts, checks the result, and goes again until the task is done or you stop it.SessionOne continuous run with an agent, from an empty context to the moment you clear it, close it, or hand its work off.Usage limitThe cap on how much agent work your plan or API key allows in a window. Hitting it pauses you; it isn't the context window.

Plain-English definitions from the AI Coding Dictionary.