Hey all,
I’m trying to understand what is the best practice you found when writing rules for your team.
My idea was to take a few developers and tell them to write rules as they progress with their tasks to get the most efficient, problem-solving rule guidelines we can get.
This is all fine and dandy, but there are a few obstacles i want to jump over to make sure we’re the most efficient we can be.
-
How do they actually write the rules? when asking Cursor to
/generate Cursor rules
it creates a random file in the./cursor/rules
folder and i want it to be more specific, technology/repo level; should i grant them a base rule that explain Cursor how to generate rules to begin with? and if so what was your best practice approaching this? -
If you tried writing rules in tandem with multiple teammates, did you find a specific amount of writers to be ideal?
-
If you have any tips, rules (no pun intended) or any other best practice you think i should know of, please enlighten me
Thanks!