feat: move cursor rules to .cursor/rules, add metadata #474
+30
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this do?
.cursorrules
. Other rules are found inprompts/
. The new way of defining rules is outlined on the Cursor context rules documentation, and defines rules under.cursor/rules/
. With the new way of defining rules, it is easy to define globs and when rules should be used by Agents.Why did you do this?
Defining rules this way gives developers more flexibility in using and creating rules as the new way of creating rules through Cursor will create them in


.cursor/rules/
, reducing project clutter. Additionally, rules are now visible from the contextRules
selection.Who/what does this impact?
Since this update has been here for some time now, users should be acquainted with the new way of defining and using rules. Otherwise, this should not affect any current users.
How did you test this?
Each rule was ran to accomplish the same goal using the current
prompts/
and new.cursor/rules/
.