ISB AI Founders · portal
3
Week / Day 3 · Fri Aug 7 / Claude Code Mastery
Studio · taught

Claude Code Mastery

You have used it for two days. Now master it: the gap loop, versioning, and never being stuck again.

Open this session's deck →
9:15
start
90m
duration
2
exercises
3
things you leave with
Welcome

You have been building with Claude Code since Wednesday. Today you stop using it like a beginner. The gap loop, checkpoints, knowing when to re-prompt and when to start fresh: these are the moves that separate people who ship from people who stall, and you will learn them on your own product, on problems you actually hit yesterday.

You walk out with
✓The gap loop as a reflex
✓Versioning discipline
✓Your real product, visibly further along
Why this session exists

The difference between people who ship and people who stall is one sentence: I expected X, it does Y. Say it precisely and you are never stuck for long.

The arc, minute by minute
9:15
Agent vs chatbot: what Claude Code actually does
9:30
Live: wireframe + spec go in, working app comes out
9:50
The gap loop: describe, run, test, describe the gap, repeat
10:15
Checkpoints and versioning: commit before you experiment
10:30
When to re-prompt vs when to restart a conversation
Exercises
01
The gap loop, on your product
Take your prototype v0, pick the biggest gap from your wireframe, close it with three precise gap statements.
02
Checkpoint discipline
Save a version, try something risky, break it on purpose, roll back. Fear of breaking things dies today.
prompt · give this to the room verbatim
I expected [X exactly]. It currently does [Y exactly]. The difference matters because [user impact]. Fix the gap without changing anything else that works.
Tools in play
Claude Code
Materials to prep
SCOPE red cardsWireframes from Day 2 on desks
The checkpoint · nothing counts unless it is live
Every team closed at least one wireframe gap, live.
← previousThe Verdictnext →Design with AI