How this works · Before you ship
4 min read
How this works · read once

How to read
this book.

For the impatient
The structure, the rhythm, and the one commitment that turns the kit into actual shipped code.
★ The ratio this whole course runs on

Spend 60% planning, 30% executing, 10% reviewing.

60%Plan
30%Execute
10%Review

Most solo bugs are planning failures. Claude Code makes the planning step nearly free, but only if you actually do it.

§ 01 · The arc

Five parts. One escalator.

Foundations and Setup come first because the workflow modules in Part 02 assume them. Skipping Setup means rebuilding it on the fly mid-feature, which is where most solo Claude Code adoption stalls. Read in order the first time. Jump around the second.

Part 00
Foundations

Why solo is different, plan-first discipline, which Claude tool fits which job.

3 mods · ~16 min
Part 01
Setup

CLAUDE.md, slash commands, subagents, MCP. The 30-minute ritual.

4 mods · ~24 min
Part 02
The Solo Workflow

Prototype, refactor, debug, test, commit, run in parallel. The day-in-the-life that ships.

6 mods · ~37 min
Part 03
Production

Limits and model choice, hooks, knowing when to take over.

3 mods · ~19 min
Finale
First 30 Days

Week-by-week plan, plus the transition to a small team.

2 mods · ~12 min
§ 02 · Module anatomy

Every module has the same shape.

Once you learn to read one module, you've learned to read all eighteen. Here's what each recurring block means.

§
Anchor

Anchor

Section header. Signals a shift in argument. Don't skim past it.

★
Key idea

Key idea

Orange poster. The one thing to remember from the module. Take a screenshot if nothing else.

P
Pro tip

Patrick's pro tip

What actually works in production, not what's theoretically right.

✦
Try it

Try it now

A concrete task. In setup modules this means actually wiring the file. Skip these and the kit is theoretical.

↺
Recap

Recap

Four bullets distilling the module. Read first if time-poor; come back to body later.

⌘
File

Templates & snippets

The file or snippet that ships with the module. Copy, fork, drop in your repo.

§ 03 · Getting around

Your progress is saved. Close the tab whenever.

The modules you've read and the try-it boxes you've ticked are saved in this browser. Come back next week and pick up where you left off.

Keyboard shortcuts

Turn pages without the mouse.

←→page
✦ The one commitment

Install the kit. Use it Monday.

The kit only earns its keep when it's in your repo. Every module ends with a "Try it now" block. The setup modules end with file installs. If you skip these, this is just reading. If you do them, you finish the course with a working ritual, not a notes doc. That's the deal.

Claude Code for Solo Builders · How this works02