Lesson 4 · Build your own way
Worksheet

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.

Stuck? The first help

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.

1

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.

  1. In the Code tab, any session: paste the Download prompt and send.
Download prompt
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
  1. Claude says /coach is installed. It may name it coach or coach-at-work: either works as /coach.
Done whenClaude says /coach is installed.
2

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:

a · Where are we? · 3 minutes

Ask where your project stands, then let threads make mockups of what's left.

  1. + New, and check the folder button shows your project. This session is your orchestrator.
  2. Paste Prompt 1 and send.
Prompt 1
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.
  1. 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.

  1. In the sidebar, click a thread under your orchestrator. Paste Prompt 2, or open the mockup's HTML file yourself.
Prompt 2
Open the mockup for me.
  1. Not what you need? Say what to change, in your own words.
  2. 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.

  1. Back in your orchestrator session, paste Prompt 3.
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.
  1. Read its plan. Something you'd do differently? Say so.
  2. Agree? Send the line below.
Go ahead
Go ahead: split it into the threads you think best.
Your own words work too
No project yetStart with /grill-me instead of the three activities

Where you see [ ], type your own words instead.

  1. In the Code tab, open your projects folder and send: Create a folder called [project-name] here.
  2. Open that new folder with the folder button, then + New.
  3. Switch the mode to Plan, then send: /grill-me I want to build [your project in one sentence], for [who uses it].
  4. Answer until Grill Me writes the plan.
  5. 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).

3

Share, then save what the session taught

3 · Share · 10 minutes · then Habit · Save what the session taught · 3 minutes

  1. In your orchestrator session, paste What did we learn today? and send.
What did we learn today?
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.
  1. 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."

4

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?

Check GitHub
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.
Check you seeYour GitHub username. Not set up: a browser window to sign in first.

2 · Create a private repository

Create the 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.
Check you seeA file list with the data folder and .env (the one file where keys may live, on your computer only) left out.
Claude says a key or a real export is already in the project's saved history? Don't push. Tell the course group (in class: the meeting chat).

3 · Push it

Push
Save the project with a short note and push it to the repository. Then give me the link.
Check you seeOpen the link: the Private label, your files, no .env, no real data.

Now it's on GitHub

Share it, build it together, open it from any computer.

Real data and keys stay on each computer: a colleague adds their own.

?

If you're stuck

The first help

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.