I stopped using Cursor and switched to Claude Code. Best decision...
Prajwal Tomar@PrajwalTomar_
59 views
Jul 12, 2025
~3 min read
Advertisement
1
I stopped using Cursor and switched to Claude Code.
Best decision I’ve made in a while.
Here’s why I’m not going back (and the tips saving me 10+ hours every week) ↓
Best decision I’ve made in a while.
Here’s why I’m not going back (and the tips saving me 10+ hours every week) ↓
2
1/ Cursor kept messing up my bigger projects
Whenever I worked on large codebases, Cursor started breaking.
Context got confusing. Code suggestions didn’t make sense.
I was fixing AI mistakes more than building.
It got frustrating.
Whenever I worked on large codebases, Cursor started breaking.
Context got confusing. Code suggestions didn’t make sense.
I was fixing AI mistakes more than building.
It got frustrating.
3
2/ The biggest realization
Cursor and Windsurf are just wrappers around Claude.
Claude Code is built by the people who made the model.
That’s like using the original engine instead of a copy.
Cursor and Windsurf are just wrappers around Claude.
Claude Code is built by the people who made the model.
That’s like using the original engine instead of a copy.
4
3/ It actually works better
Here’s what I noticed right away:
- Keeps context clean
- Doesn’t give up halfway
- Understands my codebase
- Gives real solutions, not just guesses
It feels like it gets what I’m trying to build.
Here’s what I noticed right away:
- Keeps context clean
- Doesn’t give up halfway
- Understands my codebase
- Gives real solutions, not just guesses
It feels like it gets what I’m trying to build.
5
4/ Use planning mode every time
Shift+Tab → Describe exactly what you want → Claude maps out everything → Review → Execute
Don’t skip this. Always plan as much as possible. More time you spend here, less time you will spend later fixing the mistakes.
Shift+Tab → Describe exactly what you want → Claude maps out everything → Review → Execute
Don’t skip this. Always plan as much as possible. More time you spend here, less time you will spend later fixing the mistakes.
6
5/ Real example: Stripe webhook
Last week I had to set up Stripe webhooks in a Next.js app.
Cursor: tried 3 times, still buggy
Claude Code: One prompt → perfect code → done in 15 minutes
It just worked.
Last week I had to set up Stripe webhooks in a Next.js app.
Cursor: tried 3 times, still buggy
Claude Code: One prompt → perfect code → done in 15 minutes
It just worked.
7
6/ Always set up a CLAUDE.md file first
This is your source of truth.
Include:
- Goal of the project
- Tech stack
- Folder structure
- App flow
Claude keeps referring to this in every prompt. Without it, it forgets fast.
This is your source of truth.
Include:
- Goal of the project
- Tech stack
- Folder structure
- App flow
Claude keeps referring to this in every prompt. Without it, it forgets fast.
8
7/ Switch models to save time + tokens
Use /model opus for building and planning complex features.
Switch to /model sonnet for majority of the building and to save tokens.
Use /model opus for building and planning complex features.
Switch to /model sonnet for majority of the building and to save tokens.
9
8/ A workflow that you can experiment with
- Claude Code for building the MVP
- Cursor as your code editor (lets you use best of both worlds)
- Lovable for building 70/80% of the MVP
Simple and super effective.
- Claude Code for building the MVP
- Cursor as your code editor (lets you use best of both worlds)
- Lovable for building 70/80% of the MVP
Simple and super effective.
10
9/ Use /clear more often
Don’t carry 100 messages worth of context.
After every major feature, I run /clear.
Less confusion, fewer hallucinations, cleaner results, and you will save tokens.
Don’t carry 100 messages worth of context.
After every major feature, I run /clear.
Less confusion, fewer hallucinations, cleaner results, and you will save tokens.
11
10/ Why Claude Code feels smarter
- Remembers longer conversations
- Tests the code it writes
- Handles multiple files better
- Fixes errors automatically
Way less stress, way more output.
- Remembers longer conversations
- Tests the code it writes
- Handles multiple files better
- Fixes errors automatically
Way less stress, way more output.
12
11/ Use “UltraThink” for complex coding prompts
If you’re stuck on a tough problem, try adding the word UltraThink to your prompt.
It tells the model to go all in. Deeper reasoning, more edge cases, cleaner logic.
Think of it like flipping a switch to full power.
If you’re stuck on a tough problem, try adding the word UltraThink to your prompt.
It tells the model to go all in. Deeper reasoning, more edge cases, cleaner logic.
Think of it like flipping a switch to full power.
13
12/ Something bigger is happening
When the model makers build the tool, it’s always better.
Everyone else just adds a wrapper on top.
If you’re early to this, you win.
When the model makers build the tool, it’s always better.
Everyone else just adds a wrapper on top.
If you’re early to this, you win.
14
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_
I stopped using Cursor and switched to Claude Code.
Best decision I’ve made in a while.
Here’s why I’m not going back (and the tips saving me 10+ hours every week) ↓
Best decision I’ve made in a while.
Here’s why I’m not going back (and the tips saving me 10+ hours every week) ↓
15
You’re probably going to forget this.
And all the other AI dev workflows I’ve shared this week.
So I started a weekly newsletter
Quick recap every Sunday on AI dev, vibe coding, and MVP building.
Subscribe here:
aimvpweekly.beehiiv.com
And all the other AI dev workflows I’ve shared this week.
So I started a weekly newsletter
Quick recap every Sunday on AI dev, vibe coding, and MVP building.
Subscribe here:
aimvpweekly.beehiiv.com