Thirteen modules

Shape how
the model
behaves

Every tool in Claude Code is a different lever on that. One module per lever, and each one ends with something running in your own project the same day.

Start at module 00 See all thirteen

On-ramp Use it, and meet the problems.

  1. 00 Install it and ask it something Start Claude Code inside a project you already have. 15 min
  2. 01 Let it change something Hand Claude Code a small task. 20 min
  3. 02 Why it forgot what you told it You can explain why an instruction you write gets weighed instead of obeyed. 15 min

The levers Each one works on its own.

  1. 03 Rules You can predict which instruction files load. 20 min
  2. 04 Your first command Ship a working slash command from a single file. 25 min
  3. 05 Skills Promote your command into a skill directory. 35 min
  4. 06 Settings and themes Write a custom theme, and predict which settings file wins when two of them disagree. 30 min
  5. 07 Shaping the model Say where any instruction you write ends up. 30 min
  6. 08 Subagents Write a subagent and state exactly what it inherits from the session that spawned it. 40 min
  7. 09 Hooks Write a hook that actually blocks. 50 min
  8. 10 MCP Add an MCP server to a project. 35 min
  9. 11 Permissions and the sandbox State why a hook is not a security boundary. 40 min

Packaging Only if you hand your work on.

  1. 12 Build the plugin Assemble the eight directories you already wrote into one installable plugin. 45 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.

Rule two

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

Two modules ship nothing

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