Teacher handover

Isto · Lesson 3

Thursday 22 October 2026 · 15:30 Lisbon · Google Meet · English. Skills, automations and GitHub.

The deck Teacher view Restock planner (private repo) brand-brain-demo (private repo)

The two repositories are private: they open once you have accepted our invitations.

Start here

  1. Watch the two videos below: about 14 minutes in all.
  2. Do the checklist in section 4 of the written handover. Tick the boxes as you go; your ticks stay in this browser.
  3. Rehearse the demos, then send the check-in form by Wednesday 21 October, 15:00 Mexico City (22:00 Lisbon).

Your preparation should take 1 to 2 hours. The rehearsal is the part not to skip.

Want a helper? Give this checklist (.md) to your own AI assistant, Claude, Grok or any chat, and it walks you through the preparation.

Video 1 · Cohort intro 2:22

Keys: J back 10 s · L forward 10 s · K play or pause
Transcript

1 · Title. This is the cohort intro for Isto: who they are, what they want from the course, and the eight people you will teach. The class video covers the lesson itself, and the written handover below has every detail.

2 · The company. Isto is a Portuguese apparel brand, about nine years old. Around two hundred products with sizes, four collections a year, six stores and two warehouses. A restock takes about eight weeks to arrive, and for Pedro, the owner, stock is cash.

3 · Systems and pain. Their data lives in several places. Sage holds stock, purchase orders and accounting. Shopify holds online sales. Notion holds product information, and production plans live in Excel. Ask the same question in two systems and you can get two answers. An earlier attempt with Power BI gave inconsistent numbers.

4 · What they want. What they want from this course is one shared source of truth, that everyone asks the same way. The thread we use in class is a single product, a white t-shirt: forecast, stock, sale, sell through and replenishment. Then the same thinking, scaled to a hundred products.

5 · The course. The course is four live lessons on Thursdays, at half past three Lisbon time, in English. They work in Claude Code inside VS Code. Before each lesson there is a pre-work pack on the Academy platform. Several of them already used Claude and Cowork, so the course skips the basics.

6 · The room, part one. Eight people. Pedro is the owner; he cares about stock because it drives cash. Ricardo is ahead of the room on Claude. Jerónimo is an experienced planner who tests ideas against the direct way, so give him the why first. Sofia needs to see the destination before the steps, and she cares about who is allowed to feed a number others rely on.

7 · The room, part two. Rita administers their Claude organisation, so organisation settings go through her. Manuel had setup trouble in lesson one, so check his panel early. Teresa and Gonçalo: little recorded so far; Gonçalo found the pre-work hard, like Sofia did.

8 · Tone and contact. The tone is friendly and informal, and a little apologetic about asking questions, so tell them questions are the point. They ask how things would work inside Isto more than about tools. You talk to the group in the WhatsApp group, and we add you. Anything about scope, dates or the contract comes to us.

Video 2 · The class 12:01

Keys: J back 10 s · L forward 10 s · K play or pause

Chapter C is the slide-by-slide walkthrough. Open the teacher view beside it: each slide with its notes next to it, and the set-up for each demo.

Transcript · A · This week

1 · Title. Lesson three, Thursday the twenty second of October, at half past three Lisbon time. This chapter is what happened before your class and what is particular to this week. Then a chapter on getting ready, and then the walkthrough, slide by slide.

2 · Lesson 1. Lesson one, on the eighth of October, was about what Claude knows. A tour of VS Code, a practice project for a fictional apparel company called Este, and CLAUDE dot md, the file that tells Claude about a project. Most of it was demonstration, and setup took longer than planned.

3 · Lesson 2. Lesson two was plan, build, check, and everyone came except Pedro. Raffaello built a restock planner with the room. The plan was written with Grill Me, a skill that interviews you to write the plan. It was then split into phases, sketched as text and then as a mockup. It closed with a habit: ask Claude what the session taught that is worth saving.

4 · What did not work. One thing did not work. Participants followed each step on their own laptops, and when one person got stuck, the whole room stopped. That is why lesson three is watch only. Sofia and Gonçalo also said the lesson two pre-work was hard, not because of jargon, but because they could not see the end goal.

5 · The pre-work since. Before your class they have seventy seven minutes of pre-work: build phase one of their own project, create a GitHub account, and install git and the GitHub tools. As of Tuesday the twentieth, nobody had submitted anything. Check the Academy again on the morning of the class.

6 · Promises that land on you. Two promises from lesson two land on you. Feeding the database from Sage and Shopify comes in lesson three: in your class, that is a discussion of scheduled jobs, not a live build. And lesson two said lesson three would start with GitHub; tell them it comes in the second half, after skills and automations.

7 · Questions to park. One question is still open: who owns cleaning the shared data for the team's real project, which Jerónimo asked in lesson two. If it comes up, note the question and pass it to us.

8 · After the class. Record the class in Google Meet, and send us the link within a day. Then reset your laptop: remove the project status skill and the exports hook, and put the planner and its repository back to the prepared state. Fill in the feedback form within twenty four hours. The most useful part is where this handover fell short: every time you relied on something you already knew, or would have had to ask us.

Transcript · B · Get ready

1 · Title. Getting ready. Live classes break on preparation more than on content, so this is where most of your prep time goes. The full checklist, in the same order, is on the page below the video.

2 · Access. First, access. A Claude account that includes Claude Code. A GitHub account you are signed in to, both in the browser and in the GitHub tools, because Claude pushes the change and opens the pull request through them. Then accept our three invitations: the Academy, to read the pre-work answers, the calendar series, which has the Meet link, and the two private GitHub repositories, the restock planner and brand brain demo.

3 · Your laptop. On your laptop: VS Code with the Claude Code extension, git, the GitHub tools, and Python, which the hook demo uses. Keep your computer in light mode too. If one of these is missing, install it a day ahead, not on the day; in lesson one, setup took longer than planned.

4 · Two prepared projects. Two prepared projects. Brand brain demo: clone it twice, as two clean copies; the second one is the fallback for the hook demo. And the restock planner: clone its GitHub repository; Raffaello built it with the room in lesson two. In light mode its page is light, and the GitHub demo turns it pale yellow.

5 · The GitHub demo, prepared. For the GitHub demo, the planner's repository is the one you use, so once you have cloned it, it is already connected; there is nothing to create. Make a backup pull request there with the same pale yellow change, and keep it open in a tab. If the network or the login fails live, that is what you show.

6 · Rehearse. Then rehearse. None of these demos has been run on a teacher's laptop yet. Run each demo twice, the skill, the hook and GitHub, each time from a clean state. For the hook, check that every kind of change is stopped, while reading the export and the loading script still work. Afterwards, delete the project status skill, remove only the exports hook, and close the rehearsal pull requests, keeping the backup one.

7 · Check in with us. By Wednesday the twenty first, at three in the afternoon Mexico City time, ten at night in Lisbon, send us the check-in form: ready, or not ready on what. That leaves time for us to help. Preparation gets fixed before class, never by debugging in front of the room.

8 · The morning, and ten minutes before. On the morning of the class, check the Academy for pre-work answers; if there are some, line up two people to show their build, and keep one answer you can read out, with its author's OK. Ten minutes before: remove the project status skill, any connector, and only the exports hook, leaving any other hooks in place. Leave one small uncommitted change in the planner, and discard it right after the skill demo. GitHub open and signed in. Deck on the first slide, screen share and audio checked.

Transcript · C · The walkthrough

1 · Title. Slide one, the title. Have it up as people join. This chapter walks the deck slide by slide: what you say, why, and what to watch for. Keep the presenter agenda open next to it for the exact wording.

2 · Before we start. Slide two. Say how today works, plainly: the skills, the hook and the GitHub loop are demos, so watch, don't type; they do the same steps in the pre-work. Point at card two: the Sage and Shopify feed is a discussion of the scheduled jobs that could keep the database current. Say GitHub comes in the second half. Then ask for a thumbs up from everyone whose git and GitHub are set up, and note who isn't.

3 · The building blocks. Slide three, the six building blocks. One line per block, in order; this is the map, not the lesson. Say aloud: without these blocks, you are Claude's memory and messenger. Point at lessons one and two, then at lesson three: today the tool stops depending on you. Four minutes, no more.

4 · How did it go. Slide four starts the build debrief, eight minutes. Two people share their screen for two minutes each: the project in one line, where they got to, one place Claude went off track. Ask one follow up only: what did you say to bring it back? If screen sharing fails, they describe it while you point. If the Academy still shows no submissions that morning, skip the shares and use the who got stuck path on the next slide.

5 · Where in the loop. Slide five is the loop. As they talk, point at the step: that was the mockup step. Most snags land on the same two or three steps, so say which ones. Land it with: which step did you do twice? Hold that thought. If nobody did the pre-work, ask who got stuck and where, or show the restock planner for two minutes.

6 · Three concepts. Slide six comes before any demo, so the room has the words for the rest of the class. Three concepts, not a sequence. A skill is a job Claude repeats the same way. An automation runs without someone starting it. GitHub is separate: one shared copy where changes get reviewed. Link back: the job you did twice is the kind of job a skill can hold.

7 · How automation starts. Slide seven: an automation starts when something happens, or when a time arrives. Use the two Sage examples on the slide, then name only one term, cron, for scheduled work. Ask the room for one event and one timed job, then bridge: now I will show what these look like on one tool.

8 · Skills in Claude Code. Slide eight. Most of this room has used skills before, in Cowork or with Grill Me, so skip what a skill is. Say every skill in Claude Code has a skill dot md file you can open, either global for every project or local to one. Open the global skills folder, then a project's. Ask who saved a skill in the pre-work.

9 · The skill demo. Slide nine, the skill demo, four minutes. In the restock planner, paste the prompt. Open the file Claude shows: the description at the top is what Claude reads to know when the skill applies. Type a slash, it is listed, run it. The small change you left gives what changed recently something to show. Discard that change before the GitHub demo.

10 · What a skill can carry. Slide ten, two folder shapes. A small skill is just its skill dot md file. Add templates or references when Claude needs reusable material, and a script when a repeated step must be exact. Ask which supporting file would help one of their own skills. Two minutes.

11 · Check before you trust. Slide eleven, the habit. A new skill is like a new colleague's first report: check one result against something you know is right before you rely on the rest. It can be a stock figure or a total, or an approved template. If it matches, use it. If not, fix the skill and check again.

12 · Hooks. Slide twelve. Say: a hook is a safety check inside Claude Code; it runs at a named moment, every time. It is one kind of automation, not the name for all of them. Today it runs before Claude changes an original export. If asked: hooks run with the computer account's permissions, so only use one you or a colleague reviewed.

13 · Protect the original data. Slide thirteen, the hook demo, on a clean copy of the practice project. Paste prompt one, and show the new hook in plain English, added next to any hooks already there. Start a fresh conversation and paste prompt two. The change to order E C three zero one is stopped. Say: a rule can be forgotten; this check runs before the change. If it does not fire, repeat on the second copy. If it still does not, show the tested hook file and say the live result is not reliable enough to claim.

14 · Three scheduled jobs. Slide fourteen, three cron ideas, five minutes. A cron starts a job when its time arrives; it does not decide what matters, the owners do. Read each lane left to right: the time, the source, the result. Say plainly these are ideas to assess, not systems running at Isto. Ask which one would save the most repeated work, and who would own its result.

15 · Where it runs. Slide fifteen. Point back at the seven o'clock idea: if nobody's computer is on, the job cannot run, so it needs an always on service. Three questions: who pays, who keeps it updated, and where the passwords live, which is the server's settings, never a file or a chat. Do not open a server live. Who owns it is a lesson four decision.

16 · One shared history. Slide sixteen opens part two, GitHub. Read the picture left to right: a proposed change, pushed to the review gate, merged, then pulled back to your project and a teammate's. The cloud is the one shared copy, not someone's computer. The gate stops a change reaching that copy before review. Keep it a picture, not a vocabulary lesson.

17 · One compact loop. Slide seventeen, the GitHub demo, eight minutes. Paste the first request and show the pale yellow page. Then the second: Claude makes a separate working version and opens a pull request. Read the diff, and ask Claude what changed and whether anything else did. Say you are the reviewer here only to show the route. Stop at the pull request; step four on the slide, the pull, is not shown today. If it fails, show the backup.

18 · To keep. Slide eighteen, the close. One line per habit; they join lesson two's four. Then the lesson four pre-work, which goes up after class: their own project on GitHub, one change reviewed by a teammate, one saved skill, their page online behind a login, and a four minute demo. Tell them to keep the restock planner and the practice project, the brand brain demo folder.

19 · Questions. Slide nineteen stays up for the questions, about seventeen minutes. Park anything that belongs to a later lesson, note it, and pass it to us. If someone hit a setup problem, note who and send us the details afterwards, rather than fixing it in the room.

For the teacher who runs this class. We (Raffaello and Giuseppe) wrote the material; you deliver it. You do not need the repo, and you do not need to write or change any content.

The class: Thursday 22 October 2026, 15:30 Lisbon time, Google Meet, English. 75 minutes of teaching, then a 15-minute buffer (the calendar blocks 15:30 to 17:00).

Your prep: 1 to 2 hours. Suggested order: watch video 1, the cohort intro (3 minutes), and video 2, the class (13 minutes: this week, get ready, the walkthrough) → do the section 4 checklist (30 minutes) → rehearse the demos from section 5 (45 minutes) → send the check-in form by Wednesday 21 October, 15:00 Mexico City (22:00 Lisbon). The rehearsal is the part not to skip.

1. Who the client is

ISTO. is a Portuguese apparel brand (isto.pt). About nine years in business, around 200 products with sizes, four collections a year, six stores and two warehouses, prices in euros, dollars and pounds. Restocks take about eight weeks to arrive.

Their systems: Sage 50c (ERP: stock, purchase orders, accounting), Shopify (online sales), Notion (product information), Excel (production plans). The pain: the same question gets a different answer depending on which system you ask, and a Power BI attempt gave inconsistent numbers.

What they want from the course: a shared source of truth over those systems, that everyone queries the same way. The running example in class is one product, a white t-shirt: forecast, stock, sale, sell-through, replenishment, then scaled to a hundred products.

The course: AI Builder Bootcamp, four live lessons on Thursdays, Claude Code inside VS Code, taught in English. Lesson 1 was 8 October, lesson 2 was 15 October, lesson 3 is yours (22 October), lesson 4 is 29 October. Some of the group already knows Claude from Claude.ai and Cowork (Ricardo ran his own introduction before we started), so the course skips that.

Contact with the group: the WhatsApp group "Isto & Adaptto.ai"; we add you to it. Ricardo Ferreira is the client contact for the course as a whole: anything about scope, dates or the contract goes to us.

The eight participants

Person What we know
Pedro Palha Owner and buyer. Early with AI; had not used connectors at the start. Cares about stock balance because it drives cash flow.
Ricardo Ferreira Finance and business; runs several companies. The most advanced with Claude. Has built websites. Owns the company brain, the shared project everyone contributes to.
Jerónimo Garcia del Rio About 20 years as a senior inventory planner. Between Pedro and Ricardo on AI.
Sofia Seruya Production side; her team owns delivery dates. Had never programmed.
Rita Bilbao Serrano The administrator of Isto's Claude organisation.
Manuel Salgado Little recorded beyond a setup problem in lesson 1.
Teresa Vasconcelos Little recorded so far.
Gonçalo Rato Little recorded so far. (Some notes spell it Gonçalo Moreira Rato.)

Section 6 has notes on how to run the room with these people.

2. What they have already seen

Before lesson 1 (pre-work, about 60 minutes)

Welcome, a short questionnaire about their AI use, setting up VS Code with Claude Code, and setting up their project folders.

Lesson 1 · 8 October · taught by Raffaello

Why Claude Code, and how it differs from Cowork. A tour of VS Code. Downloading a practice project (a fictional apparel company called Este, used for all practice). CLAUDE.md, the file that tells Claude about a project, and memory, what Claude keeps between sessions. Where each kind of instruction goes.

It was mostly demonstration; participants installed, downloaded and opened things. Setup took time: for several people the Claude panel disappeared when they opened a new folder, and the remote-control setting needed their administrator (Rita).

Pre-work for lesson 2 (about 60 minutes)

A one-time VS Code workspace, installing the Grill Me skill, planning their own project with it (saved as PLAN.md), building the project skeleton with a short CLAUDE.md, a free Supabase account, and downloading and connecting to the shared practice database.

Lesson 2 · 15 October · taught by Raffaello

Everyone attended except Pedro.

Asking the practice data questions, then plan first, sketch, mockup, build: Raffaello built a "restock planner" with the room, using Grill Me to write the plan, splitting it into phases, sketching phase 1 as text and then as a mockup. It ended with the habit of asking Claude, at the end of a session, what the session taught that is worth saving.

What did not work: participants followed along step by step on their own laptops. When one person got stuck the whole room stalled. That is why lesson 3 is watch-only. Also, the framework (plan, phases, build little by little) arrived too late and in pieces; and the demo skipped the Supabase sign-in because the connector was already installed on the teacher's laptop.

What landed: commenting on a plan (changing "last 56 days" to 60), sketch-then-mockup, and the closing "save what you learned" habit.

Two things people said that you will hear again: Sofia and Gonçalo found the pre-work hard, not because of jargon but because they did not know the end goal while going step by step. Jerónimo asked why not simply prompt Claude directly; the answer given was that Grill Me gets closer by proposing standard options while the expert stays in charge.

Pre-work for lesson 3 (about 77 minutes, due before your class)

A feedback form (2 minutes), building phase 1 of their own project (50 minutes), creating a GitHub account (5), and installing git and the GitHub tools (20).

As of Tuesday 20 October, nobody has submitted anything for the lesson 3 pre-work. That is a fact you need to plan around (section 7). The lesson 2 pre-work did get answers: 12 were submitted on the planning lesson alone, by a group of eight.

What was promised to them, and where it lands

Promise Said in Where it lands
"Feeding the database from Sage and Shopify comes in lesson 3" Lesson 2 opening Lesson 3, as a discussion of scheduled jobs. Not a live feed build.
"Lesson 3 starts by putting the project on GitHub" Lesson 2 close Second half of lesson 3, after skills and automations. Say so out loud.
Skills and automations, and sharing work as a team Lesson 1 Lesson 3
Access and approvals: who sees what Lesson 1 Lesson 4
Demos of what they built Lesson 1 Lesson 4
Homework available on the platform Lesson 1 The platform has it; the next pack goes up after your class

3. What this class covers

Lesson 3 · Skills, automations and GitHub. Seventy-five minutes. By decision, nothing is hands-on: the skills, the hook and the GitHub loop are demonstrations (watch, don't type). They do the same steps on their own project in the pre-work for lesson 4.

How the 75 minutes split: they show 8 minutes (how the build went) · you show and they watch and suggest 29 minutes (skill 9, hook 5, scheduled-job ideas 5, GitHub 10) · you talk 21 minutes · questions 17 minutes.

Time Block Min
0:00 Opening: how today works, lesson 2's promises 3
0:03 The six building blocks of the course (the map) 4
0:07 How the build went (two participants share a screen) 8
0:15 Skills, automations and GitHub: the three concepts 8
0:23 Skills in Claude Code (demo) 9
0:32 A hook that protects the original Sage exports (demo) 5
0:37 Three scheduled-job ideas for a company (discussion) 5
0:42 Where work that runs on its own lives 4
0:46 GitHub: one shared history, one reviewed change (demo) 10
0:56 Close and what comes next 2
0:58 Questions 17

The deck and the teacher view (the deck with the agenda beside it) are on this page (links in the header). Video 2, chapter C, walks the deck slide by slide. Keep the teacher view open as the reference: its Agenda tab has the exact words, what to click, the expected result and the fallback for every block.

The outcome we want: a verified skill, a clear model of automations (they start when something happens or when a time arrives), and one GitHub loop seen live.

4. Setup so the class and the demos run

This is the complete list. It comes from every "Before class", "Test before class" and "Reset" note in the agenda, the hook demo notes, and the lesson 2 debrief.

1. Access

2. Your laptop

3. Two prepared projects

4. The GitHub demo, prepared

5. Rehearse

None of these demos has been run on a teacher's laptop yet.

6. Check in with us

"How the build went" (block 3): who shows their build

The class opens with two participants showing, for two minutes each, the phase 1 they built in the pre-work. It is the bridge into skills: "the step you did twice is the kind of job a skill can hold." The agenda suggests lining two people up before class so the block does not open on silence. Nobody has submitted the pre-work yet, so check the Academy the morning of the class. If there is still nothing, skip the asking and use the agenda's "if few did the pack" path: ask the room who got stuck and where. If you do want volunteers in advance, a short message in the group the day before is enough.

Ten minutes before the class

After the class

Reset: remove project-status, remove only protect-original-exports and confirm any other hooks are still there, restore the demo clone, and close or recreate the backup pull request.

5. The demos: what to type, what should happen, what to do if it does not

The agenda has the full wording for each. These are the prompts exactly as they appear on the slides.

Demo 1 · Skill (block 5, 9 minutes). In the restock planner, paste:

Make a global skill called project-status. When I ask for project status, tell me: what this project is for, what changed recently, what I should do next, and any risks or blockers. Do not change anything. Show me the file.

Expected: Claude creates ~/.claude/skills/project-status/ with a SKILL.md inside and shows it. Type / in the Claude panel: the skill is listed. Then paste Use project-status. and it gives a plain-language snapshot. If the skill does not appear: close VS Code fully and reopen it. Still no: show the file anyway and ask "Use the project-status skill."

Demo 2 · Hook (block 6, 5 minutes). Use a clean copy of brand-brain-demo. Paste:

Keep the original Sage exports in this project's data/raw folder unchanged so our stock and purchasing reports keep using the source data. If Claude tries to change one, however it tries or wherever I start the conversation, stop it and say: "Original exports stay unchanged. Make a correction note instead." I still need to read and load the exports as usual. Show me what you set up in plain English.

Then start a fresh Claude conversation and paste:

Change order EC301 to CE301 in the original Sage purchase-orders export.

Expected: the change is stopped and Claude says to make a correction note instead. Reads of the export and python load.py still work. If the hook does not fire: try again on the second clean copy (prompt 1, fresh conversation, prompt 2). Still not: show the tested hook file and say the live result is not reliable enough to claim. Do not improvise another protection. The check matches the path as written in the command, so it is a safety check, not a complete security boundary; say so if asked.

Demo 3 · GitHub (block 9, 10 minutes). In the planner with its private repository, paste:

Make the dashboard background a pale yellow instead of white. Show me the result before you save it.

Show the visible change. Then paste:

That looks good. Put the change on GitHub and open a pull request for a colleague to review. Do not merge it yet.

Open the pull request and read the diff. Then ask Claude: "Show me exactly what you changed, in plain English. Is anything else different? Do not merge it yet." Say: no colleague is reviewing this demo, you are checking the diff yourself to show the route; in real work a teammate reviews and approves. Stop at the pull request. If GitHub or the network fails: show the backup pull request, read its diff, and trace the push, review gate, merge and pull arrows on the slide. Do not spend the questions block debugging login.

Not a demo (blocks 7 and 8). The scheduled-job ideas and "where work that runs on its own lives" are discussion. Do not set up or open a server live. Say plainly that these are ideas for Isto to assess, not systems already running.

6. The room

Written for running the class, not for judging anyone. Facts come from lessons 1 and 2 and the pre-work; the "how to engage" lines are our judgement and may be wrong.

Person How to engage
Pedro Palha The owner. Frame things in stock and cash. Missed lesson 2, so he has not seen the planner built.
Ricardo Ferreira Will be ahead of the room on Claude. Good source of a real "who should own this" answer in the automation discussion.
Jerónimo Garcia del Rio Experienced planner who tests ideas against doing it the direct way. Give him the "why" before the "how"; his questions usually help the whole room.
Sofia Seruya Needs the destination before the steps. After each step, check she can see where it is going. In lesson 1 she raised an important concern: who is allowed to feed a number others rely on (marketing feeding delivery dates). That is your opening for the automation-ownership point.
Rita Bilbao Serrano Claude administrator for Isto. If something needs an organisation setting, it is her.
Manuel Salgado Had the most setup trouble in lesson 1. Check early that his Claude panel works.
Teresa Vasconcelos, Gonçalo Rato Little recorded. Gonçalo found the pre-work hard for the same reason as Sofia.

General tone: friendly and informal, fluent English, practical, a little apologetic about asking questions (tell them questions are the point). Their questions are about how this would work inside Isto (ownership, who sees what), more than about tools. In lesson 2 a stuck person held up the room: keep to "watch, don't type", and for anything that needs a screenshot, take it to the group chat afterwards.

Pedro missed lesson 2. He has not seen the restock planner built or Grill Me in action; one sentence of context when you open the planner is enough.

7. What can go wrong

Risk What to do
The demos have not been rehearsed. The agenda's two-run evidence tables are empty, and two checks are still open (the hook prompt and the GitHub prompt, each twice in clean sessions). Do section 5 yourself, twice for the hook and the GitHub demo, before class. Tell us what you could not reproduce.
No pre-work answers. Block 3 depends on them. Use the "if few did the pack" path in the agenda. Ask who got stuck and where, pin each answer to a step of the loop. If nobody can show anything, show the restock planner for two minutes: it is phase 1 of that loop.
Your laptop is already set up. A pre-installed connector or skill hides the step they need to see. Section 4, "ten minutes before".
Someone wants to type along. Lesson 2 showed this stalls the room. "Watch today. You do exactly this on your own project in the pre-work."
A demo fails live. Use the fallback in section 5. Say the result is not reliable enough to claim; do not improvise.
Setup problems you did not cause. The Claude panel disappeared on some laptops after opening a new folder; some people could not save a VS Code workspace; one person could not sign in to Supabase. Do not fix them in the room. Note who, and send the details after class.
Running over. Lesson 1 ran over. You have 17 minutes of questions and a 15-minute calendar buffer. Never take time from the demos.
An open question. Who owns cleaning the shared database for the team's real project (Jerónimo asked in lesson 2). Note it, pass it to us, and put it in the feedback form. Do not promise dates or recordings.
The practice database. The free Supabase project pauses after a week without use. Lesson 3 does not need it. Ignore unless asked.

8. After the class

  1. Record the session in Google Meet and send us the link within a day. We publish it and the deck on the Academy.
  2. Fill in the feedback form (about 10 minutes, within 24 hours): what broke, who struggled, what questions are open, and how well this handover worked for you. The last part matters most: tell us every place where you used something you already knew, or would have had to ask us.
  3. Send us the questions you parked. Do not answer for us on anything about contract, price, dates or what lesson 4 will contain beyond what the close block of the agenda lists.
  4. The lesson 4 pre-work goes up on the Academy after class. We do that; you do not.

What you say at the close (the close block of the agenda has it): the habits that join lesson 2's four; the lesson 4 pre-work list (put their own project on GitHub, take one change through the loop with a teammate's review, save one skill from their build, put their page online behind a login, prepare a four-minute demo for lesson 4, and optionally the privacy guard on their own project); and keep restock-planner and brand-brain-demo.

Feedback form: Isto L3 · After the class.