Bookmark this if you're just getting started with Cursor We’ve built 17+ MVPs using it and finally cracked the most efficient way to use it without breaking things. If you’re a beginner, this thread has everything you need to get started and make Cursor work for you ↓
1. Plan before you code A messy plan leads to messy prompts. Use ChatGPT to generate: - A simple PRD with your app goals, user flows, and features - Your database schema and table relationships - A color palette and typography reference - Tech stack outline (e.g. Supabase, Stripe, Tailwind, etc.) Pro tip: Save all this as .md files inside your Cursor repo. That way, you and the AI stay aligned on scope from day one.
2. Start with a foundation (don’t go blank) Cursor is powerful, but it performs better with some structure. Use tools like: - UX Pilot to create styled screen mockups - Or Lovable/Bolt for fast UI generation Once you have your layout, refine it in Cursor.
3. Set up Project Rules (replace .cursorrules) Don’t skip this. With Project Rules, you can: - Apply scoped instructions (e.g. “Only use Tailwind classes in .tsx files”) - Define naming conventions and preferred patterns - Sync rules with your GitHub repo for team use Set these up early. It’s how you make AI behave like a real teammate. A detailed post on setting up Cursor is a Right is coming soon. Stay tuned.
4. Save reusable code in Notepad Cursor’s Notepad is your AI memory. Store: - Auth flows (e.g., Supabase signup/login) - Stripe checkout setup - Common fetch/query patterns - Validation logic and Zod schemas
5. Split your work with Chat Tabs Cursor 0.48 introduced tabs, massive for multitasking. I use: - One tab for planning (talking to the AI about structure) - One tab for fixing bugs or iterating This avoids losing context across different conversations.
6. Automate with MCP (Model Context Protocol) MCP lets Cursor do more than code: - Run scripts to clean your repo - Automate database setup (like Supabase table creation) - Pull research from tools like Perplexity or Docs
8. Save working code in .md files When Cursor gives you a great response: - Save it in a markdown file like auth-flow(.)md, deployment(.)md, etc. - Reuse later when building similar apps - Cursor will refer to it for future prompts too
9. Use YOLO Mode (but wisely) YOLO Mode = no confirmation before running commands. Use it to: - Format files - Generate boilerplate - Run scripts fast Watch Out: Use on a separate Git branch. It will overwrite files instantly.
10. Fix UI with Screenshots Cursor supports visual input. Just: - Take a screenshot of the broken UI - Drag it into the chat - Prompt: “Fix this spacing and align it with the design system” Much faster than explaining with words.
11. Learn while building Ask Cursor to: - Explain code like you’re a beginner - Walk through step-by-step logic - Suggest better patterns This is how I upskilled while working on real MVPs.
12. Use code templates Why start from scratch? Use Vercel’s official templates for: - Next.js apps - Auth flows - Stripe payments - Blog + CMS setup Link: https://vercel.com/templates/n...
13. New in Cursor 0.48.x Take advantage of these new features: - Custom modes (beta) allow you to compose new modes with tools and prompts that fit your workflow. - Chat Tabs: Run parallel conversations without losing context - Ask mode now has access to all search tools by default, so the @Codebase tool has been removed. - Sound Notifications: Get notified when Cursor is done thinking Set these up to make Cursor feel even more personal
TLDR: - Plan your build with .md docs - Use Project Rules to control AI - Review everything with async reviews (use CodeRabbit) - Save and reuse smart responses - Use tabs and screenshots for better context - Combine with tools like MCP and Notepad for superpowers Let me know if you want a walkthrough video of this and I’ll record one soon. Build fast. Stay in control.