I’m seeking some clarification on the project rules system and how Cursor discovers and applies .mdc files.
My question is: Is it a strict requirement for all project rule files (.mdc) to be located inside the .cursor/rules directory, regardless of their Rule Type?
I’ve been thinking about the different rule types, and it seems plausible that some might not need to be in that specific directory. For instance, a rule with alwaysApply: true feels like it should apply to the entire project context constantly. My initial thought was that perhaps such a file could live in the project root or another config directory and still be picked up by Cursor.
However, I’ve noticed that the official documentation consistently reference the .cursor/rules path when talking about project rules.
Could someone clarify if placing rules in .cursor/rules is:
A mandatory requirement for Cursor’s file discovery and scoping mechanism?
Or, a strong recommendation for project organization, with other locations being technically possible?
Any insights on the underlying mechanism would be greatly appreciated!