Appearance
Data and Control Flow
How the parts move together at runtime. Three flows touch most of the kit: the session lifecycle the hooks hang off, the lesson lifecycle the learning layer runs, and the install flow that puts any of it into a project.
Session Lifecycle
The hooks pack fires at Claude Code's lifecycle events. Observers inject context and never block, gates guard edits and Bash and mostly fail open, and the compact and end hooks preserve and learn from the session.
Lesson Lifecycle
A correction is captured once, routed to a domain, and resurfaced automatically the next time you touch that domain. Each lesson earns its keep through hits and expires on a schedule.
Install and Update
The installer copies the parts you pick into a target project's .claude/, records what landed in a global registry, and later tells you which installs have drifted from the current harness.
Catching an Installed Project Up
An update refreshes the files a part already put in a project. It cannot help when the change is to the shape of the part itself, because a project holding an older copy has no way to hear that the module was renamed, or that it now requires a part that did not exist when it was installed. That gap is what the migration table closes: one row per change that needs something doing to the copies already out there.
The split below is a safety rule rather than a category. A rename is a pure record rewrite, so it can be applied on every registry read and a project untouched for a month reads correctly the first time it is opened. Everything that writes, moves or deletes is held back and surfaced, because a read happens in every view, and a view that quietly changes a project on disk is not something you could reason about.