thalarch-contextlisted
Install: claude install-skill LUC4N3X/antigravity-thalarch
# Thalarch Context Hygiene
Context quality is an engineering control. Too little context encourages invention; too much stale
or irrelevant context makes important evidence hard to distinguish from noise.
The goal is the **smallest fresh packet that can support the next decision**.
## 1. Context hierarchy
Load in this order and only as needed:
1. user/system/repository rules and explicit scope;
2. acceptance/spec/architecture material relevant to the task;
3. exact source/interfaces/tests near the changed behavior;
4. current Git/build/runtime/error evidence;
5. external primary documentation for version-sensitive gaps;
6. compact retrieved project/general memory that remains relevant after freshness checks;
7. other prior-session decisions only when still verified.
Conversation history and durable memory are not stronger than current repository/runtime evidence.
## 2. Pre-task packet
For meaningful work create a compact packet containing:
- `TASK` — one-sentence outcome;
- `SCOPE` — paths/components allowed and excluded;
- `STACK` — proven language/framework/toolchain versions relevant now;
- `RULES` — applicable repository/user constraints;
- `TARGETS` — exact files/interfaces likely involved;
- `PATTERN` — one nearby working analogue when available;
- `TESTS` — closest existing tests and real commands;
- `EVIDENCE` — current failure/log/diff facts;
- `MEMORY` — only revalidated or explicitly marked unverified memory relevant to this decision;
- `UNKNOWNS` — facts