Who this course is for
For teams already using Claude Code who keep hitting the same wall: work that only makes sense while one person remembers the conversation behind it. Three core modules teach the method on Tool Scout, a fictional product-team scenario adapted from a worked comparison of five AI app builders, mistakes included. A closing test tells you if it worked, run against your own project, not this one.
Completing the course means Core 1 through 3, plus the takeover test below. Specialists are optional. Finish the core and you're done. The specialists just take the same project further.
What context engineering for Claude Code means
Context engineering for Claude Code is the practice of putting everything Claude needs into files it reads on every session: the brief, the project instructions, the decisions already made and the state of the work. Prompting shapes one answer. Context engineering shapes every answer, for every person on the team, without the conversation that produced it.
Plenty of courses hand over Claude Code instructions and stop there. This one shows the instructions actually being followed (one project, adapted examples, the mistakes included) because the instructions are not the hard part. Keeping the work legible once the conversation ends is.
Every piece the course teaches answers the same question a different way. Where does this stand? Read the file names. What got decided, and why? Read lessons.md. How do two people work without blocking each other? A worktree per feature. None of it is a feature to learn for its own sake. It exists because a team loses sight of its own work the moment the person holding the context is unavailable.
The work has to live in the repo, not in the person.
The Operating Brain makes the same argument at company scale, past what one repo can hold.
Can your teammate take over tomorrow?
This is the course's closing test, and it runs on your own project, not ours. Open your project's files (not your memory of the last conversation about them) and tick a statement only if the files themselves answer it.
The takeover test
- GoalA teammate can find the goal (what we're building and why) in the files alone.
- Approved decisionsA teammate can find which decisions were approved, and which were rejected, in the files alone.
- Current stateA teammate can tell exactly where the build stands right now, in the files alone.
- Next actionA teammate can tell what to do next, in the files alone, without asking you.
