Claude Code, as a checklist.
Six runbooks that take you from nothing installed to a thing you can open on your phone. Every step has the prompt to paste and the result to expect. No code to understand. No video to sit through.
Ask your first question.
Type this and press Enter. Watch what it does before it answers: it looks at the folder first. It always looks before it talks.
What is in this folder, and what are three small things we could build here? Keep it short.
Six runbooks, in the order to run them.
- 01Install Claude Code and say hello.Claude Code running in a folder on your computer, answering a question about that folder.Setup · 10 min
- 02Give Claude a brief it will keep reading.A file called
CLAUDE.mdin your folder. Claude reads it every time it starts, so it stops asking the same questions.Setup · 12 min - 03Build the smallest version that works.Something you can open and try today. Small on purpose: the first version exists to be wrong in useful ways.Build · 25 min
- 04Turn a messy folder into a tidy one.Your downloads, notes, or photos sorted into folders you chose, with a written log of every move.Everyday · 15 min
- 05Make Claude prove its own work.A rule in your brief that ends every change with a check you can see. Fewer “it should work now” moments.Habit · 8 min
- 06Put it on a link you can open on your phone.Your small build at a public address. Sent to one friend. That is a shipped thing.Ship · 20 min
Read the line. Do the line. Check the result.
The format pilots use for a reason: when you are new, you should not have to think about what to do next. You should only have to do it.
One instruction, in plain words.
Four sentences at most. What to do and why it matters, nothing about how Claude works inside.
The exact text to paste.
A terminal command or a prompt, with the parts you change marked in terracotta. Copy with one tap.
What you should see before moving on.
If you do not see it, stop. The runbook is wrong, not you, and it gets fixed when you reply.
One link. Then five short emails, one a day.
Each one is under two hundred words and points at one runbook. The last one tells you about the paid vault and the price, once. Leave at any point in one tap.
- Day 0Your Starter Vault is ready.The link, and which runbook to open first.
- Day 1The one habitAsk for the plan, not the code.
- Day 2Why it ignored youBriefs, and the three lines that fix most of it.
- Day 3A real build, 25 minutesRunbook 03, with a worked example.
- Day 4What people ask mostThe five questions, answered short.
- Day 5The Full VaultWhat is in it, who it is for, the price.
Forty more, and eight walkthroughs on screen.
The Full Vault is built from the questions people actually send. One payment of $97. It opens when you are ready for it, not before.