Recently stumbled across this Cursor pro-tip from Ian Nuttall on X: "1. ask it to recommend a folder structure
2. ask it to actually create the folder/files based on that this makes it 10x easier for me to get started and Cursor is more accurate using codebase cos it knows where to update files."
That got me thinking, what other pro tips are people using to generate better code, ship faster, organise your space better, etc. Drop em below:
You can now work with Cursor Agents on web and mobile. Just like the familiar agent that works alongside you in the IDE, agents on web and mobile can write code, answer complex questions, and scaffold out your work.
Now with automated code review to catch and fix bugs in your PRs, memories to learn from your codebase, 1-click MCP installs, and Background Agent in GA. Plus, faster multi-location edits, richer chat interactions, new settings, and Jupyter notebook support.
Cursor 1.7 is here! Introducing autocomplete for agent, hooks, team rules, ability to share prompts with deeplinks, and more. Look forward to hearing what you think!
There's a lot of options for models these days. I've been using Claude 3.7 but I'm curious what's been working well for others. What model are you using and why?
Is the thinking version of @Claude by Anthropic worth the extra credit spend? Does @DeepSeek work well enough to save some credits? Is it worth trying any of the @ChatGPT by OpenAI models?
Recently started consulting with a startup, and I ve fully switched to Cursor for all my PRDs and PM needs no more Google Docs or anything else. I ll never go back!
With MCP, I ve even connected Google Docs, just in case I ever need it right inside Cursor itself, haha.
Oh, and I m nudging the devs here to try Cursor too slowly moving them away from Copilot.
A more powerful version of Copilot that can suggest mid-line completions and entire diffs. Trained to autocomplete on sequences of edits, it's quick to understand the change you're making.
