Claude Code · L4 · 1
Claude Code · ISTO.

Lesson 4 · Build your own way

Before we start

Today you build on your own project, your own way, then put it on GitHub.

1 · Add /coach
The help for when you're stuck. You add it.
2 · Build
Your project, your words. You do it.
3 · Share
Two or three screens, then what you learned. We talk.
4 · GitHub
A private copy, in three steps. You do it.
5 · What next
Other kinds of project you could build. We talk.

No set prompt for the build: you work it out, with /coach beside you.

If you don't know how to start

Four ways to start, or your own words: there's no right prompt.

·Where are we with this?
·What would make it useful to me this week?
·I'm waiting for [X]. What can we do meanwhile?
·What did we learn today?

Stuck? Ask /coach in a side chat first, then the meeting chat. No project yet? Start with /grill-me.

Add /coach · 5 min

Add /coach: help for when you're stuck.

/coach · stuck on what to do

Stuck on what to do: asking gets you Claude's ideas; /coach helps you find yours.

When a colleague or IT must fix it, /coach drafts the message: you read it, then send it.

/coach · add it
ActivityWatch first · 1 minYour turn · 3 minDemo project: restock-planner

Add /coach, then try it in a side chat.

1In the Code tab, any session: paste the download prompt and send.
2Start a new session: + New.
3Type /btw and a question: a side chat opens. There, type /coach and where you are.
A side chat
/btw opens it: it sees your session but doesn't change it. Ask, close it, carry on.

Download prompt · saves /coach in your skillsDownload 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

Build · 18 min

Build: your project, in your own words.

Build
ActivityYour turn · 18 minYour own project

Move your project forward: say what you want, check what Claude did.

1Open your project in the Code tab: the folder button shows its name. Then + New.
2Say what you want, or start from a line: Where are we with this? · What would make it useful to me this week? · I'm waiting for [X]. What can we do meanwhile?
3Read what Claude did. Not what you meant? Say so, in plain words.
Stuck?
Type /btw and your question; in the side chat, type /coach and what you see. Still stuck: the meeting chat.

At the end, you may be asked to share your screen: what you asked, and what Claude did.

Pocket: accesssubagents
Share · 12 min

Share: what did you ask, and what did Claude do?

Share and discuss
Two or three screens · 12 min

Share: what worked? what would you do differently?

You, sharingWhat did you ask? Did Claude do what you meant?
Where did it go somewhere you didn't mean, and what did you say?
The roomWho hit the same wall? What would you have asked differently?
Who else at your company would use this?

There's no right prompt: we learn from what happened in your sessions.

Pocket: accesscompany accesssubagents
Habit · Save what the session taught
ActivityYour turn · 3 min

End every session the same way: ask what it taught, and save it.

1In the same session, send: What did we learn today?
2Read its answer. Then: "Save what's worth keeping in my project's files." Approve what makes sense.
3What you save goes up to GitHub with your project, in a few minutes.

What did we learn today?What did we learn today?

Save what's worth keeping in my project's files.Save what's worth keeping in my project's files.

Quick? Add: "…and save this as a skill I can use at the end of every session."

GitHub · 15 min

Put your project on GitHub.

Why GitHub

A private copy on GitHub: one place a colleague can open, every push kept.

One copy to share
A colleague opens the same project, not a file you emailed.
Every push, with a note
"Added the stock column": each time you save and push, you can go back to that version.
Private, without secrets
Only people with access see it. You choose what goes up: passwords and real data stay on your computer.

Three short steps. For each: watch my screen, then do it on yours.

Pocket: access
GitHub · three steps
ActivityEach step: watch 1 min, your turn 3 minDemo project: restock-planner

Three steps, one at a time: watch each on my screen, then send it on yours.

1 · Is GitHub connected? Check you see: your GitHub username. Not set up: a browser window to sign in first.

Check GitHubIs 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 Check you see: a file list with the data folder and .env (the one file where keys may live, on your computer only) left out.

Create the repositoryCreate 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.

3 · Push it Check you see: open the link: the Private label, your files, no .env, no real data.

PushSave the project with a short note and push it to the repository. Then give me the link.

When Claude asks to run a command, read the one line, then Allow.

Pocket: access
Shapes of a project · 9 min

What shape can a project take?

Shapes of a project

Many shapes of project, one method: plan, build one phase, check.

Reports that make themselves
Daily sales by store, from Sage.
Stock against the production plan, weekly.
Tools your team uses
Expenses submitted and sorted.
One B2B client master file.
Drafts from your data
Shopify product pages from the product sheet.
Supplier emails from the purchase orders.
Checks and alerts
Shopify and Sage disagreeing on a product.
A style running low in one store.
Also, not a project
Your day-to-day work, run from the Code tab: a meeting pack prepared, the week's emails sorted, a supplier researched.

Which of these do you do by hand today? Which would you build next?

To keep

Trial and error, no one right way: push past the resistance and build.

/coach
When you're stuck, in every project on this computer.
The course group
Still open for questions after the course.
The course materials
Every lesson stays in the Academy, to go back to.

After class, two minutes in the Academy: the final questionnaire on the whole course.

Your turn to ask

Questions?

Annex

Pocket slides: extra slides, pulled only when a topic comes up.

Pocket slide · Subagents

Subagents are Claude's helpers: one session coordinates, each helper does one job.

Each helper works on one job only, so the two jobs don't get mixed up.

← back
Pocket slide · A connector's access

A connector sees only what your account sees: give it reading only, where you can.

Read, or also editSome connectors can change data. Start with reading only, because a wrong edit lands in the real system.
Your account's viewNo more than you could open yourself.
Passwords and keys only in .envThe project's keys file, kept off GitHub. Never in the chat, because it can be read or shared by mistake.
← back
Pocket slide · Access at company scale

At company scale, accounts and permissions decide who sees what.

Separate data by audience
Finance data where only finance accounts can open it, so a sales tool never reads it.
A shared database has an owner
One person decides what goes in and whose account can open what.
Accounts in the company's name
GitHub, and Vercel (where pages go online), belong to the company: it decides who gets in.

An account without access is a lock: the data is out of reach.

← back