If you want “global” rules, the easiest way to do it right now is to:
create a dedicated rules repo.
sit it beside project repos in a multi-root workspace.
Teams that don’t want your rules in their root directly can import them into say the docs/ directory as a submodule and then symlink it to the root cursor directory.
What’s nice about this approach is that you could have a main branch for all default rules, and then you can also have variants as branches per user, team, or project. so team-cursor and team-foo could have modified a subset of the rules from main to satisfy their needs. Crowdsourcing refinements is just a matter of pushing PRs to the main rule set.
I encountered a similar problem. Our entire company needs to use public cursor dotfiles, not just rules, but also commands. We simply copied the public cursor directory to $HOME/.cursor so that everyone and every project would have all of these.
i put my workaround for this on a related feature request. i am one of at least two people in my org that blindly tried dumping mdc files into ~/.cursor/rules expecting exactly this behavior. glad we’re not alone!
I’m managing the ‘global rules’ in ‘C:\Users\PC.cursor\rules’ and ‘Juntion’ them to the project directories. This works quite well, you can try it.
Open PowerShell and run the following two commands in the project root directory: New-Item -ItemType Directory -Force “.cursor” New-Item -ItemType Junction -Path “.cursor\rules” -Target “C:\Users\PC.cursor\rules”