I’ve built 18+ products for clients using Cursor, and I’ve cracked...

If you’re a beginner, this thread has all the tips and tricks you need to get started and make Cursor actually work for you 👇
This tells Cursor your coding preferences and standards.
Use /generate-cursor-rules
Stop copy-pasting random project rules. Build them based on your own codebase context. You’ll get way better results.
Before launch, make sure:
• Rate limiting is active
• Row-level security is enabled on all Supabase tables
• CAPTCHA is added to all auth flows
• API keys are in .env
• Backend validation is in place
• Unused dependencies are removed
• Logging is set up for 500 errors, login failures, etc.
Non-negotiable.
Go to Settings → Chat → Enable Custom Modes.
Switching modes lets you change the agent’s behavior instantly.
Set up 2 modes:
• Planning Mode (Claude Opus): no code, just analysis
• Fast Build (Claude Sonnet): no explanation, just output
Switch between them using Cmd+1 and Cmd+2.
Feels like switching teammates.
Enable Auto-Run, but add a denylist:
• rm -rf /*
• git push --force
• npm uninstall
Use it only for safe tasks like formatting and installing packages.
Avoid using it for:
• Critical production changes
• Database migrations
• Complex deploy scripts
For bigger tasks, pick a model with the brain icon.
They pause, plan, and code more reliably.
Less bugs, more structure.
Be clear and specific.
Instead of:
Build a SaaS app
Try:
Build the login page using Supabase. Start with the login component. Once that’s done, tell me how to test it. Then we’ll move to the signup part.
Add:
If you’re not 95% confident, ask questions first.
Or:
Explain your approach first. No code yet.
Before building, create:
• PRD or MVP Plan
• Database schema
• UI Development Plan
• Implementation Plan
Save these as .md files inside your repo. Cursor uses them well.
Install Wispr Flow.
Press the function key, speak, release.
Saves hours.
Never ask Cursor to build everything at once.
Break tasks down.
Commit after each one.
You’ll create restore points if anything breaks.
Pro tip: Use Taskmaster MCP to split PRDs into subtasks.
@ makes Cursor more accurate:
• @ filename for specific files
• @ foldername for directories
• @ docs for added documentation
• @ #123 for GitHub issues/commits
Press Cmd+E to launch a background agent.
They work in the cloud and submit a pull request when done.
Important:
Always create a new Git branch first.
Never let agents work on main or dev directly.
Give them clear tasks.
After every feature, run the coderabbit extension inside cursor
Click “fix with ai”
The agent reviews the code and patches issues instantly
Feels like a senior dev is reviewing your PRs in real-time
Click the notepad icon in the sidebar.
Store:
• Best prompts
• Reusable code snippets
• Feedback
• Project notes
All in one place, without switching tools.
Turn off privacy mode in settings.
Then go to Memories and add your preferences.
Examples:
• Always use pnpm
• Use functional components in React
• Never use any in TypeScript
These apply globally across all projects.
ChatGPT = your architect
Cursor = your builder
Plan using GPT-4 or o1.
Ask for multiple approaches.
Then implement the best one with Cursor.
This avoids bad architecture decisions.
• Switch models
• Paste full error and say “Fix it”
• Upload a screenshot of broken UI
• Add “Do not do anything else” to your prompt
• Ask it to explain the logic like you’re a beginner
Almost always works.
You got a tip not mentioned above, drop it below.
Let's make it the best cursor tips and tricks thread out there.
And all the other AI dev workflows I’ve shared this week.
So I started a weekly newsletter
Quick recap every Sunday on AI dev, vibe coding, and MVP building.
Subscribe here:
aimvpweekly.beehiiv.com