At-Mentions and Context Types

Done means you can attach precise context and leave discovery to Agent only when appropriate.

Better answers come from smaller, explicit context: files, docs, terminal output and evidence.

Use Prompting and at-mentions when the task depends on specific files, diffs, logs or docs. Keep the boundary narrow.

Start small. Name the job, attach the context that proves the point and decide what evidence would make the output trustworthy.

Read the loop before touching the controls. The first beat frames the work, the second uses Cursor, the third checks the result and the fourth leaves a handoff someone else can inspect.

Treat this as a short practice loop, not a product tour. The task should be small enough that you can inspect the result without trusting the summary.

1. 1Name the task and identify the minimum context it needs.
2. 2Attach exact files or folders when you know the boundary.
3. 3Attach terminal output, errors, docs or diffs when they define done.
4. 4Ask Cursor to search when you do not know the right files yet.

The exercise is complete only when the proof matches the requested outcome. If the proof is weak, reduce the scope or fix the context instead of adding more instructions.

Verification decides the next move.

Use the first failure signal as the next prompt. Broad retries usually make the run noisier; a narrow retry gives Cursor a concrete repair target.