Project Rules: ability to have personal .cursor/rules files

Feature Requests
1

Hi folks!

Loving the new .cursor/rules folder approach so far. I’m currently implementing it in a shared codebase with many different roles. In our case, we would love to commit a general set of rules to our repos, but then still allow folks to have untracked personal rules.

I was thinking, it would be ideal to be able to have the standard .cursor/rules for files that will be committed to the repository and then a .cursor/rules/local or even .cursor/rules/file.mdc.local so we can filter things out in our .gitignore a little more easily.

This would supercharge the approach and not require granular file-level ignoring!

Alternatively if anyone can think of a sustainable way to achieve this now, I’m all ears!

2

I guess you could create a

.cursor/rules/joe-rules

For yourself and then have an entry in the .gitignore for that, so that it didn’t get uploaded.

1 Like
3

That’s a great suggestion @futuretech and it’s what I’m currently doing.

One use-case I like is similar to things like docker with it’s .env files. You can have a .env.local file to override locally. This would be a really nice way to have a customised version of a repo-based rule.

None of this is a deal breaker, but it could be a lovely feature.