What today looks like

The 75 minutes.

This is the first Advanced session — the pair that shows you how real things get built. Same rules as every stage: you do the work, no coffee break, the hands-ons are the break.

PresenterName the tier in one sentence, then move. No pricing, no pitch — the offer is stage 6's close, not yours.

Where you got to

Your work has addresses now.

• A dashboard changed in front of the room at the same URL.
• A questionnaire of your own went live and started collecting answers.
• The loop: say the change, see it live.
• Tools that run without you keep the work current.

PresenterThree minutes, and ask: “Who actually sent their questionnaire?” That was the homework. Then the segue: everything so far happened inside one window. Today we step out of it.

Claude Code

The same Claude, in a terminal.

Claude Code is Claude with its hands on the files — it reads a whole project, plans a change, makes it, and shows you exactly what it did. The window looks technical. The conversation is the same one you've been having since stage 1: plain English in, work out.

The terminal is not the skill. Saying what you want clearly is the skill — and you've had four sessions of practice.

8 minutes · the install check

Launch it.

Installed before today per the email? This takes ninety seconds. Didn't? Pair with a neighbour for the session — the install guide in your pack gets you running at home tonight, step by step, pictures first.

PresenterWalk the room, fix the quick ones, pair the slow ones. Do not stop the room for one machine. The /context line is a planted seed for w13 — make sure they run it.

The trust beat

The plan comes first.

Say add an export button to the reports page — plan first. Before a single file changes, Claude Code lays out what it will touch, in what order, and why. You read it and approve it — or say no, and nothing happened.

This answers “but what if it breaks something?” Nothing happens until you say yes. That's not a setting — it's the way of working you're learning today.

PresenterRun it live on the throwaway repo. Read the plan out loud, slowly. The room needs to see that a plan is readable by a non-programmer — that's the whole trust argument.

Before and after

Read the change, then decide.

A diff is before-and-after with the changes marked: red went away, green arrived. This frame shows the edit already applied; your job here is to read what changed, ask if anything looks wrong, and approve it or push back.

You review changes for a living. This is the same job with better highlighting.

PresenterApprove the w8 change live and let the room watch it land. Then show the app actually running with the button in it — the diff is abstract until the thing exists.

12 minutes · the throwaway repo

Your turn — and you can't break anything.

The repo is a throwaway built for this room. Break it with confidence — that's what it's for.

PresenterWalk the room; do not sit down. Send one-word prompts back to stage 1: say what you want and what done looks like. Sit with anyone afraid to approve for one approval; the fear doesn't survive contact.

You already know this idea

CLAUDE.md — your context skill, one level down.

In stage 1 you built a context skill so Claude knows who you are on every task. A project's CLAUDE.md is the same idea for a codebase: what this project is, how it's structured, what the rules are. Claude Code reads it every session, automatically.

Same lesson as ever: context in once, quality out every time after.

/context

Tens of thousands of tokens went before you typed.

A session starts with a chunk of its memory already spent — the tool's own instructions, your CLAUDE.md, the project map. The rest is your working room, and everything you do eats it. When it runs low, answers get worse before they stop.

Same physics as “one topic, one chat” — you learned it in the chat window; here there's a gauge for it.

PresenterRun /context live on your open session. After the w8–w9 work it will show real spend, which is the point. This is D9's code half; the room half was stage 2.

/compact

Clear at task boundaries.

When one job ends and the next begins, /compact — Claude keeps a summary of what mattered and clears the rest. New room to think, same knowledge of the work.

A task boundary is the moment you'd say “right — next”. That's when. Not mid-job.

Longer jobs

The handoff: summarise → clear → paste back.

For a job too big for one session: ask for a handoff summary of where things stand, start fresh, paste it back. Thirty seconds of ritual, and the new session picks up mid-stride. It's the same trick your own team uses when a shift changes.

PresenterDon't demo this one — assert it and move. It lands properly the first time they hit a long job at home; the deck's job is that they recognise the moment.

Not a demo repo

Five minutes inside a shipped app.

Everything you've been taught scales to this. Same tool, same habits, real store, real users.

PresenterYour machine, read-only, rehearsed — no env files, no keys, no store credentials on screen. The real repo is never distributed or cloned by attendees. Don't accept “can it add a feature to Prune live?” — park that scoping conversation. If the machine dies, narrate this three-step walk from the slide.

Point it at a drawing set.

Say analyse this drawing set. A folder of construction drawings goes in; out comes a structured index — every sheet, every reference, cross-checks between them — that later questions answer instantly. One pass, then it's a resource.

This one is a live demo today, not a download — it ships to your pack once its cleanup lands. The tool you installed is the takeaway of this stage.

PresenterConstruction/CM route only. In a non-construction room, skip this slide and give the 5 minutes to the w10 hands-on. Do not improvise a route for another industry.

What you unlocked

Six things, one tool.

Stage 6 shows you the pipeline that turns this tool into shipped products — and it's the last rung of the ladder.

One real question this week

Take the guide, keep the repo, and see you at stage 6.

Stage five's takeaway is the tool itself. No zip — your downloads are the guide and the practice project.

Start here · install guidePractice projectDeck PDF

Scan to add Stuart to your contacts.
training.stuartdigital.io/card

PresenterHomework: one real question against a real project this week. Not a change: a question. “Where does X happen?” is how trust starts. Name the stage-6 date.