salience-splitter

# salience-splitter — Governance-Semantic Context Split > **Renamed from `skill-splitter` (2026-07-05).** Old-name references still route here. The rename reflects > the generalized scope: the split criterion applies to **any always-loaded context asset** — a SKILL.md, > a CLAUDE.md, or a memory index — not only skills. The label now names the substance (salience-tiering of > always-loaded context), not one instance of it. Dogfood: applied to a memory index 2026-07-05. > An always-loaded asset that holds everything in one layer is not simple — it is unscoped. > The goal is a lean always-loaded layer + an on-demand layer, not one file and its appendix. **Scope (all three share one criterion — salience: what must be in attention every load):** - **SKILL.md** → always-loaded SKILL.md + on-demand `SKILL_detail.md` - **CLAUDE.md** → lean rules + on-demand detail docs (imperative `> **Detail**: See …` pointers) - **memory index** → hot `MEMORY.md` + on-demand `MEMORY_archive.md` (cold/closed/superseded entries) ## Trigger Phrases | Phrase | Situation | |---|---| | "this skill is getting too long", "trim the skill", "split this SKILL.md" | Direct split request | | "context-doctor flagged this skill", "SKILL.md is bloated" | Post-diagnosis split | | "I can't see the key parts", "too much detail in the skill file" | Readability problem | | "separate the bash from the logic", "move the templates out" | Structural refactor request | | `/salience-splitter` | Explicit invocation | -...