Context Management
Use this skill when editing always-loaded files, deciding where durable knowledge
belongs, diagnosing context bloat, or preserving continuity across compaction.
For new substantive work or materially changed scope, follow the native
WORK-CONTEXT.md contract when present; this skill points to that contract but
does not own work-placement policy.
Contract
The workflow is complete only when:
- the request is classified into one context lane
- only the relevant files are loaded
- durable knowledge is routed to the right store
- always-loaded files stay compact and role-pure
- touched files are re-read or linted after edits
Context lanes
| Lane |
Use when |
Output |
| Bootstrap hygiene |
Root instruction files are too large, stale, or mixed-purpose |
Smaller root files with pointers to deeper docs/skills |
| Memory routing |
A fact, preference, lesson, decision, or project state needs a home |
Correct durable memory/document location |
| Conversation continuity |
Compaction, transcript recovery, or session handoff is the problem |
Recovery summary and source-of-truth refresh |
| Monitoring/maintenance |
Watchdogs, context budgets, or trend reports show drift |
Diagnosis, targeted cleanup, and verification |
Routing rules
- Facts and preferences go to the durable memory surface.
- Decisions with tradeoffs go to decision records.
- Lessons from mistakes go to lessons.
- Project state goes to project state or the tracker.
- Operational procedures become skills or docs, with a short pointer from the
always-loaded file.
- Brain-native objects such as people, companies, concepts, beliefs, and goals
belong in the workspace's chosen structured knowledge layer.
Always-loaded file hygiene
Keep root instructions short. They should contain durable rules, routing
pointers, and triggers. Move long procedures to skills, references, or docs.
Before deleting content, diagnose why it is no longer needed. Watchdog output is
evidence, not an automatic pruning command.
Verification
After editing:
- Re-read the touched file or run the relevant lint/check.
- Confirm the file still has one clear job.
- Confirm any moved content has a pointer from the original surface if users or
agents need to find it.
1---2name: context-management3description: Context Management4---56# Context Management78Use this skill when editing always-loaded files, deciding where durable knowledge9belongs, diagnosing context bloat, or preserving continuity across compaction.1011For new substantive work or materially changed scope, follow the native12`WORK-CONTEXT.md` contract when present; this skill points to that contract but13does not own work-placement policy.1415## Contract1617The workflow is complete only when:1819- the request is classified into one context lane20- only the relevant files are loaded21- durable knowledge is routed to the right store22- always-loaded files stay compact and role-pure23- touched files are re-read or linted after edits2425## Context lanes2627| Lane | Use when | Output |28|---|---|---|29| Bootstrap hygiene | Root instruction files are too large, stale, or mixed-purpose | Smaller root files with pointers to deeper docs/skills |30| Memory routing | A fact, preference, lesson, decision, or project state needs a home | Correct durable memory/document location |31| Conversation continuity | Compaction, transcript recovery, or session handoff is the problem | Recovery summary and source-of-truth refresh |32| Monitoring/maintenance | Watchdogs, context budgets, or trend reports show drift | Diagnosis, targeted cleanup, and verification |3334## Routing rules3536- Facts and preferences go to the durable memory surface.37- Decisions with tradeoffs go to decision records.38- Lessons from mistakes go to lessons.39- Project state goes to project state or the tracker.40- Operational procedures become skills or docs, with a short pointer from the41 always-loaded file.42- Brain-native objects such as people, companies, concepts, beliefs, and goals43 belong in the workspace's chosen structured knowledge layer.4445## Always-loaded file hygiene4647Keep root instructions short. They should contain durable rules, routing48pointers, and triggers. Move long procedures to skills, references, or docs.4950Before deleting content, diagnose why it is no longer needed. Watchdog output is51evidence, not an automatic pruning command.5253## Verification5455After editing:56571. Re-read the touched file or run the relevant lint/check.582. Confirm the file still has one clear job.593. Confirm any moved content has a pointer from the original surface if users or60 agents need to find it.
levineam