gems
Installation
SKILL.md
Gems: keep the 2% of context that matters
Most of a long session is noise: file dumps, tool output, abandoned drafts. A small part
is gold: what we are building, the rules we must not break, what we decided and why,
what already failed, where we are right now. This skill keeps that gold in one short file,
.gemkeeper/ledger.md at the project root, while the session is still sharp, so the
user can /clear a bloated session at any moment and continue at full quality.
The ledger is written for the next instance of you, not for the human. Be dense, exact, and literal.
The ledger test
Before writing anything, ask: "Would a fresh session with only the code and this ledger get this wrong or waste time on it?"
- Yes → it is a gem. Write it.
- No (it's in the code, in git history, in CLAUDE.md, or easy to rediscover) → leave it out.
Gems, typically: