So it seems Cursor unrolled one more update to their rules system, but I still can’t visualize the difference between their rules system and me just creating a loose rules.md file and pinging it to the AI.
What am I missing here?
If you have a random rules.md file alone how do you assure that Cursor reads that file when you open a new chat context window?
I have an “official” Cursor rules file - all it says is “Always refer to the Readme file.”
So, the only difference really is that the chat picks up automatically upon starting new chats? It’s just a shorthand for like, typing @rules.md manually?
I’m not saying this has no value, specially when you’re working in a multi-people environment - just making 100% sure there’s no invisible functionality I am missing.
I believe you can more reliably refer to Metadata, path scoping, file references, and auto-attach features in an official cursor rules folder.
If that is not relevant to you and you are willing to load it into context each time, then I have not found any differences.
Or you can set the official rules folder to always refer to your README file so you do not have to manually bring the README into context each time.
1 Like
I use markdowns. Cursor rules has always seemed broken to me . Hard to say as long as cursor hides what context actually gets to the model
2 Likes
Using markdown, too. There are some conveniences with Cursor rules et al, but share the same feeling as you - don’t know if there’s any magic under the hood that a plain a markdown wouldn’t solve.
1 Like
Cursor rules have “Rule Type” which can conditionally add rules to a chat.
This lets us define rules and the conditions under which to apply them and then not have to worry about attaching some rules.md file to each message manually. Saves time and effort when working with large codebases and complex rules.
Official Docs: Cursor Rules
1 Like
The rule mechanism is much too esoteric to actually use it.
For the editor itself: the main reason we have a custom editor is that you can @files! Also an easy way for you to switch between rule types.
We agree that it’s definitely in its most basic form, and looking forward to keep making improvements.
For rules in general:
there’s different rule types as @ed1432 mentioned! and we manage them for you based on your rule type pick. that way, you don’t have to do manual rule management (unless you want to! and you can still @-mention rules to highlight to the agent you really encourage its use)
2 Likes
One is a rule to which the cursor reacts *.mdc, the other is a markdown *.md that you can use as a template in connection with rules, for example. The main difference is the scope, otherwise Cursor would interpret every markdown as a rule.
You are lost as much as I am at the beginning I will explain to you the global course rules apply to all ai behavior done in all projects the course rules directory in your project only applies to your own project Got it now