Vibe Coder · Unit 8: Building With Claude Code · Lesson 3 of 15

Plan first

Ask for a plan before any code. Reading and correcting a plan is the cheapest way to avoid a wrong build.

Read the short notes and pictures.Do everything inside a blue frame.

Agree before it builds

Left alone, an agent starts building straight away. For anything bigger than a small fix, ask for a plan first. Plan mode makes Claude Code research and propose without touching your files, so you can spot a wrong turn before it costs anything.

A 3D scene of coloured blocks and cards. : Plan mode, Build.
Plan mode reads and thinks but changes nothing.

Reading a plan

  1. Does it match the brief?

    Nothing extra, nothing missing.

  2. Is it in a sensible order?

    Data before the screens that need it.

  3. Is anything risky?

    Deleting files, changing sign-in, touching payments.

  4. Ask why

    If a step is unclear, ask it to explain in plain words.

A 3D scene of coloured blocks and cards. A plan says: which files it will create, what each one does, the order of work.
A plan lists the files, what each does and the order.

When to plan

Always

A new feature, anything with data or sign-in.

Skip it

A typo, a colour, a single line of text.

ActivityBuild stepThe first working version

Plan your next feature

In plan mode, ask Claude Code to plan the next must-have from your ranked list. Read the plan, change at least one thing, and only then let it build.

Done when

Make this a habit for every feature that follows.

Keep these

  • Ask for a plan before code.
  • Plan mode changes nothing.
  • Correcting a plan is cheap.