context-optimization

athola 的头像作者 athola

使用MECW原则(保持低于总窗口的50%)减少上下文使用。触发:上下文压力、令牌使用、MECW、上下文窗口、优化、分解、工作流程拆分、上下文管理、令牌优化。使用场景:上下文使用接近窗口的50%,需要分解的任务、计划复杂的多步操作、上下文压力高。不使用场景:上下文使用率低的简单单步任务。不使用场景:已经使用mcp-code-execution进行工具链。在开始复杂任务之前使用此技能。积极检查上下文级别。

📖 中文导读:使用MECW原则(保持低于总窗口的50%)减少上下文使用。触发:上下文压力、令牌使用、MECW、上下文窗口、优化、分解、工作流程拆分、上下文管理、令牌优化。使用场景:上下文使用接近窗口的50%,需要分解的任务、计划复杂的多步操作、上下文压力高。不使用场景:上下文使用率低的简单单步任务。不使用场景:已经使用mcp-code-execution进行工具链。在开始复杂任务之前使用此技能。积极检查上下文级别。 以下正文为该技能的原始 SKILL.md 内容(英文),上方安装命令可直接使用。

name: context-optimization description: |

Triggers: context, optimization Reduce context usage with MECW principles (keep under 50% of total window).

Triggers: context pressure, token usage, MECW, context window, optimization, decomposition, workflow splitting, context management, token optimization

Use when: context usage approaches 50% of window, tasks need decomposition, complex multi-step operations planned, context pressure is high

DO NOT use when: simple single-step tasks with low context usage. DO NOT use when: already using mcp-code-execution for tool chains.

Use this skill BEFORE starting complex tasks. Check context levels proactively. category: conservation token_budget: 150 progressive_loading: true

Claude Code 2.1.0+ lifecycle hooks

hooks: PreToolUse: - matcher: "Read" command: | echo "[skill:context-optimization] 📊 Context analysis started: $(date)" >> ${CLAUDE_CODE_TMPDIR:-/tmp}/skill-audit.log once: true PostToolUse: - matcher: "Bash" command: | # Track context analysis tools if echo "$CLAUDE_TOOL_INPUT" | grep -qE "(wc|tokei|cloc|context)"; then echo "[skill:context-optimization] Context measurement executed: $(date)" >> ${CLAUDE_CODE_TMPDIR:-/tmp}/skill-audit.log fi Stop: - command: | echo "[skill:context-optimization] === Optimization completed at $(date) ===" >> ${CLAUDE_CODE_TMPDIR:-/tmp}/skill-audit.log # Could export: context pressure events over time


Table of Contents

Context Optimization Hub

Quick Start

Basic Usage

# Analyze current context usage
python -m conserve.context_analyzer

When to Use

  • Threshold Alert: When context usage approaches 50% of the window.
  • Complex Tasks: For operations requiring multi-file analysis or long tool chains.

Core Hub Responsibilities

  1. Assess context pressure and MECW compliance.
  2. Route to appropriate specialized modules.
  3. Coordinate subagent-based workflows.
  4. Manage token budget allocation across modules.
  5. Synthesize results from modular execution.

Module Selection Strategy

def select_optimal_modules(context_situation, task_complexity):
    if context_situation == "CRITICAL":
        return ['mecw-assessment', 'subagent-coordination']
    elif task_complexity == 'high':
        return ['mecw-principles', 'subagent-coordination']
    else:
        return ['mecw-assessment']

Context Classification

Utilization Status Action
< 30% LOW Continue normally
30-50% MODERATE Monitor, apply principles
> 50% CRITICAL Immediate optimization required

Large Output Handling (Claude Code 2.1.2+)

Behavior Change: Large bash command and tool outputs are saved to disk instead of being truncated; file references are provided for access.

Impact on Context Optimization

Scenario Before 2.1.2 After 2.1.2
Large test output Truncated, partial data Full output via file reference
Verbose build logs Lost after 30K chars Complete, accessible on-demand
Context pressure Less from truncation Same - only loaded when read

Best Practices

  • Avoid pre-emptive reads: Large outputs are referenced, not automatically loaded into context.
  • Read selectively: Use head, tail, or grep on file references.
  • Leverage full data: Quality gates can access complete test results via files.
  • Monitor growth: File references are small, but reading the full files adds to context.

Integration Points

  • Token Conservation: Receives usage strategies, returns MECW-compliant optimizations.
  • CPU/GPU Performance: Aligns context optimization with resource constraints.
  • MCP Code Execution: Delegates complex patterns to specialized MCP modules.

Resources

  • MECW Theory: See modules/mecw-principles.md for core concepts and the 50% rule.
  • Context Analysis: See modules/mecw-assessment.md for risk identification.
  • Workflow Delegation: See modules/subagent-coordination.md for decomposition patterns.

Troubleshooting

Common Issues

If context usage remains high after optimization, check for large files that were read entirely rather than selectively. If MECW assessments fail, ensure that your environment provides accurate token count metadata. For permission errors when writing output logs to /tmp, verify that the project's temporary directory is writable.