If you’re not using /generate cursor rules, you’re leaving 80% of...

Here’s how to actually make it code like a real dev: 👇
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.
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.
Global Rules are your default settings.
They teach the AI how to behave across all projects.
Here’s how to create them in Cursor:
• Click ⚙️
• Go to “Rules for AI”
• Add your own preferences
Example rules:
• Write clean modular code
• Use async/await
• Ask before adding new libraries
• Comment complex logic
This is where the real magic happens.
Project Rules live inside your codebase under:
.cursor/rules/*.mdc
These files give Cursor project-specific knowledge like:
• What your app does
• Folder structure
• Auth setup
• Style and conventions
Most people create these rules reactively.
But there's a better way...
Don’t waste time copying someone else’s Cursor setup.
Use /generate cursor rules to create rules based on your own codebase.
It scans your project and figures out:
• Tech stack
• Folder layout
• Auth logic
• Code stylecture
•Code style
Custom rules > generic templates.
You don’t need 30+ rules.
You just need the essentials.
If you're building an MVP with 6–7 features, 5–6 well-written rules are enough to cover everything.
Keep it lean, not bloated.
Here are the only .mdc files I use in most MVPs:
• project-overview.mdc → what the app is, tech stack, key configs
• folder-structure.mdc → where things live
• supabase-auth.mdc → login/session details
• form-handling.mdc → how forms work
• api-routes.mdc → backend structure, error handling
• style-guide.mdc → code format, naming, commenting
Each rule has an attachment level:
• Always → load for every task
• Auto-Attach → loads by file type
• Agent-Requested → loaded when needed
• Manual → use when you want
Set core rules like tech stack and folder layout to Always.
Or to keep it simple, set all rules to Always (this is what I do)
Saves time and avoids confusion.
This prompt tells Cursor to first analyze your codebase, not blindly generate anything.
Once it’s mapped your tech stack, folder structure, and logic patterns, then (and only then) use /generate cursor rules to create the 6 rules that actually fit your project.
Once the analysis looks good, then I run /generate cursor rules.
Cursor is powerful but only when it knows what you’re building.
With the right rules:
• Cursor writes cleaner code
• Puts it in the right folders
• Needs less fixing
• Feels like a real dev, not a guessing bot
Set it up once.
Build faster forever.
If you want the exact prompt + full breakdown, it’s all in there.
Join now -> skool.com/ai-mvp-builders