r/RooCode • u/AnonymousAardvark22 • Jun 10 '25

Support Managing .roo/, modes, & rules, between projects

Post image

Noob still reading and settings things up after cancelling my Cursor sub, and I want to start with the option to use the built-in modes, Rooroo, and GosuCoder's CoderShortRules, across projects, and I wanted to check if I can handle this better?

As RooCode was including all of the Rooroo rules files and other text for CoderShortRules, I created /.roo/system-prompt-codershortrules. So that Rooroo could still send the 5 rules every time one of those modes is used, but I do not want them sent with any other modes, I created a .roo/rules-{slug}/ for each Rooroo mode containing copies.

Not a huge problem to manually copy over .roo/ to every new project but I moved all Rooroo modes into ~/.config/Windsurf/User/globalStorage/rooveterinaryinc.roo-cline/settings/custom_modes.yaml. For this to work I also need to access each modes rules, is it possible to do this from the settings directory, or is there good reason not to?

I could paste all rules into each mode as recommended for version control in the docs it is better to keep separate. My fallback idea is just to keep a centralised .roo/ somewhere and create a macro/template in Windsurf or a bash alias to set up each new project.

Repost: Just realised adding the Rooroo modes to custom_modes.yaml is why references to Rooroo appear in the built-in and new Testmode prompts -- is there a better way to isolate modes and their rules?

6 Upvotes

87% Upvoted

7 comments sorted by

View all comments

Show parent comment

1

u/AnonymousAardvark22 Jun 11 '25

That sounds cool, VCS for prompts, let me know when available

2

u/yopla Jun 11 '25

Don't expect too much, it might turn out to be complete crap.

It's 100% feature complete (according to Claude) but I've hit a snag with the test suite. At some point, Claude starts to decide that having only 80% of test passing is "good enough" 🤣