And suddenly, building with Cursor felt calm again.
Here’s how I ship faster without burning out ↓
Reposting this thread because many of you didn’t catch it the first time. It’s worth reading.
-------
1/ The workflow (quick summary)
This is the system that works:
- Plan clearly (PRD) @ChatGPTapp
- Break it down with TaskMaster
- Execute one task at a time in @cursor_ai
- Review everything with @coderabbitai
Let’s go deeper ↓
2/ “Vibe coding” was a trap
I’d give a vague prompt like “Build a landing page” and Cursor would go wild.
Sure, things moved fast, but most of my time went into cleaning up the mess:
- Messy logic
- Hallucinated features
- Bugs I never asked for
It wasn’t fun anymore. It was firefighting.
3/ The root problem: Agent Chaos
When you give a high-level goal, your Cursor agent starts guessing.
It assumes structure, state, styles, everything.
You end up with bloated, unmaintainable code.
Fast now, painful later.
You’re not building, you’re babysitting.
4/ The mindset shift that changed everything
I stopped prompting like a user.
Started directing like a product engineer.
It’s not “can you build this?”
It’s “here’s what to build, exactly how I want it.”
Cursor became my dev. I became the architect.
5/ My “Calm Coder” Workflow
Here’s what I follow every time:
1. Plan → Write a clear 1-page PRD 2. Break down → Use TaskMaster in Cursor to list exact tasks 3. Execute → Feed ONE task at a time to Cursor 4. Review → Use CodeRabbit to double-check quality
Clean. Repeatable. Fast.
6/ Step 1: The 1-Page PRD
Don’t jump into Cursor yet.
Start by writing a simple 1-page PRD that explains what you’re building and why.
If you’re using lovable to build apps, read this first
This is everything I wish I knew before starting ↓
Reposting this thread because many of you didn’t catch it the first time. It’s worth reading.
-------
1. Nail your first prompt
I always start inside my custom GPT, SnapPrompt, and get the full prompt for my landing page first.
This includes layout, structure, typography, and design style. I just copy-paste that into Lovable with a design reference attached and it gives me a clean starting point.
2. Always prep your technical docs before starting in Lovable
Don’t dive in blind.
Have your DB design, UI Dev plan, MVP plan, and implementation plan ready.
Keep it simple, generate them during the planning phase using GPT or Gemini.
Then just paste them as .md files into Lovable.
That way, Lovable has full context about your product from the start.
I’ve used Claude Code for 100+ hours building MVPs.
Most developers are missing the best features.
Here are 10 tricks that will change how you build ↓
1/ Use planning mode before EVERYTHING
- hit Shift+Tab twice to enter planning mode
- I plan every feature here first
- no code gets written until the plan is solid
- saves me hours of refactoring later
2/ Create custom commands for repetitive tasks
- Make a /claude/commands folder
- Create markdown files for common workflows
I have commands for:
- Security audits
- Documentation generation
- Code reviews