A coding agent's default Read is all-or-nothing: point it at a 6,000-line file to change one method and it pulls the whole thing into context — then re-bills every line on every later turn. Give it a structural 'map' read that returns signatures and line ranges with bodies dropped, and let it range-read only the symbols it actually needs.
Read a Structural Map of a Big File First, Not All 6,000 Lines
🔒 Pro tip · Advanced
Unlock this tip — and 123 more
This is one of 124 advanced, fact-checked tactics reserved for Pro. Get the full 146-tip library, a searchable archive, and a new tip every morning. Free for 7 days, then $9/mo.
Prefer to browse? The 22 Beginner tips are free forever.
More in Coding Assistants
💻Coding Assistants
Often cuts output tokens 40-70% on edits to large files, varies by file size
Ask for the Patch, Not the Whole File
When editing an existing file, tell the assistant to return only the changed lines as a diff or snippet instead of regenerating the entire file.
💻Coding Assistants
often 30-60% on long sessions
Run /clear Between Tasks in Claude Code Instead of Letting Context Pile Up
Claude Code resends the whole conversation every turn. Finishing one task and starting an unrelated one in the same thread means you keep paying for stale tool output and dead files.
💻Coding Assistants
10-30% on context-heavy chats
Add a .cursorignore So Cursor Stops Indexing Your node_modules
Cursor's @codebase and automatic context can pull in build artifacts, lockfiles, and vendored dependencies. A .cursorignore file keeps that noise out of every prompt.