Global .cursor/rules directory

Ideas Feature Requests
22

Wanted to update y’all on what is working for me.

If you want “global” rules, the easiest way to do it right now is to:

  1. create a dedicated rules repo.
  2. 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.

24

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.

1 Like