kernel

Recording architectural decisions. Why we chose X over Y.

How to craft a Sub-Agent persona.

Crafting blueprints. Persistent task tracking with user confirmation.

How to craft a Slash Command trigger.

What a comment is for, what shape it takes, and the space around code that means no comment is needed. Applies to any language, not only shell.

Show what happens next, in what stages, and where it branches. Use for a process, a lifecycle, a state change nobody owns. Not for static structure (craft-map) or who acts at each step (craft-swimlane).

Create a handoff document. Preserves state across sessions.

How to create a new Reflex (Hook) for the OS.

Show what exists, where it lives, and what each part is for. Use for a directory tree, a codebase layout, a component hierarchy. Not for sequence (craft-flow) or who acts (craft-swimlane).

Crafting effective CLAUDE.md files. Project memory that Claude won't ignore.

Record a learning or discovery. Compounds knowledge across sessions.

The Architecture of the Cognitive OS.

Release a plugin version. Bump plugin.json, then commit.

Opening a pull request on top of one that has not merged. When a stack earns its merge order, how to rebase a child, and where the child lands when the parent merges.

How to craft a README. Direct, minimal, clear.

Binding one repository to one GitHub account when a machine holds several. Which identity signs a commit, which token pushes it, and why the CLI's account is global when everything else is per repo.

Activates ruthless critic mentality. Use when evaluating code quality.

Proposing technical designs. How we should build X.

Crafting a shell script that reads like prose. One story in main, one job per function, early returns, and the ways a shell lies to you.

How to craft an atomic skill. Includes templates and registration.

Draw who or what acts at each step, and what crosses between them. Use when a hand-off, an approval, a human touchpoint or an adapter seam is the point. Not for static structure (craft-map), ownerless process (craft-flow), or a call and return trace.

Testing philosophy. Confidence, not coverage. What to test, what to skip.

When a test earns its line, and when to cut it. Removal is the test of a test.

How to verify the Cognitive OS is functioning correctly.

Internalize all ground-* philosophy skills.

Context budget management. Solves context exhaustion.

Strategic delegation. When to lead, delegate, or collaborate.

Research before implementation. Reading before writing.

Sensing resistance. The "push back" instinct when code feels forced.

Spec refinement via AskUserQuestion. Extract requirements before implementation.

Code or model. What must be deterministic, and what must be judged.

Naming patterns. "Specific is better than generic."

Context loading. Solves cold start.

Anchor yourself. Prevent context drift.

Ground the right stack philosophy for the current technology context.

Isolate yourself. One branch, one memory.

Deep code polish. Seven-pass readability protocol. Use when code works but doesn't sing.

Interrogate an ask before acting on it. What was asked, why, is it still right, and where does it fit. Use at the start of any piece of work, and again whenever the ask is restated.

Find what went wrong before somebody else does. Run it when work ends, when a check goes red, and when a person catches what you missed.