Lesson 4 worksheet
The class's activities in order, each with its prompt: add /coach, build on your project, save what you learned, then put your project on GitHub. Everything runs in the Claude app's Code tab: copy a prompt with its button, paste it in your Claude session, send.
Select a few words of Claude's answer, then Start a side chat. There, type /coach and what you see. It gives you a hint or the next step. Still stuck: the meeting chat in class, the course group after it.
No /coach yet? You add it in 1 · Add /coach, below.
Add /coach
1 · Add /coach · 3 minutes · any project
/coach is a skill for when you're stuck: hints before answers, plain words, one safe step. It stays in your personal skills and works in every project. When a colleague or IT must fix something, it drafts the message: you read it, then send it.
- In the Code tab, any session: paste the Download prompt and send.
Download this skill and install it for all my projects, without changing a word: https://adapttoai-walkthrough-assets.pages.dev/skills/coach-at-work/SKILL.md
- Claude says
/coachis installed. It may name itcoachorcoach-at-work: either works as/coach.
/coach is installed.- Claude says it can't download the file: open the link in your browser and copy all the text. In Claude, send
Save this text exactly as .claude/skills/coach/SKILL.md inside my home folderand paste the text with it. coachnot found: type/reload-skills. Still missing: quit the app completely and open it again. Mac: Cmd + Q. Windows: open Task Manager (Ctrl + Shift + Esc) and end the Claude process.
Build: your project, in your own words
2 · Build · 20 minutes · your own project
Three activities: ask where your project stands, check a mockup of each part, then let Claude split the build. Two words for it:
- Orchestrator session: the session you talk to; it hands out the jobs and gathers the results.
- Thread: a session the orchestrator opens for one job; it shows under it in the sidebar and reports back when done.
a · Where are we? · 3 minutes
Ask where your project stands, then let threads make mockups of what's left.
- + New, and check the folder button shows your project. This session is your orchestrator.
- Paste Prompt 1 and send.
Read PLAN.md and tell me in a few lines where we are: what's built, what's left and what's still blocking us. Then open a thread for each part we haven't started, to make its mockup as an HTML page with invented data. Don't build anything.
- Read where you are. The threads appear in the sidebar: let them work.
b · Check the mockups · 6 minutes
Check each mockup in its thread: change it until it's what you need.
- In the sidebar, click a thread under your orchestrator. Paste Prompt 2, or open the mockup's HTML file yourself.
Open the mockup for me.
- Not what you need? Say what to change, in your own words.
- Next thread only when you can say: yes, that's it.
Claude will build what the mockup shows: what you change now, it won't have to redo.
c · The build plan · 8 minutes
Ask the orchestrator how to build the rest, then let it split the work into threads.
- Back in your orchestrator session, paste Prompt 3.
I've checked the mockups. How would you build the rest of PLAN.md: which parts can be built at the same time, which together, and in what order? For each blocker, suggest a way to keep going meanwhile. Tell me in a few lines, then wait for me.
- Read its plan. Something you'd do differently? Say so.
- Agree? Send the line below.
Go ahead: split it into the threads you think best.
- Where are we with this?
- What would make it useful to me this week?
- I'm waiting for [X]. What can we do meanwhile?Type it with your X
No project yetStart with /grill-me instead of the three activities
Where you see [ ], type your own words instead.
- In the Code tab, open your projects folder and send:
Create a folder called [project-name] here. - Open that new folder with the folder button, then + New.
- Switch the mode to Plan, then send:
/grill-me I want to build [your project in one sentence], for [who uses it]. - Answer until Grill Me writes the plan.
- Switch Plan off, then send:
Save the plan as PLAN.md in the project folder. Don't build anything yet.
Never installed Grill Me? First the Before Lesson 2 lesson "Add your first skill: Grill Me" (about 5 minutes).
Share, then save what the session taught
3 · Share · 10 minutes · then Habit · Save what the session taught · 3 minutes
- In your orchestrator session, paste What did we learn today? and send.
Before we stop: what did this session teach that's worth keeping? Think about the project, how we worked together, and anything that blocked us. Suggest specific updates to CLAUDE.md or a new skill, and tell me before changing anything.
- Read what it suggests keeping. Approve what makes sense; say no to the rest.
Quick? Add: "…and save this as a skill I can use at the end of every session."
Put your project on GitHub
4 · GitHub · three steps, about 3 minutes each · your own project
A private copy on GitHub: one place a colleague can open, every push kept. Only people with access see it. You choose what goes up: passwords and real data stay on your computer.
Only what you push is kept: push again after each change you want saved.
Three steps, one at a time, in your project's session. When Claude asks to run a command, read the one line, then Allow.
Your project is already on GitHub? Do step 1, then skip to step 3: the push sends today's changes.
1 · Is GitHub connected?
Is git set up on this computer, and am I signed in to GitHub? Tell me which account. If something is missing, set it up with me one step at a time and tell me what to click.
2 · Create a private repository
Create a private GitHub repository for this project. Before anything goes up, show me which files you'd include, and leave out real data, exports and any file with passwords or keys.
.env (the one file where keys may live, on your computer only) left out.3 · Push it
Save the project with a short note and push it to the repository. Then give me the link.
.env, no real data.- It says Public: send
Make this repository private now. - The wrong GitHub account: send
Switch to [my username].with your own username in place of [my username]. A clash between personal and work accounts: tell the course group (in class: the meeting chat).
Now it's on GitHub
Share it, build it together, open it from any computer.
- Share it with teammates: invite a colleague to the repository: they open the same project, not a copy you emailed.
- Work on it together, in order: pull their changes before you start, push yours with a note: everyone builds on the latest version.
- Open it from another computer: it's in the cloud: sign in to GitHub on a new laptop and ask Claude to bring the project down.
Real data and keys stay on each computer: a colleague adds their own.
If you're stuck
Select a few words of Claude's answer, then Start a side chat; there, type /coach and what you see. Still stuck: the meeting chat in class, the course group after it.
- A side chat can't open files. If
/coachneeds to look at one, type/coachin your session instead. - A colleague or IT must fix it (an account, access to data):
/coachdrafts the message. You read it, then send it. - No time to finish in class: this page stays here; finish after the lesson.