context-optimizelisted

# Context Optimize Improve the current project's Claude Code context system based on evidence. The goal is not to make `.claude` prettier; the goal is to reduce unnecessary context and repeated discovery while preserving or improving task quality. Do not modify application code, dependencies, product behavior, or business data. Do not commit or push changes. ## Optimization objective Minimize expected context/token cost and rediscovery effort subject to these constraints: 1. Project-specific correctness must not regress. 2. Critical instructions must remain available at the time they are needed. 3. Maintenance complexity and staleness risk must not increase without evidence of a compensating benefit. 4. Changes should be measurable and reversible. A lower token number is not automatically an improvement if Claude then has to reread the repository or makes more mistakes. ## 1. Load the existing control plane Inspect: - the applicable `CLAUDE.md` hierarchy - `.claude/rules/**` - `.claude/skills/**` - `.claude/agents/**` - `.claude/settings*.json` - `.claude/hooks/**` - `.claude/context-system/**` - relevant nested Claude configuration in child repositories/subprojects - Git history/diff for Claude configuration since the last optimization, when available If `.claude/context-system/` does not exist, reconstruct a minimal state/snapshot layer before optimizing. Do not require rerunning the bootstrap skill. Read previous `optimization-log.jsonl` experiments first. Evalu