One installable directory that bundles skills, hooks, subagents, MCP servers and settings. The layout, the one directory mistake everyone makes, what a plugin change costs your cache, and how marketplaces distribute them.
Continue reading »Claude-Code
23 posts in this section
Hooks
The layer that turns an instruction into a guarantee. Where each event fires in a turn, which ones can block, the exit-code contract, and the asymmetry that lets a hook tighten your permissions but never loosen them.
Continue reading »Skills
The extension point built around not being in context until it is needed. Progressive disclosure, the four ways a skill can be invoked, single-turn tool grants, and what running one in a subagent costs you.
Continue reading »Output Styles
The one extension point that edits the system prompt itself. Five built-in styles, the single frontmatter field that decides whether Claude still behaves like an engineer, and how output styles differ from the four mechanisms they get confused with.
Continue reading »Sessions, Checkpoints & Rewind
A session is a JSONL file you can resume, branch and rewind. What each of those restores, what a resumed session quietly forgets, and the four categories of change that rewind cannot undo.
Continue reading »The Context Window
The budget every other chapter spends. What is already in the window before you type, what each file read costs, what compaction keeps and drops, and why the prompt cache makes a mid-task model switch more expensive than it looks.
Continue reading »Rules & Auto Memory
Two ways instructions persist without you retyping them: rules you scope to file paths so they cost nothing until they are relevant, and the notes Claude writes for itself between sessions.
Continue reading »CLAUDE.md
The file that stops you re-explaining your project every session. Where it can live, how several of them combine, why it is context rather than configuration, and the test for whether an instruction belongs in it at all.
Continue reading »Settings: the Control Panel
Four settings files, one precedence stack, and the handful of keys that break the stack's rules. Where each file reaches, why some keys merge instead of overriding, and how to find out which file is beating yours.
Continue reading »Permissions & Sandboxing
Rules decide whether a tool call happens; the sandbox decides what it can touch once it does. Rule syntax and the wildcard placement that widens a rule further than intended, path anchoring, working directories, and where the OS boundary goes.
Continue reading »








