Fix: Cursor Ignores Your .cursorrules File
Quick Answer
Verify the file is named exactly .cursorrules (no extension) in your project root. Restart Cursor after creating or editing it. Keep rules concise — under 500 words works best.
Quick Fix Summary
| Issue | Ignoring .cursorrules |
| Fastest fix | Check file name and location |
| Use this page if | Cursor generates code that contradicts your .cursorrules |
Symptoms
- !Cursor generates code that contradicts your .cursorrules
- !AI uses wrong styling approach despite rules specifying Tailwind
- !Rules are ignored in Composer but work in chat
- !New conversations don't pick up .cursorrules
Step-by-Step Fix
Check file name and location
The file must be named exactly .cursorrules (not .cursorrules.txt, not cursorrules) and placed in your project root directory (same level as package.json).
Keep rules concise
Long .cursorrules files get truncated. Keep it under 500 words. Focus on: tech stack, file conventions, coding patterns, and explicit do/don't rules.
Restart Cursor
After creating or editing .cursorrules, restart Cursor (Cmd+Shift+P > Developer: Reload Window) to ensure it picks up the changes.
Reinforce in prompts
For critical rules, repeat them in your prompt: 'Remember: use App Router only, as specified in .cursorrules.' Belt and suspenders.
Frequently Asked Questions
Yes, but Composer sometimes prioritizes the explicit prompt over .cursorrules when they conflict. Be consistent between your rules and prompts.
No, only the one in the project root is read. But you can organize rules by section within that file.
Related
Weekly Signals
Get the next fix, switch, or warning before it hits your build.
Join builders getting the community signals, fix patterns, and tool shifts that matter before they show up everywhere else.
Follow the signals →