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

Reading what was built

You do not need to write code to check it. How to ask what changed, what each file is for, and whether it matches the brief.

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

Reading without coding

Checking is your half of the work. You can do it without writing code by asking good questions, looking at the list of changed files and comparing the result with your brief.

A 3D scene of coloured blocks and cards. After each change: what did you change?, why?, what should I test?.
Ask what changed, why, and what to test.

Questions to ask every time

  1. What changed?

    Which files, in one line each.

  2. Why that way?

    Ask for the reason behind a choice you do not understand.

  3. What could go wrong?

    Ask it to name the risks.

  4. How do I test it?

    Ask for the exact clicks to try.

A 3D scene of coloured blocks and cards. Ask for a map: app/, components/, lib/.
A map of the main folders and what each is for.

Reading a change

Green lines

Added.

Red lines

Removed.

The file name

Tells you which part of the app was touched.

ActivityBuild stepThe first working version

Understand your app

Ask Claude Code for a one-page map of your project and save it as "MAP.md". Then, for your last change, ask what changed and how to test it, and do the test yourself.

Done when

Update the map whenever the structure changes.

Keep these

  • Ask what changed and why.
  • Keep a plain-words map of the project.
  • Compare the build with the brief.