If you’re new to Cursor, this will help you get started right. Here...
Prajwal Tomar@PrajwalTomar_
55 views
May 11, 2025
~2 min read
Advertisement
1
If you’re new to Cursor, this will help you get started right.
Here are a few lessons I wish I knew earlier while building MVPs with Cursor, Bolt, and MCP.
Not everything I know, but enough to save you weeks of trial and error ↓
Here are a few lessons I wish I knew earlier while building MVPs with Cursor, Bolt, and MCP.
Not everything I know, but enough to save you weeks of trial and error ↓
2
1. The wrong stack will break your MVP
AI doesn’t code like humans. It replicates patterns it’s seen before.
So if your stack is rare or messy, it’ll hallucinate.
What works for me:
• Next/ React for frontend
• Supabase for backend
• Stripe for payments
• Vercel for deploying
AI flows clean when your stack is AI-native.
AI doesn’t code like humans. It replicates patterns it’s seen before.
So if your stack is rare or messy, it’ll hallucinate.
What works for me:
• Next/ React for frontend
• Supabase for backend
• Stripe for payments
• Vercel for deploying
AI flows clean when your stack is AI-native.
3
2. You don’t need a full team. You need roles and structure.
My builds follow 4 clear stages, all driven by AI:
• Planner: Draft the PRD, user flows, and tech stack using ChatGPT
• Architect: Break down features into tasks and screen logic
• Builder: Load the plan into Cursor or Windsurf and execute task by task
• Reviewer: Run security audits, test flows, clean up UI, and commit builds
Security isn’t optional.
I run this inside Cursor before shipping:
rb.gy/tanzmm
This one prompt has caught dozens of silent bugs before launch.
My builds follow 4 clear stages, all driven by AI:
• Planner: Draft the PRD, user flows, and tech stack using ChatGPT
• Architect: Break down features into tasks and screen logic
• Builder: Load the plan into Cursor or Windsurf and execute task by task
• Reviewer: Run security audits, test flows, clean up UI, and commit builds
Security isn’t optional.
I run this inside Cursor before shipping:
rb.gy/tanzmm
This one prompt has caught dozens of silent bugs before launch.
4
3. Project Rules change everything
Most developers skip this. I used to too.
But once I started attaching .mdc rules inside .cursor/rules/, things changed.
Cursor stops guessing. Starts building.
Most developers skip this. I used to too.
But once I started attaching .mdc rules inside .cursor/rules/, things changed.
Cursor stops guessing. Starts building.
5
4. Different AI models serve different roles
People ask: which model is the best?
Wrong question.
Here’s what I use:
• Claude 3.5 Sonnet → Best for bug-fixing and logic-heavy execution
• GPT-4o → Great for product planning and UI dev plans
• Gemini 2.5 Pro → Reads huge codebases. Best for refactors/auditing the code for bugs, etc.
Pick your model according to your use case.
People ask: which model is the best?
Wrong question.
Here’s what I use:
• Claude 3.5 Sonnet → Best for bug-fixing and logic-heavy execution
• GPT-4o → Great for product planning and UI dev plans
• Gemini 2.5 Pro → Reads huge codebases. Best for refactors/auditing the code for bugs, etc.
Pick your model according to your use case.
6
5. Save often. Or regret it later.
Cursor is powerful. But it can nuke your working code in one wrong generation.
My tip?
Use git from day 1.
Run:
git init
git add .
git commit -m "stable"
Code broke?
git log
git reset --hard <commit>
Cursor is powerful. But it can nuke your working code in one wrong generation.
My tip?
Use git from day 1.
Run:
git init
git add .
git commit -m "stable"
Code broke?
git log
git reset --hard <commit>
7
6. If you’re using AI to debug, stop copy-pasting logs
Use Browser MCP.
Now I just prompt:
“Use Browser MCP to take a screenshot and gather console logs”
AI sees the actual screen + errors and fixes them without me doing anything.
Faster QA, smoother feedback loops, no tab switching.
Use Browser MCP.
Now I just prompt:
“Use Browser MCP to take a screenshot and gather console logs”
AI sees the actual screen + errors and fixes them without me doing anything.
Faster QA, smoother feedback loops, no tab switching.
8
Final Thoughts
The tools aren’t the problem.
It’s the lack of system.
You can build a real MVP solo, if you prep your docs, set rules, and use AI the right way.
Vibe coding got me here.
Structured coding with AI is what’s taking it to the next level.
The tools aren’t the problem.
It’s the lack of system.
You can build a real MVP solo, if you prep your docs, set rules, and use AI the right way.
Vibe coding got me here.
Structured coding with AI is what’s taking it to the next level.
9
There’s so much more you can do to make Cursor insanely efficient. I’ll keep sharing what’s working for me.
In the meantime, drop your favorite Cursor tips below. Let’s make this the go-to thread for building smarter with AI.
In the meantime, drop your favorite Cursor tips below. Let’s make this the go-to thread for building smarter with AI.