← Day 01: The route DAY 01 · SESSION 03 · AFTERNOON

Brief it, check it, own it

How to work with Claude as an engineering partner: briefed clearly, building in small loops, and checked by you before anything is kept.

Claude CodeCLAUDE.mdPlan modeThe build loopTests/rewind

Present slides Full screen, one slide at a time · 13 slides

THIS SESSION 01

What you will leave with this session

Explain how Claude.ai and Claude Code differ, and when to use each
Brief Claude with context, goal, reasons, an example and what done looks like
Describe the build loop: plan, build, verify, review, commit
Ask for the right tests and read a diff with five questions
Explain server-side access control and where secrets belong

OUTPUT · A first brief for your slice, saved in product/01-route.md

THE TOOLS 02

Claude.ai vs Claude Code

Claude.ai

Chat in the browser or app; Projects hold your Product Book
Thinking, writing, research and Artifacts
Days 1–3: problem, proposition, prototype, plan

Claude Code

Works in your project folder from the terminal
Reads files, edits code, runs tests and commands, with your permission
Days 3–5: repository, slice, tests, demo

Think in Claude.ai. Build in Claude Code. The Product Book connects them.

BRIEFING CLAUDE 03

Briefing Claude: five parts

CONTEXTWhat the product is, who it is for, and what already exists
GOALWhat you want from this piece of work
REASONSWhy it matters, so Claude can make sensible choices you did not spell out
EXAMPLEWhat good output looks like: a sample, a format, a past case
DONEHow you will both know it is finished, including what to report back

Claude does what the brief says. Give reasons, not just rules, and invite uncertainty.

© 2026 MVP Studios Ltd. MVPAI™ and the MVP Studios Academy course materials, including the MVP Founders Programme and MVPAI in a Week, are original works of MVP Studios Ltd. All rights reserved. No copying, redistribution or commercial use without written permission. Course terms