Thanks for clarifying. This is a different setup than in the original post. Your rules are in ~/.cursor/rules (a global user directory), and that’s separate from project rules.
Here’s how it works today.
About ~/.cursor/rules/*.mdc. These files are only partially supported, and there are two gotchas that can make the list look empty:
- A file without
---frontmatter is silently ignored. If your.mdcstarts right away with# ...and doesn’t have a---block at the top, it won’t be picked up. Frontmatter fields likedescription,globs, andalwaysApplyare required. - Cursor searches upward from the opened project directory. So
~/.cursor/rulesis only found if the project itself is inside your home directory. If your project lives somewhere else, the global folder won’t be loaded. This is a known limitation we’re tracking, but there’s no ETA yet.
What works reliably for one set of rules for all projects. Use User Rules: Cursor Settings (not VS Code settings) > Rules > User Rules > New rule. This is plain text with no frontmatter or globs. It’s global and injected into every Agent chat no matter where the project is located. For tone and general preferences, this is the easiest path.
Why rules show up in Settings but not in Customize. Settings > Rules shows workspace scoped project rules plus User Rules. Use Cursor Settings (not VS Code settings), open the Rules tab.
Another option, if you want to keep everything in a personal repo and reuse it across projects, is to package it as a plugin with always-on rules. Another user did this and it worked well for them.
There’s also a thread about bringing file-backed user rules to parity with .cursor/rules here: File-backed / agent-editable User Rules (parity with project `.cursor/rules`)
Try moving the rule into User Rules, or add frontmatter to your .mdc, and let me know if it gets picked up.