# Isto lesson 3: help me get ready I am a freelance teacher preparing to run one live class: lesson 3 of a Claude Code course for a client called Isto (Thursday 22 October 2026, 15:30 Lisbon time, on Google Meet). I have no background on this course. Below is my preparation checklist. Please help me work through it. ## Links I will need - Teacher handover page: https://adapttoai-handover-isto-8a262f.pages.dev/ - Check-in form: https://tally.so/r/1WAkBl - Teacher view (the slides with notes beside them): https://adapttoai-handover-isto-8a262f.pages.dev/teacher.html - The class deck: https://adapttoai-ccw-isto-l3.pages.dev/ - Academy (sign in with your invitation): https://academy.adaptto.ai - Restock planner (private repository): https://github.com/staraceraffaello-blip/restock-planner - brand-brain-demo (private repository): https://github.com/staraceraffaello-blip/brand-brain-demo ## The three demos I will run in class 1. **Skill:** ask Claude to create a skill called `project-status`, in the restock-planner project. 2. **Hook:** ask Claude to create a safety check (a "hook") that stops changes to the original data files, in brand-brain-demo, then try to change one and see it refused. 3. **GitHub:** change the page background in restock-planner to pale yellow and open a pull request without merging it. Each one is rehearsed once, or twice if there is time. The exact prompts are in the "Demo prompts" part of the handover page. ## How to help me - Take one area at a time (Access, Your laptop, Two prepared projects, The GitHub demo, Rehearse, Check in). Start by asking which computer I use (Windows, Mac or Linux) and keep every answer for that computer. - For each item, tell me in plain words what it is for, how to do it, and how I can check that it worked. Ask me to confirm, or to paste what I see, before we move on. - When you give a command, give it for my computer and explain in one line what it does. Keep steps small. - Never ask me for a password, a token or a key, and never accept one in this chat. If one is needed, tell me where to type it myself. Sign in to GitHub's tool with `gh auth login` and choose the web-browser option; never type a GitHub password into the terminal. - Do not change the files inside the two projects to make a demo work. The steps in the checklist itself are fine (cloning, the demos' own pull requests, the reset). If you can run commands yourself, ask me before each one and say what it does. - Explain every check in one plain sentence. The tool names in the checklist (Edit, Write, Bash and so on) are for you, not for me. - You cannot decide for me whether a step can be skipped. Tell me what the checklist says, and if I cannot do something, help me say so on the check-in form. - On Windows, if typing `python` opens the Microsoft Store, install Python from python.org and tick "Add to PATH". To put a project back to its clean state, delete its folder and clone it again. The skill lives in `C:\Users\\.claude\skills\project-status`. - If something fails, ask me for the exact message. Help me work out whether it is my computer or something the team has to fix. If the team has to fix it, help me write one clear sentence for the check-in form. Do not suggest workarounds that would change what the demos show. - Urgent problems before the class: I write to the team in the WhatsApp group. The check-in form is for the written summary. - If you do not know something, say so. Do not guess. - Keep a running list of what is done and what is not. ## At the end Give me a short summary I can paste into the check-in form: - Done: ... - Not done: ... - Questions for the team: ... # My checklist 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 - [ ] A Claude account that includes Claude Code. - [ ] GitHub: an account, signed in **in the browser and in the GitHub tools** (`gh auth status` says logged in). Claude pushes the change and opens the pull request through them. - [ ] The Academy invitation accepted: you can open the Isto cohort and its pre-work answers. - [ ] The calendar invitation accepted: you have the Meet link. - [ ] The invitations to the two private GitHub repositories accepted (you are a collaborator on both): the restock planner and `brand-brain-demo`. - [ ] You are in the WhatsApp group "Isto & Adaptto.ai". ### 2. Your laptop - [ ] VS Code with the Claude Code extension. - [ ] git and the GitHub tools (`gh`). - [ ] Python (the hook demo uses it). - [ ] Your computer is in **light mode**. The planner page follows it: in dark mode its background is dark. ### 3. Two prepared projects - [ ] `brand-brain-demo`: clone the private repository (link above) **twice**, into two folders, as two clean copies. The second is the fallback for the hook demo. - [ ] The restock planner: clone its private GitHub repository (Raffaello built it with the room in lesson 2). Open it in VS Code next to `brand-brain-demo`. In light mode its page is light grey with white cards: the GitHub demo turns the background pale yellow. ### 4. The GitHub demo, prepared - [ ] The planner's repository **is** the demo repository: once cloned, the planner is already connected. Nothing to create. - [ ] A **backup pull request** in that repository with the same pale yellow change, open in a tab. You make it yourself: run the GitHub demo once and leave its pull request open. - [ ] Invented data only. ### 5. Rehearse None of these demos has been run on a teacher's laptop yet. The prompts are in Demo prompts, expected results and fallbacks. - [ ] Skill: once, or twice if you have time, each in a fresh session on the account you present with. Then delete `~/.claude/skills/project-status/`. - [ ] Hook: once, or twice if you have time, the second in your other clean copy (prompt 1, fresh conversation, prompt 2). Check that changes through `Edit`, `Write`, `NotebookEdit`, `Bash` and `PowerShell` are all stopped, that reading the export and `python load.py` still work, and that the new hook was added without replacing others. Then remove only `protect-original-exports`; any other hooks stay. - [ ] GitHub: once, or twice if you have time, from a clean planner. Then restore the planner and its repository to the prepared state: close the rehearsal pull requests and branches, keep the backup pull request. ### 6. Check in with us - [ ] Send the [check-in form](https://tally.so/r/1WAkBl) by **Wednesday 21 October, 15:00 Mexico City (22:00 Lisbon)**: ready, or not ready on what. Preparation gets fixed before class, never by debugging in front of the room. ### "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 - **Remove everything the demos install.** The `project-status` skill, any connector the demo adds, and only the `protect-original-exports` hook: any other hooks stay. The room must see every step they will have to do. In lesson 2 a connector already installed on the teacher's laptop hid the sign-in step, and participants needed to see exactly that step. - Leave **one small uncommitted change** in the restock planner, so "what changed recently" shows something in the skill demo. **Discard it right after the skill demo**: the GitHub demo uses the same project and has to start clean, or the change shows up in the pull request. - The deck open on the first slide. The Meet window shared and the audio checked. - GitHub open and signed in, with the backup pull request in a tab. ### 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.