Cursor is powerful. But if you’re just prompting it randomly,...
Prajwal Tomar@PrajwalTomar_
38 views
Mar 28, 2025
~3 min read
Advertisement
1
Cursor is powerful.
But if you’re just prompting it randomly, you’re leaving 80% of its potential untapped.
Here’s my exact playbook after building 17+ products with it.
But if you’re just prompting it randomly, you’re leaving 80% of its potential untapped.
Here’s my exact playbook after building 17+ products with it.
2
1/ Don’t start coding. Plan first.
Most devs open Cursor and start prompting randomly.
That’s why things break.
Instead, prep a folder with:
• PRD
• Tech stack overview
• Suggested file structure
• Frontend/backend guidelines
• .cursorrules file
Save them all as markdown inside your repo.
I used to do this manually in ChatGPT.
Now I use @CodeGuideDev to generate everything in minutes. Total game-changer.
Most devs open Cursor and start prompting randomly.
That’s why things break.
Instead, prep a folder with:
• PRD
• Tech stack overview
• Suggested file structure
• Frontend/backend guidelines
• .cursorrules file
Save them all as markdown inside your repo.
I used to do this manually in ChatGPT.
Now I use @CodeGuideDev to generate everything in minutes. Total game-changer.
3
2/ Don’t start from scratch
Cursor works best when it has something to build on.
Use V0/Lovable/Bolt to generate complete functional screens and trying building 80% of the MVP there
Then bring the code into Cursor for refinement + logic.
Cursor works best when it has something to build on.
Use V0/Lovable/Bolt to generate complete functional screens and trying building 80% of the MVP there
Then bring the code into Cursor for refinement + logic.
4
3/ Set up Project Rules
Stop using .cursorrules. Set up Project Rules instead
Project Rules let you:
- Apply different rules per filetype (e.g., SQL vs JS)
- Control AI tone and structure
- Sync across your team via GitHub
This makes Cursor feel like an AI dev trained on your stack.
Stop using .cursorrules. Set up Project Rules instead
Project Rules let you:
- Apply different rules per filetype (e.g., SQL vs JS)
- Control AI tone and structure
- Sync across your team via GitHub
This makes Cursor feel like an AI dev trained on your stack.
5
4/ Sync relevant docs for better suggestions
Go to @Docs → Add new doc
Sync docs for:
- Next.js
- Supabase
- Stripe
This gives Cursor deeper context, improving both code accuracy and suggestions.
Go to @Docs → Add new doc
Sync docs for:
- Next.js
- Supabase
- Stripe
This gives Cursor deeper context, improving both code accuracy and suggestions.
6
5/ Use @Codebase to query the entire repo
Need to trace a bug or locate a function?
Use @Codebase and ask:
- “Where is the payment flow handled?”
- “Which component renders the dashboard?”
Cursor will scan and answer based on your full project context.
Need to trace a bug or locate a function?
Use @Codebase and ask:
- “Where is the payment flow handled?”
- “Which component renders the dashboard?”
Cursor will scan and answer based on your full project context.
7
6/ Set up MCP for schema access + automation
Model Context Protocol (MCP) gives Cursor live access to your Supabase schema.
With MCP, you can:
- Fetch tables dynamically
- Automate schema edits
- Skip writing migration files manually
The database becomes AI-readable. Game changer. It has many other use cases as well.
Model Context Protocol (MCP) gives Cursor live access to your Supabase schema.
With MCP, you can:
- Fetch tables dynamically
- Automate schema edits
- Skip writing migration files manually
The database becomes AI-readable. Game changer. It has many other use cases as well.
8
7/ Auto-generate Row-Level Security with AI
Most developers skip RLS because it’s tedious.
Now? Just tell Cursor:
“Generate RLS policy so users can only access their own data.”
It writes secure access rules in seconds.
Most developers skip RLS because it’s tedious.
Now? Just tell Cursor:
“Generate RLS policy so users can only access their own data.”
It writes secure access rules in seconds.
9
8/ Enable YOLO Mode for speed
Cursor normally asks before executing commands.
With YOLO Mode:
- Commands run instantly
- No confirmation prompts
- Perfect for trusted flows or power users
If used wisely, it saves hours.
Cursor normally asks before executing commands.
With YOLO Mode:
- Commands run instantly
- No confirmation prompts
- Perfect for trusted flows or power users
If used wisely, it saves hours.
10
9/ Use screenshots to improve UI
If your UI feels off, take a screenshot.
Drag it into Cursor or click the image icon under chat.
Then prompt:
“Make this UI cleaner and more modern”
This visual feedback unlocks next-level UI iterations.
If your UI feels off, take a screenshot.
Drag it into Cursor or click the image icon under chat.
Then prompt:
“Make this UI cleaner and more modern”
This visual feedback unlocks next-level UI iterations.
11
10/ Save your best code in .md files + Notepad
Whenever Cursor writes something useful:
- Save it as a .md file for future prompting
- Store snippets in Notepad for reuse
This helps you build a personal AI library, your own internal Copilot.
Whenever Cursor writes something useful:
- Save it as a .md file for future prompting
- Store snippets in Notepad for reuse
This helps you build a personal AI library, your own internal Copilot.
12
Final takeaway
Treat Cursor like a teammate, not a magic trick.
Guide it right, and it will ship faster than any junior dev you’ve hired.
If you found this helpful, bookmark it.
Let’s build better with AI.
Treat Cursor like a teammate, not a magic trick.
Guide it right, and it will ship faster than any junior dev you’ve hired.
If you found this helpful, bookmark it.
Let’s build better with AI.
