Fix
Cursor Ignoring My Rules? How to Fix .cursor/rules
By The Field Academy Editorial TeamUpdated
Cursor ignores rules when they aren't scoped to the files you're editing (wrong/missing globs), when they live in the deprecated root .cursorrules instead of .cursor/rules/*.mdc, or when they're so long or contradictory they get diluted. Tighten the glob, migrate to .mdc, and keep each rule short and specific.
Why is Cursor ignoring my rules?
- The rule's globs don't match the files you're editing (or there are none).
- You're using the deprecated `.cursorrules` file instead of
.cursor/rules/*.mdc. - The rule is too long or contradictory, so it's diluted.
- Malformed `.mdc` frontmatter.
How do I make Cursor follow my rules?
- 1Move rules to *`.cursor/rules/.mdc`** (one concern per file).
- 2Set `globs` so the rule loads for the files it's about.
- 3Shorten the rule to concrete do/don't lines with an example.
- 4Verify the frontmatter is valid; reload Cursor.
Frequently asked questions
Is .cursorrules deprecated?
The single-file .cursorrules is legacy. Use .cursor/rules/*.mdc files, which support per-path scoping via globs and are what current Cursor expects.
How do I scope a Cursor rule to certain files?
Add a globs array in the rule's .mdc frontmatter (e.g. ["**/*.tsx"]). The rule then loads only when you work in matching files.
Sources & last verified
Cursor ships frequently. Facts verified against primary sources on June 15, 2026.