Context Management in Cursor
Useful context is relevant context. A large amount of background can still hide the task's most important constraints.
#Start with structure, then narrow
Use files/folders to understand a module or repository layout. When making a precise change, attach the relevant file or code segment rather than the entire project. Dragging a file into the conversation can be a convenient alternative to the reference picker.
#Use local code for local questions
A selected function, effect or hook is often more useful than a whole file when diagnosing one behavior. The aim is to focus attention, not maximize the number of attached documents.
#Attach documentation when the API matters
For an unfamiliar library or external system, use the supported documentation/context features or supply the official reference. The source describes @Docs and an Indexing & Docs settings area; names and availability may differ in your version. Inspect the actual interface rather than assuming a historical workflow still applies.
#Common context mistakes
- Attaching the whole repository for a narrow bug.
- Carrying an old conversation into a different task.
- Providing broad folders without the actual failing code or error.
#A three-layer strategy
- Explain the project structure.
- State the current task and constraints.
- Provide the exact local code and evidence.
Start a fresh conversation when moving from exploration to implementation, implementation to performance work, or frontend diagnosis to a backend contract. Retain a concise handover of relevant facts instead of stale assumptions.
#Context also affects written content
When producing documentation or Wiki articles, precise source material helps prevent empty, repetitive or off-topic drafts. It does not guarantee search indexing; its practical benefit is a clear, supported topic.
#Next steps
Before adding more context, remove material that does not help answer the present question.
