I’ve built 12+ MVPs for clients using Cursor. Here are 11 tips to...

If you’re a beginner, this thread has everything you need to get started and make Cursor work for you – thread below.
Every great project starts with a solid plan.
Use ChatGPT to create:
- PRDs
- Database designs
- User Journey
- UI screens
- Task Breakdown
- Branding Guidelines
Save these as .md files in Cursor. This keeps everything consistent and accessible.
Pro Tip: Use ChatGPT o1 for this. If you don't have the access, 4o works well too.
Cursor shines when you give it a base to build on.
Use tools like Lovable or V0 to generate initial UI code, then move to Cursor for:
- Refining the UI
- Adding complex logic
This combo improves efficiency and reduces rework.
Cursor works best when you guide it.
Set project-specific rules in a .cursorrules file, like:
- Preferred libraries or frameworks
- Naming conventions
- Code style
This helps Cursor align with your coding standards.
Sync official docs (Next.js, Supabase, etc.) into Cursor.
Reference popular libraries using @LibraryName, or add your own using @Docs → Add new doc.
Need up-to-date information?
Use the @Web feature to let Cursor search the internet for the latest solutions and fixes.
This feature is perfect for handling changes in libraries or APIs.
Whenever Cursor generates good code, save it for future reference.
Store snippets in .md files, so Cursor can reuse them across your project or even in new ones.
Use @Codebase or ⌘ Enter to ask questions about your codebase. Cursor will search your codebase to find relevant code to your query.
Cursor makes editing a breeze.
Select a block of code and press ⌘ K to describe the changes you need.
Or, generate new code without selecting anything.
Pro Tip: Always describe the outcome clearly. Cursor thrives on detailed instructions.
Not happy with your UI?
Screenshot it and upload it to Cursor. It will analyze the design and replicate the design. It's not perfect but get's the job done after 1-2 more prompts.
Example Prompt:
"Make this hero look exactly like the attached image."
Learning while building? Cursor can explain code like a tutor.
Example Prompt:
"Explain this code like I’m a beginner. What does each function do, and how does it connect to the database?"
Cursor’s explanations will help you improve while building.
When debugging, provide Cursor with logs and a clear explanation of the problem.
Example Prompt: "Here’s the error: [error details]. Track the data flow in this function and find where the issue occurs. Don’t code for now - just tell."
Once you identify the root cause, ask Cursor to fix it.
Cursor is only as powerful as the context you give it.
By following these 11 steps, you’ll:
- Build faster
- Debug smarter
- Reduce mistakes
Mastering Cursor isn’t just about coding, it’s about knowing how to use AI effectively.
Which of these tips will you try first? Let’s discuss 👇

Writing PRDs used to take forever, until I discovered this workflow that’s fast AND delivers top-tier results.
Here’s how I do it:
1. Start by throwing everything the client shared into ChatGPT.
2. Ask it to list core features + nice features.
3. Use the MoSCoW framework to prioritize the MVP features.
4. Take the refined list along with a description of the MVP to ChatPRD to finalize the PRD.
After 4-5 prompts, I’ve got a polished, detailed PRD ready to go.
I’ll be sharing the PRD structure as well in a few hours. Stay tuned!

1. Introduction: Explain the problem you’re solving and the vision for the product. This sets the context for everyone involved.
2. Objectives & Goals: Highlight the main outcomes the product should achieve. What’s the core purpose?
3. Target Users & Roles: Identify who will use the product (e.g., clients, admins) and what actions they need to perform.
4. Core Features for MVP: List the must-have features to deliver value quickly and validate the product.
5. Future Scope: Outline features that can be added later. This helps clients think beyond the MVP without overloading the first phase.
6. User Journey: Map out how users interact with the product step by step. Cover all roles for complete clarity.
7. Tech Stack: Define the tools, frameworks, and APIs you’ll use to build the product.
You don’t need to overcomplicate things. Just focus on Core Features for MVP and Future Scope to ensure the client has a clear roadmap. That’s all you need to get started!