The Toolkit
One template per module. Blank starting points for each layer of the operating system. Grab what you need; the full teaching lives in the modules.
Where you are on the maturity ladder, where you're going, and the cost of staying.
Friction encoded as a binding rule that fires before every response.
Every place real data about your business lives, with AI access state per source.
Your tone, your banned phrases, your required moves, your sentence rhythm.
A named persona for a specific job. Inherits your voice, adds mode-specific rules.
The four-beat cadence — daily, weekly, monthly, quarterly — that keeps the system alive.
Starter CLAUDE.md
The entry-point file that loads on every Claude Code session. Points the AI at every artifact you build across the program. Drop this in ~/.claude/CLAUDE.md or your project root and edit as your library grows.
How to use the toolkit
Each template is a blank version of the artifact a module produces. Use them to bootstrap your own files without going through the full module exercise. The teaching still lives in the module — the template only gives you the shape.
Save the downloaded files in one place — a memory directory inside your AI tool of choice. For Claude Code, the convention is ~/.claude/projects/<your-project>/memory/. For ChatGPT, paste the contents into Custom Instructions or use the Memory feature. For other tools, find the equivalent "always loaded" field.
Then point your CLAUDE.md or equivalent at the directory so the files load before every response. The bonus starter is a working example.