Are you making these Cursor mistakes?
Three common habits that send Agent the wrong way. See how you'd handle each one. Answers are instant, and no sign-up is needed.
-
Q1 Agent keeps writing new validation helpers when your repo already has one. What should change first?Why
Agents take requests literally, and "add validation" can succeed by writing new code. An exploring step makes it read your validators and gives you names for a better request. A rule naming the helper stops repeats.
Why Does Cursor's Agent Duplicate Code You Already Have? -
Q2 You're mid-feature, and Agent has been going in circles for a while. What should you do?Why
Everything said in a chat stays in context, including wrong turns, so a stale approach can seem settled. Starting fresh with no summary risks repeating the failure, so bring what you've learned. Project rules still load at the start.
When Should You Start a New Chat in Cursor? -
Q3 To be safe, you set all 30 of your rules to Always Apply. What's the downside?Why
Whatever loads every time leaves less room for your code. Glob-scoped rules, skills and subagents keep instructions available without loading them each time.
Are Too Many Rules and MCP Servers Hurting Cursor?
Study this topic