Want to know how I use Cursor and Lovable to ship MVPs fast for...
Prajwal Tomar@PrajwalTomar_
66 views
Jul 17, 2025
~3 min read
Advertisement
1
Want to know how I use Cursor and Lovable to ship MVPs fast for clients?
I’ve built 18+ products using this exact workflow.
Here’s the full system I use to plan, design, build, and launch.
👇 Save this. You’ll need it.
I’ve built 18+ products using this exact workflow.
Here’s the full system I use to plan, design, build, and launch.
👇 Save this. You’ll need it.
2
1. Start with planning
Before writing a single line of code, I plan everything inside ChatGPT.
The documents I create:
- PRD (Product Requirements Document)
- UI Development Plan
- Database Design
- Implementation Plan
This step is where 90% of the clarity comes from. The more structured these are, the better the output across every tool.
Before writing a single line of code, I plan everything inside ChatGPT.
The documents I create:
- PRD (Product Requirements Document)
- UI Development Plan
- Database Design
- Implementation Plan
This step is where 90% of the clarity comes from. The more structured these are, the better the output across every tool.
3
2. Create your PRD inside ChatGPT
Same method I always use:
- Paste everything you or your client has shared
- Ask ChatGPT to list features and break them into core, optional, and future
- Prioritize with the MoSCoW method
- Refine it inside ChatPRD (my custom GPT)
Once it feels right, lock it in.
Same method I always use:
- Paste everything you or your client has shared
- Ask ChatGPT to list features and break them into core, optional, and future
- Prioritize with the MoSCoW method
- Refine it inside ChatPRD (my custom GPT)
Once it feels right, lock it in.
4
3. Design your database
Paste your final PRD into ChatGPT and ask:
Define the tables, their purposes, and how they relate to each other
It generates a clean database structure.
Copy this into your Notion or save as a .md file.
You’ll use this constantly inside Cursor.
Paste your final PRD into ChatGPT and ask:
Define the tables, their purposes, and how they relate to each other
It generates a clean database structure.
Copy this into your Notion or save as a .md file.
You’ll use this constantly inside Cursor.
5
4. Draft your UI Development Plan
This replaces old-school wireframes.
Here’s how I do it:
- paste your PRD into ChatGPT
- ask it to list all the UI screens your product needs
- for each screen, ask it to describe what it looks like, what components are used, and what it does
- copy these descriptions into a Google Doc
This is your UI dev blueprint.
The more detailed these are, the better Lovable performs.
This replaces old-school wireframes.
Here’s how I do it:
- paste your PRD into ChatGPT
- ask it to list all the UI screens your product needs
- for each screen, ask it to describe what it looks like, what components are used, and what it does
- copy these descriptions into a Google Doc
This is your UI dev blueprint.
The more detailed these are, the better Lovable performs.
6
5. Build the UI inside @lovable
This is where things get fun.
- Take the UI screen descriptions and feed them into Lovable
- Add visual inspiration or drop in reference websites
- Use SnapPrompt to build beautiful landing pages
- Once the landing page is solid, use it as the design system for the rest
After 4–5 iterations, you’ll have a beautiful, production-ready UI.
This is where things get fun.
- Take the UI screen descriptions and feed them into Lovable
- Add visual inspiration or drop in reference websites
- Use SnapPrompt to build beautiful landing pages
- Once the landing page is solid, use it as the design system for the rest
After 4–5 iterations, you’ll have a beautiful, production-ready UI.
7
6. Add backend inside Lovable
Auth, Stripe, OpenAI, everything.
Try to get 70–80% of your MVP working inside Lovable before moving anywhere else.
If a feature starts burning tokens or you’re hitting frustrating bugs, that’s your signal to bring it into Cursor.
Auth, Stripe, OpenAI, everything.
Try to get 70–80% of your MVP working inside Lovable before moving anywhere else.
If a feature starts burning tokens or you’re hitting frustrating bugs, that’s your signal to bring it into Cursor.
8
7. Move to Cursor
Use GitHub two-way sync.
Pull the full codebase into Cursor.
Then drop all your docs (PRD, database design, UI plan, implementation plan) as .md files into the project.
These act as the Cursor agent’s memory.
PRO TIP: Always refer to these docs in your prompts.
Cursor performs 10x better with rich context.
Use GitHub two-way sync.
Pull the full codebase into Cursor.
Then drop all your docs (PRD, database design, UI plan, implementation plan) as .md files into the project.
These act as the Cursor agent’s memory.
PRO TIP: Always refer to these docs in your prompts.
Cursor performs 10x better with rich context.
9
8. Build, test, and refine
Now you’re in dev mode.
Use Cursor to:
- Break down features
- Discuss implementation approaches
- Generate and test full backend logic
Keep updating the docs if things change. Iterate fast, and keep context flowing.
Now you’re in dev mode.
Use Cursor to:
- Break down features
- Discuss implementation approaches
- Generate and test full backend logic
Keep updating the docs if things change. Iterate fast, and keep context flowing.
10
9. Run security reviews with CodeRabbit
Before pushing to prod, run full security + code reviews inside Cursor using @coderabbitai.
It catches:
- RLS issues
- API key exposure
- Unvalidated inputs
- Poor logic or structure
Treat it like your senior dev reviewing your final push.
Before pushing to prod, run full security + code reviews inside Cursor using @coderabbitai.
It catches:
- RLS issues
- API key exposure
- Unvalidated inputs
- Poor logic or structure
Treat it like your senior dev reviewing your final push.
11
10. Launch checklist + polish
Once your MVP is complete:
- Run through your launch checklist
- Final test flows
- Analytics, SEO, monitoring
Then push live.
Once your MVP is complete:
- Run through your launch checklist
- Final test flows
- Analytics, SEO, monitoring
Then push live.
12
Final Takeaway
Always start in Lovable.
Only switch to Cursor when needed.
Keep all planning docs inside the codebase.
Run code reviews before you ship.
Planning feels slow at first.
But it makes everything else 10x faster.
This workflow has shipped 18+ MVPs.
Steal it.
Always start in Lovable.
Only switch to Cursor when needed.
Keep all planning docs inside the codebase.
Run code reviews before you ship.
Planning feels slow at first.
But it makes everything else 10x faster.
This workflow has shipped 18+ MVPs.
Steal it.
13
if this thread helped, i post ai workflows like this every day
follow @PrajwalTomar_ for more
questions? drop them below, happy to help :)
like or repost the quote tweet if it was useful:
follow @PrajwalTomar_ for more
questions? drop them below, happy to help :)
like or repost the quote tweet if it was useful:
Prajwal Tomar@PrajwalTomar_
Want to know how I use Cursor and Lovable to ship MVPs fast for clients?
I’ve built 18+ products using this exact workflow.
Here’s the full system I use to plan, design, build, and launch.
👇 Save this. You’ll need it.
I’ve built 18+ products using this exact workflow.
Here’s the full system I use to plan, design, build, and launch.
👇 Save this. You’ll need it.
14
This thread is based on the “Launch Your First AI MVP” video series inside my private AI-first devs community @aimvpbuilders
300+ of us are building AI MVPs together.
If that sounds like your thing, join here:
skool.com/ai-mvp-builder…
300+ of us are building AI MVPs together.
If that sounds like your thing, join here:
skool.com/ai-mvp-builder…
15
@rashem48 But yeah, they’re improving the product super fast, feels like we’re not too far from building full complex apps entirely inside Lovable :)
