mkcontext-engineeringlisted

# mk:context-engineering — Runtime Context Router Decide the next context move for the task in front of you: read more, stop, ask, assume, or delegate — then load at most one pattern reference to execute it. This skill routes decisions; it does not preload a knowledge library. **Boundary vs `mk:context-audit`:** that skill audits *structural* `.claude/` overhead (what is statically loaded every session). This skill decides *runtime* context moves for one task. Structural question → context-audit. Runtime question → here. If a request is ambiguous between the two (e.g. "this project's context is messy"), ask ONE question — structural `.claude/` setup or this session's runtime context? — then route. ## When to Use - Context is near its working ceiling and phases remain — decide what to keep. - A long session is drifting or output quality is slipping. - You must choose the minimal read-set before a task (Plan/Build/Review). - You are choosing between `/compact`, `/clear`, and spawning a sub-agent. - A known pattern applies (lost-in-middle, RAG dump, few-shot drift) and you want the routing. ## When NOT to Use - Auditing `.claude/` token overhead → `mk:context-audit`. - Persisting a learning or reading memory topic files → `mk:memory`. - Finding *where* code lives → `mk:scout` (or `Read` for one known file). - USD run cost → `mk:budget`. - A trivial 1–2 file task — no routing needed; just do it. ## Four Operations The whole surface reduces to four moves. Name the one you