Attach evidence, not just a diagnosis
Feed Cursor the artifacts that prove the problem instead of only describing the problem in your own words.
The habit: show Cursor what happened before you tell it what you think happened. @-context is powerful because it lets you put the same evidence in front of the model that you would inspect yourself. Files show implementation reality. Logs show runtime reality. Screenshots show UI reality. Taken together, they prevent the model from overfitting to the shorthand in your summary. This does not mean drowning the session in twenty files. It means choosing the smallest evidence set that proves the problem. One failing spec and the touched module often beat a paragraph of narrative.
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in