Disclosure: Cursor offers user referral credits, not a publisher affiliate program — we don't earn a commission on this one.
According to DevTools Review's hands-on testing across 11 AI coding tools, most "Cursor tips" content repeats the same three things: write a .cursorrules file, use @ mentions, try Agent mode. True, but thin. Here are the ones that actually change your daily workflow, pulled from our full guide.
Stop accepting whole Tab suggestions
When Cursor's Tab completion gets the first part of a suggestion right and the rest wrong, don't accept-then-edit. Press Cmd+Right Arrow (Mac) / Ctrl+Right Arrow (Windows/Linux) to accept word by word, stop where it diverges, type your correction, and a new suggestion picks up from there. This alone cuts a surprising amount of "accept, immediately delete half of it" friction on function calls and conditionals.
.cursorignore is not optional
If you haven't set one up, Cursor is indexing your node_modules, build output, and .sql dumps as project context. That's slower indexing and noisier AI responses for no benefit. A minimal one excludes node_modules, dist/build/.next, coverage, *.min.js, *.lock, and any large data directories. Immediate effect, one-time cost.
@docs beats hoping the model's training data is current
Add your key dependencies' documentation URLs under Cursor Settings > Features > Docs, then reference them directly: @docs How do I set up middleware in Next.js App Router to redirect unauthenticated users?. This grounds the answer in the actual current docs instead of whatever version the model happened to train on — the gap matters more than people expect for fast-moving libraries.
Composer's real failure mode isn't hallucination, it's silent context loss
When a Composer session hits its context window limit, there's no visible warning — it just starts losing track of earlier files and quality quietly degrades. If output several files into a session gets worse for no obvious reason, that's usually why. Start a fresh session rather than pushing through.
Tag files explicitly in Composer, every time
"Add a delete endpoint" invites Composer to touch files you didn't intend. "Add a DELETE endpoint for users. Modify @src/routes/users.ts, @src/services/user-service.ts, @src/tests/users.test.ts" scopes it precisely and gives better context in one move. Two problems, one habit.
@git for the boring part of shipping
@git Write a detailed commit message for my staged changes and @git What files have I changed in the last 3 commits? turn PR prep from a chore into a one-liner. Small, but it's the kind of thing that saves five minutes a dozen times a day rather than an hour once.
The full list
The complete guide covers 16 tips across project setup, productivity shortcuts, code-quality workflows (including a systematic security/performance/error-handling review prompt), and advanced patterns like chaining Agent mode with explicit success criteria instead of step-by-step instructions.
Full guide: https://devtoolsreview.com/tutorials/cursor-tips-tricks/
Top comments (0)