← ClaudeAtlas

budget-zoneslisted

This skill should be used when the context window is filling up, when deciding whether to read a file or use grep, when planning work scope, when the user asks about "budget zones", "context budget", or "token management", or when you notice the conversation is getting long.
silvesterdivas/context-engineer · ★ 0 · AI & Automation · score 75
Install: claude install-skill silvesterdivas/context-engineer
# Context Budget Zones Apply these budget zones to manage context consumption throughout the conversation. ## Zone Definitions ### GREEN Zone (< 60% context used) - **Behavior:** Work normally. Full creative freedom. - Read entire files when helpful - Explore the codebase broadly - Include full code blocks in responses - Use multiple tool calls freely - Plan ambitious multi-step operations ### YELLOW Zone (60-75% context used) - **Behavior:** Be selective. Start economizing. - Prefer `Grep` with targeted patterns over `Read` for large files - Summarize file contents instead of quoting them fully - Batch related operations together - Avoid re-reading files already in context - Delegate exploration to the investigator agent (Haiku) when possible ### ORANGE Zone (75-85% context used) - **Behavior:** Conserve aggressively. Focus on completing the current task. - Only read specific line ranges, never full files - Use `Grep` exclusively for finding information - Give concise responses - skip explanations unless asked - Do NOT start new exploratory tasks - Delegate any research to subagents - Consider creating fresh context files (TASK.md + PROGRESS.md) ### RED Zone (> 85% context used) - **Behavior:** Wrap up immediately. Prepare for handoff. - Stop all exploratory work - Complete only the immediately active task - Create TASK.md and PROGRESS.md with current state - Suggest the user start a new conversation - If code changes are in progress, commit or save the current state