How to build MVPs with AI the right way This is the system I...
Prajwal Tomar@PrajwalTomar_
48 views
May 15, 2025
~2 min read
Advertisement
1
How to build MVPs with AI the right way
This is the system I recommend to anyone starting from scratch.
Beginner-friendly. AI-powered. Repeatable.
Bookmark this if you want to build smarter ↓
This is the system I recommend to anyone starting from scratch.
Beginner-friendly. AI-powered. Repeatable.
Bookmark this if you want to build smarter ↓
2
1/ Don’t start with code
Most indie devs waste time building things nobody wants.
Only build when:
- The product already exists in some form
- There are paying users
- You’ve studied what works
Copy the structure, not the brand.
Most indie devs waste time building things nobody wants.
Only build when:
- The product already exists in some form
- There are paying users
- You’ve studied what works
Copy the structure, not the brand.
3
2/ Design before logic
No need to plan the backend yet.
Start with:
- Sketching out the screens
- Collecting working UI patterns
- Use UX Pilot to generate the layout
You should see the app before you build it. This saves hours later.
No need to plan the backend yet.
Start with:
- Sketching out the screens
- Collecting working UI patterns
- Use UX Pilot to generate the layout
You should see the app before you build it. This saves hours later.
4
3/ Plan your backend after the UI is done
Once the layout is ready, ask:
- What data powers this screen?
- What actions does the user take?
Then use Supabase to handle:
- Auth
- DB
- Edge Functions
- File uploads
Skip the heavy infra.
Once the layout is ready, ask:
- What data powers this screen?
- What actions does the user take?
Then use Supabase to handle:
- Auth
- DB
- Edge Functions
- File uploads
Skip the heavy infra.
5
4/ Let AI help you architect it
Cursor can handle:
- Creating the database
- Creating routes and APIs
- Implementing all this straight inside Supabase
Connect Supabase via MCP and guide it clearly.
Cursor can handle:
- Creating the database
- Creating routes and APIs
- Implementing all this straight inside Supabase
Connect Supabase via MCP and guide it clearly.
6
5/ Talk to AI like a teammate
Don’t just throw in a task. Explain your goal.
And always add:
“Only write code if you’re 95% confident. Ask questions if anything is unclear.”
For more tips feel free to go through my other tweets around cursor.
Better structure = fewer mistakes.
Don’t just throw in a task. Explain your goal.
And always add:
“Only write code if you’re 95% confident. Ask questions if anything is unclear.”
For more tips feel free to go through my other tweets around cursor.
Better structure = fewer mistakes.
7
6/ Build in scoped chunks
The biggest mistake? Trying to do too much in one go.
Break your build down:
- One screen at a time
- One function at a time
- One table at a time
Try using an implementation plan for this.
Keep your context thread alive for smarter AI outputs.
The biggest mistake? Trying to do too much in one go.
Break your build down:
- One screen at a time
- One function at a time
- One table at a time
Try using an implementation plan for this.
Keep your context thread alive for smarter AI outputs.
8
7/ Debug visually with screenshots
Text prompts are useful, but screenshots make a big difference.
If something breaks:
- Paste the screenshot in Cursor
- Tell the AI what’s wrong
- Let it patch the layout
This saves hours.
Text prompts are useful, but screenshots make a big difference.
If something breaks:
- Paste the screenshot in Cursor
- Tell the AI what’s wrong
- Let it patch the layout
This saves hours.
9
8/ Repeat this loop for every feature
This is the loop I follow when helping clients:
- Research similar apps
- Design the UI
- Plan data and logic
- Build with AI
- Debug and refactor
- Ship it
- Move on
Simple. Structured. Effective.
This is the loop I follow when helping clients:
- Research similar apps
- Design the UI
- Plan data and logic
- Build with AI
- Debug and refactor
- Ship it
- Move on
Simple. Structured. Effective.
10
I’m planning to do an entire series on this after the "Vibe Coding System" series wraps up inside @aimvpbuilders.
If this is something you’d find useful, let me know.
Might even start the series in parallel.
If this is something you’d find useful, let me know.
Might even start the series in parallel.
