META·SUITE ← all nine
overview / skills / meta-context
Skill 09 · keep axis

meta-context

A context strategy and a droppable-in memory scaffold — so work compounds across sessions instead of resetting.

SESSION → SESSION · MEMORY CARRIES session 1 session 2 session 3 MEMORY STORE grows every session ↗ WHAT'S HAPPENING 1 · A session ends — decisions, constraints, and dead ends included. 2 · A memory packet carries what matters into the next session. 3 · The store grows, so the next session starts informed — not cold. It keeps decisions, not transcripts — a droppable-in structure any session can read.
FIG — a memory packet carries forward; the store grows instead of resetting to zero
// what it does

Every new session usually starts from zero — you re-explain the project, the constraints, the decisions already made. meta-context designs the memory scaffold that carries what matters forward, so the next session starts where the last one ended.

It decides what's worth keeping, how to store it, and how to hand it back — a strategy plus a droppable-in structure, not a pile of transcripts. This is the skill that makes the other eight compound across time.

// the scaffold
what to keep

Decisions, constraints, and dead ends — not raw transcripts.

how to store it

A droppable-in structure that any session can read on entry.

how to hand it back

The rule for surfacing the right memory at the right moment.

// invoke it
/meta-suite:meta-context <the ongoing work that keeps resetting>

Returns a context strategy and a droppable-in memory scaffold — so the next session starts informed, and every skill above it compounds across time instead of starting over.

No cold starts

Pick up where you left off.

Droppable-in

A structure, not transcripts.

Keeps what matters

Decisions, not noise.

It compounds

The keystone of the nine.

Grounding

The ideas here aren't invented — the skill generalizes established practice into one reusable, task-agnostic move. Below: the prior art it builds on, and the in-repo contract it actually runs on.

Prior art
Context engineering — design what an agent knows, where it lives, and what loads when, so work stays grounded across sessions instead of starting cold.
Progressive disclosure — a small always-loaded core plus references pulled in only when a task needs them.
Plain-text source of truth — the CLAUDE.md convention — greppable, version-controlled memory that outlives any single tool.
In this suite
The four context policies references/policies.md — substrate · load · compression · persistence/handoff — plus the discoverability index that routes future work to them.