context-discipline

Prevent context window overload during long coding sessions by applying MCP-first navigation, lazy loading, subagent-based context isolation, summarize-and-discard behavior, and explicit token budgeting to keep sessions effective.

Avoid wasting tokens on repeated file reads by using MCP-first navigation for symbol lookup and API inspection, applying lazy loading to read only necessary files and methods, and offloading verbose exploration into subagents.

Subagent context isolation works by offloading verbose codebase exploration and analysis into subagents, returning only compact summaries to your main context instead of raw content to keep your working context lean.

You need explicit token budgeting during coding, debugging, and implementation planning scenarios involving large codebases where naive directory browsing and repeated file reads risk exhausting your limited context window.

Lazy loading helps with implementation planning by reading only necessary files and methods when needed, instead of preloading large swaths of the repository, keeping your working context lean and effective for longer sessions.