Lesson 4 · talking points
Isto · Claude Code Workshop · 75 min · 24 slides
Open
0:00 · 3′
Slides 1–2
Today: build on your project, your own way, then put it on GitHub. You try, you get stuck, you ask /coach, you try again: that's how you'll work after today, with no teacher.
- Lesson 3's promises: GitHub, today together · the reviewed change, cut · online behind a login and the video, optional · the 4-minute demo, today's share round.
Thumbs up if the Claude app is open and your project folder is on your laptop.
Add /coach
0:03 · 6′
Slides 3–6
The course ends today; getting stuck doesn't. One skill for that, and it's yours for work.
- Why (slide 4):
You're building past what you're used to. Questions are normal there: they mean you're on new ground, not that you're doing it wrong.
Read the five cards; ask which one they've had.
- Stuck on what to do (5): just asking gets Claude's list;
/coach asks you one question back. Hints first, plain words, one safe step.
- Add it (6): watch 1′, then 3′. Download prompt → + New, ask anything → select a few words → Start a side chat →
/coach.
- Can't download? Open the link, copy all, ask Claude to save it as the coach skill.
Build
0:09 · 20′
Slides 7–10 · demo on restock-planner
- Two words: the orchestrator session is the one you talk to: it hands out jobs and gathers results. A thread is a session it opens for one job, under it in the sidebar.
- Where are we (8): watch 1′, they 3′. Prompt 1: where we are, what blocks us, threads for mockups.
They work while you do the same.
- Check the mockups (9): watch 1′, they 6′.
What you change now, Claude won't have to redo.
- The build plan (10): watch 1′, they 8′. Prompt 3, read the plan, then
Go ahead: split it into the threads you think best.
- Not done in 8′?
Leave the session open: it keeps working while we share.
- No project:
/grill-me steps. Waiting on data: invented data in the real shape.
Share and discuss
0:29 · 10′
Slides 11–12 · two screens, ~3′ each, then the room 4′
Who'll show us? Share your screen, and tell us what you asked.
- Sharer · no right promptWhat did you send: the prompts, your own words, or a line from the slide?
- Sharer · stay in the driver's seatWhat did Claude do that you didn't expect? Where did you steer it back?
- Sharer · check before you trustHow do you know it's right? Did you check one number you already know?
- Sharer · /coachWhen you got stuck, did you try /coach? What did it say?
- Sharer · access pocket slideCould Claude get to the data it needed? Whose account was it using?
- Sharer · subagents pocket slideHow did the orchestrator split the build? Did two threads get in each other's way?
- Room · blockers listWho hit the same wall? What did you do about it?
- Room · peer learningWhat would you have asked differently?
- Room · sharing the toolWho else at Isto would use this? What would they need to see first?
- Bridge · GitHubIf a colleague opened your project tomorrow, what would they find?
Two questions per sharer, one for the room. Write the blockers down, grouped by who can unblock them. Stop at 10′: Hold that thought; it comes back in the close.
What did we learn today?
0:39 · 3′
Slide 13
Same as the end of lesson 2 and of your phase 1 build.
Paste the prompt; Claude suggests, then waits.
- If the room is slow, one example:
the export has one row per store: add them up first
· a mockup first saved rework
· keep invented data in the real shape until access comes
.
- Nothing worth saving on a short session is a correct answer.
Put it on GitHub
0:42 · 15′
Slides 14–16 · demo on restock-planner-l4
A safe copy on GitHub, kept each time you push, and a colleague can pick it up.
Only what you push is kept: push again after each change you want saved.
- Three steps, each 1′ on your screen then 3′ on theirs: Check GitHub → Create the repository → Push.
.env: the file where a project keeps its passwords and keys; it never goes to GitHub.
- It says Public?
Make this repository private now.
Wrong account? Blockers list, don't fix live.
Shapes of a project
0:57 · 9′
Slides 17–18
Last thing before we close: what else could you build, and what shape would it take?
- One line per card.
Same method for all of them: plan, build one phase, check.
Which of these do you do by hand today?
· Which one would you build next?
Close
1:06 · 3′
Slides 19–20
This is trial and error. There's no one right way to work with Claude Code; you find yours by trying. Push past the resistance and build: the new app makes starting easier. Over time you'll use it to run your day-to-day work too.
- After class: the final questionnaire, about two minutes, for the certificate. Ask everyone to do it today.
- Copy the meeting chat; the blockers list goes to the managers in one message.
Spare and questions
1:09 · 6′
- Spare minutes cover GitHub sign-in snags, then questions. Late? Cut the spare, not the close.
- Pocket slides 21–24 (subagents, access) only when a topic comes up.