How I Make Cursor Write Perfect Code Every Time This thread breaks...
Prajwal Tomar@PrajwalTomar_
58 views
Jun 19, 2025
~3 min read
Advertisement
1
How I Make Cursor Write Perfect Code Every Time
This thread breaks down how I generate rules that make Cursor code cleaner, faster, and way more accurate ↓
This thread breaks down how I generate rules that make Cursor code cleaner, faster, and way more accurate ↓
2
TLDR:
• Set Global Rules for coding style
• Generate Project Rules using /generate cursor rules
• Use 5–6 custom .mdc files per MVP
• Attach rules as “Always”
• Let Cursor code with real context
• Set Global Rules for coding style
• Generate Project Rules using /generate cursor rules
• Use 5–6 custom .mdc files per MVP
• Attach rules as “Always”
• Let Cursor code with real context
3
1/ Why Cursor Rules Matter
Most people think Cursor just writes code for you.
But the truth is: the AI only works well when you train it right.
Cursor Rules are how you do that.
They tell the AI how to behave, what your project is about, and how you like your code written.
Most people think Cursor just writes code for you.
But the truth is: the AI only works well when you train it right.
Cursor Rules are how you do that.
They tell the AI how to behave, what your project is about, and how you like your code written.
4
2/ Two Types of Rules
There are two kinds of Cursor Rules:
• Global Rules → apply to all projects
• Project Rules → specific to one project
Both are powerful.
And you need to use them together to make Cursor work better.
There are two kinds of Cursor Rules:
• Global Rules → apply to all projects
• Project Rules → specific to one project
Both are powerful.
And you need to use them together to make Cursor work better.
5
3/ Setting Up Global Rules (User Rules)
Global Rules are your default dev preferences.
Here’s how to create them in Cursor:
•Click ⚙️
•Go to “Rules for AI”
•Add your preferences
Examples:
• Write modular code
• Use async/await
• Ask before adding libraries
• Comment complex logic
Global Rules are your default dev preferences.
Here’s how to create them in Cursor:
•Click ⚙️
•Go to “Rules for AI”
•Add your preferences
Examples:
• Write modular code
• Use async/await
• Ask before adding libraries
• Comment complex logic
6
4/ Setting Up Project Rules with .mdc Files
This is where the real magic happens.
Project Rules live at:
.cursor/rules/*.mdc
They give Cursor your app’s unique context:
• What the app does
• Folder structure
• Auth setup
• Style and conventions
This is where the real magic happens.
Project Rules live at:
.cursor/rules/*.mdc
They give Cursor your app’s unique context:
• What the app does
• Folder structure
• Auth setup
• Style and conventions
7
5/ The Strategy That Actually Works
Most people create these rules reactively.
Here’s what I do instead:
→ Use /generate cursor rules
It scans your codebase and auto-generates custom rules like:
• Tech stack
• Folder layout
• Supabase or auth logic
• Styling conventions
Custom > generic every time.
Most people create these rules reactively.
Here’s what I do instead:
→ Use /generate cursor rules
It scans your codebase and auto-generates custom rules like:
• Tech stack
• Folder layout
• Supabase or auth logic
• Styling conventions
Custom > generic every time.
8
6/ Don’t Overdo It
You don’t need 30+ rules.
If you’re building a lean MVP with 6–7 core features, 5–6 well-written .mdc files are enough.
Keep it simple. Keep it readable. Keep it useful.
You don’t need 30+ rules.
If you’re building a lean MVP with 6–7 core features, 5–6 well-written .mdc files are enough.
Keep it simple. Keep it readable. Keep it useful.
9
7/ The 6 Most Useful Project Rules
These are my go-to .mdc files for most MVPs:
• project-overview.mdc → app purpose, stack, config
• folder-structure.mdc → file layout
• supabase-auth.mdc → login/session handling
• form-handling.mdc → how forms are built
• api-routes.mdc → route patterns, error logic
• style-guide.mdc → naming, format, comments
These are my go-to .mdc files for most MVPs:
• project-overview.mdc → app purpose, stack, config
• folder-structure.mdc → file layout
• supabase-auth.mdc → login/session handling
• form-handling.mdc → how forms are built
• api-routes.mdc → route patterns, error logic
• style-guide.mdc → naming, format, comments
10
8/ How to Attach the Rules
Each rule has an attachment level:
• Always → always loaded
• Auto-Attach → based on file type
• Agent-Requested → only if needed
• Manual → load it yourself
I usually set all core rules to Always.
It’s simpler. No confusion.
Each rule has an attachment level:
• Always → always loaded
• Auto-Attach → based on file type
• Agent-Requested → only if needed
• Manual → load it yourself
I usually set all core rules to Always.
It’s simpler. No confusion.
11
9/ Final Takeaway
Cursor isn’t magic until it knows what you’re building.
With the right rules:
• Cleaner code
• Fewer rewrites
• Smarter file placement
• Feels like you’re working with a real dev
Set it up once.
Build faster forever.
Cursor isn’t magic until it knows what you’re building.
With the right rules:
• Cleaner code
• Fewer rewrites
• Smarter file placement
• Feels like you’re working with a real dev
Set it up once.
Build faster forever.
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: