Three tracks

Shape how
the model
behaves

Claude Code gives you a dozen levers on model behavior. This course takes them one at a time. Each module ends with something running in your own project that day.

Start at module 00 See every module

A row of machined levers on a shared rail, each pressing at a different angle against one continuous sheet of paper.

Build the Chat Plugin One reader, no coding background, ends with a multi-agent chat app that is also a Claude Code plugin.

  1. 26 Start Here: Run the App You Will Build You can open a terminal. 50 min
  2. 27 What an Agent Is You can say what a model. 45 min
  3. 28 What a Plugin Is You can open a plugin folder. 45 min
  4. 29 One Agent That Stays Alive You can keep one agent's session alive across many messages. 55 min
  5. 30 The App's Claude Is Not Your Claude You can run the app on a machine full of personal hooks. 50 min
  6. 31 A Roster of Agents You can add an agent from the sidebar. 55 min
  7. 32 Agents That Message Each Other, in Turn You can let one agent send a message to another while the other is busy. 55 min
  8. 33 Caps That Only a Person Resets You can let two agents talk. 50 min
  9. 34 The Wiki, by Hand You can build a knowledge base that an agent maintains. 90 min
  10. 35 Skills That Keep the Wiki Honest You can give the agents a capture skill that routes a new fact to the right page. 50 min
  11. 36 Each Agent Keeps Its Own Notes You can hand two agents the same wiki. 55 min
  12. 37 Keep the Main Window Small You can add a reader agent that reads the whole record. 45 min
  13. 38 Hooks That Keep Agents Inside the Lines You can write a hook that puts an unanswered question in front of the agent at the exact prompt that touches it. 45 min
  14. 39 Approval as Data, Reach as Its Own Axis You can state the approval policy as one list. 45 min
  15. 40 Ship the Plugin You can run `claude --plugin-dir .` in a plain terminal. 45 min
  16. 41 The Whole App, Top to Bottom You can stand the whole application up with one command. 40 min
Rule one

Smallest artifact first. A rule is one line of markdown. A theme is {}. Each module starts at that minimum, runs it, then adds one field at a time.

Rule two

One new idea per module. Themes come before hooks because a wrong colour is a gentler place to learn precedence than a blocked tool call.

Two modules ship nothing

Rules and permissions ship nothing you can hand to a teammate. Capabilities are distributable. Guidance and policy are not.