More context is not automatically better. The goal is to give enough evidence to understand the change while keeping irrelevant code and stale documentation out.
1. Start with the failing surface
Point to the error, file, component, symbol, screenshot or terminal output that shows the problem.
2. Add only direct dependencies
Include interfaces, types, tests or callers that constrain the behavior. Avoid attaching broad folders before you know they matter.
3. Use repository search deliberately
Ask Agent to locate definitions and references, then bring the few relevant files into active context rather than guessing based on filenames.
4. Tell it what is authoritative
Name the source of truth when docs, types and implementation disagree. Old design notes should not silently override current code.
5. Trim and restate when the task drifts
If the conversation becomes long or Agent starts using irrelevant context, restate the goal and reopen only the files needed for the next decision.
Do not scan the entire repository yet. Start from this error and identify the minimum files needed to explain it. Tell me why each file matters, then inspect only those files before proposing a fix.
Attaching the entire monorepo; mixing stale docs with live code; assuming the nearest filename is the dependency; letting a long chat accumulate unrelated decisions.
Finish check
Agent can explain the behavior and propose a bounded change using a small, auditable set of source files and evidence.