What I learned after building 2 MVPs with Claude Code (and why I...
Prajwal Tomar@PrajwalTomar_
55 views
Jun 25, 2025
~2 min read
Advertisement
1
What I learned after building 2 MVPs with Claude Code (and why I might not go back to Cursor)
Here’s what I wish someone told me earlier ↓
Here’s what I wish someone told me earlier ↓
2
1/ Claude isn’t a one-shot coder
Don’t just ask it to “add feature X.”
Start in plan mode.
Let it think first.
Then review the plan and run it.
It’s slower, but the code is way cleaner.
Don’t just ask it to “add feature X.”
Start in plan mode.
Let it think first.
Then review the plan and run it.
It’s slower, but the code is way cleaner.
3
2/ Create a claude.md file before you build
This is where you define your project:
- Goal
- Tech stack
- Folder structure
- App flow
Claude keeps referring to this throughout.
Without it, the context gets lost fast.
This is where you define your project:
- Goal
- Tech stack
- Folder structure
- App flow
Claude keeps referring to this throughout.
Without it, the context gets lost fast.
4
3/ Treat Claude like a junior dev
Break big tasks into smaller ones.
Give it the exact file/folder.
Tell it what to change.
Ask it to double-check its own work.
It’s surprisingly good at catching its own mistakes.
Break big tasks into smaller ones.
Give it the exact file/folder.
Tell it what to change.
Ask it to double-check its own work.
It’s surprisingly good at catching its own mistakes.
5
4/ Use Git aggressively
Claude doesn’t ask “Are you sure?”
It just edits.
So set checkpoints often.
I create a new branch for every task.
If something breaks, I can always roll back.
Claude doesn’t ask “Are you sure?”
It just edits.
So set checkpoints often.
I create a new branch for every task.
If something breaks, I can always roll back.
6
5/ Give it visual context
Got layout issues?
Use screenshots.
Just say:
“Here’s the bug”
“Here’s what I want it to look like”
It usually nails it in one go.
Got layout issues?
Use screenshots.
Just say:
“Here’s the bug”
“Here’s what I want it to look like”
It usually nails it in one go.
7
6/ Claude loves full folders
Sometimes I feed it entire folders from past MVPs.
It instantly understands the structure and style I’m aiming for.
Helps a LOT if you’re building something similar.
Sometimes I feed it entire folders from past MVPs.
It instantly understands the structure and style I’m aiming for.
Helps a LOT if you’re building something similar.
8
7/ Always ask: “Can you review what you just wrote?”
This one’s underrated.
Right after it writes code, just ask it to review and fix issues.
Feels like code + QA in one step.
This one’s underrated.
Right after it writes code, just ask it to review and fix issues.
Feels like code + QA in one step.
9
8/ Claude is slow… but precise
If you’re in a rush, it’ll frustrate you.
But if you want high-quality output and fewer hallucinations,
It’s one of the best I’ve used so far.
If you’re in a rush, it’ll frustrate you.
But if you want high-quality output and fewer hallucinations,
It’s one of the best I’ve used so far.
10
9/ Final tip: Claude works better when YOU think like a dev
The more context you give,
The better the results.
Treat it like a real teammate.
Not just a prompt machine.
The more context you give,
The better the results.
Treat it like a real teammate.
Not just a prompt machine.
11
TLDR:
Claude won’t magically build your app.
But if you learn how to work with it, it’s insanely powerful.
I’m still used to the Cursor workflow as I’ve shipped 18+ MVPs for clients with it.
But I’ve been testing Claude Code lately, and I’ve been loving it.
Stay tuned for a full comparison really soon.
Claude won’t magically build your app.
But if you learn how to work with it, it’s insanely powerful.
I’m still used to the Cursor workflow as I’ve shipped 18+ MVPs for clients with it.
But I’ve been testing Claude Code lately, and I’ve been loving it.
Stay tuned for a full comparison really soon.
12
I hope you've found this thread helpful.
If you have any questions, please feel free to ask below. :)
Like/Repost the quote below if you can:
If you have any questions, please feel free to ask below. :)
Like/Repost the quote below if you can: