We’ve built 20+ MVPs for our clients with AI The biggest thing I...
Prajwal Tomar@PrajwalTomar_
75 views
Sep 10, 2025
~2 min read
Advertisement
1
We’ve built 20+ MVPs for our clients with AI
The biggest thing I learned about AI coding is… it needs a detailed plan.
Most people jump straight into coding. That’s a mistake.
Documentation is 80% of the work. Implementation is only 20%.
Here’s how I build my MVPs:
🧵👇
The biggest thing I learned about AI coding is… it needs a detailed plan.
Most people jump straight into coding. That’s a mistake.
Documentation is 80% of the work. Implementation is only 20%.
Here’s how I build my MVPs:
🧵👇
2
1/ Plan Before You Code
AI tools are powerful, but they need guidance to perform well. A clear roadmap reduces hallucinations, debugging errors, and unnecessary revisions.
Before I even open Cursor, I have these docs ready:
- Project Requirements Doc
- Tech Stack Doc
- App Flow Doc
- Frontend Guidelines Doc
- Backend Structure Doc
I used to create these manually. Now I use @codeguidedev to generate them in minutes. Saves time, reduces hallucinations, and makes everything smoother.
AI tools are powerful, but they need guidance to perform well. A clear roadmap reduces hallucinations, debugging errors, and unnecessary revisions.
Before I even open Cursor, I have these docs ready:
- Project Requirements Doc
- Tech Stack Doc
- App Flow Doc
- Frontend Guidelines Doc
- Backend Structure Doc
I used to create these manually. Now I use @codeguidedev to generate them in minutes. Saves time, reduces hallucinations, and makes everything smoother.
3
2/ Structuring the MVP
Before, I used ChatGPT to break down features and structure the MVP.
Now, CodeGuide does it automatically. It creates a detailed PRD with:
- A full feature breakdown
- In-scope vs out-of-scope
- User flows + recommended tech stack
And it’s built specifically for AI coding tools like Cursor.
Before, I used ChatGPT to break down features and structure the MVP.
Now, CodeGuide does it automatically. It creates a detailed PRD with:
- A full feature breakdown
- In-scope vs out-of-scope
- User flows + recommended tech stack
And it’s built specifically for AI coding tools like Cursor.
4
3/ Building 70–80% of the MVP in @lovable First
Instead of jumping straight into Cursor, I build 70–80% of the MVP in Lovable.
Why?
- Seamless Supabase integration
- Easy backend setup
- Quickly refine UI until it’s polished
Process:
- Paste CodeGuide docs into Lovable
- Generate UI (start with landing page)
- Refine until solid
- Connect backend with Supabase
By the time I switch to Cursor, the MVP is already structured.
Instead of jumping straight into Cursor, I build 70–80% of the MVP in Lovable.
Why?
- Seamless Supabase integration
- Easy backend setup
- Quickly refine UI until it’s polished
Process:
- Paste CodeGuide docs into Lovable
- Generate UI (start with landing page)
- Refine until solid
- Connect backend with Supabase
By the time I switch to Cursor, the MVP is already structured.
5
4/ Perfecting the Landing Page First
The landing page sets the foundation. If it’s clean and consistent, the rest flows.
I focus on:
- Layout & spacing
- Component consistency
- Smooth user experience
Once this is solid, I build the rest of the screens in Lovable before switching to Cursor.
The landing page sets the foundation. If it’s clean and consistent, the rest flows.
I focus on:
- Layout & spacing
- Component consistency
- Smooth user experience
Once this is solid, I build the rest of the screens in Lovable before switching to Cursor.
6
5/ Using Cursor the Right Way
Most people tell Cursor to “just build” their MVP. That rarely works.
Instead, I:
- Import the repo from Lovable via GitHub
- Paste CodeGuide docs into Cursor as .md files
- Let Cursor handle backend logic, APIs, and refining the UI
Cursor works best when guided properly. Docs prevent hallucinations.
Most people tell Cursor to “just build” their MVP. That rarely works.
Instead, I:
- Import the repo from Lovable via GitHub
- Paste CodeGuide docs into Cursor as .md files
- Let Cursor handle backend logic, APIs, and refining the UI
Cursor works best when guided properly. Docs prevent hallucinations.
7
6/ The AI Tools That Make It All Work
Here’s my stack:
- Cursor → Core Development
- Lovable → Initial MVP Build
- CodeGuide → Docs & PRDs, Reduce Hallucinations
The right mix = Faster builds with fewer errors.
Here’s my stack:
- Cursor → Core Development
- Lovable → Initial MVP Build
- CodeGuide → Docs & PRDs, Reduce Hallucinations
The right mix = Faster builds with fewer errors.
8
7/ Key Takeaways
- Plan before you code.
- Docs are non-negotiable.
- Build UI first, dev second.
@cursor_ai + @codeguidedev + @lovable = ultimate speed.
AI doesn’t replace devs. It makes us faster.
If you’re struggling with AI coding, start by organizing your project. It changes everything.
- Plan before you code.
- Docs are non-negotiable.
- Build UI first, dev second.
@cursor_ai + @codeguidedev + @lovable = ultimate speed.
AI doesn’t replace devs. It makes us faster.
If you’re struggling with AI coding, start by organizing your project. It changes everything.
9
Want to build your first MVP? I can help in 2 ways:
1. Hire us at @ignytlabs and we’ll build it ;)
2. Learn inside @aimvpbuilders
Either way, you’ll ship faster than 99% of people.
1. Hire us at @ignytlabs and we’ll build it ;)
2. Learn inside @aimvpbuilders
Either way, you’ll ship faster than 99% of people.
