├── .clinerules
├── LICENSE
└── README.md


/.clinerules:
--------------------------------------------------------------------------------
 1 | ## Additional Rules
 2 | 
 3 | - When a user requests additional rules, add them to the "Additional Rules" section of the `.clinerules` file in the project's root directory.
 4 | - Identify new rules by the prefix `RULE:` in user messages.
 5 | - For example, if the user writes `RULE: keep the README.md up to date`, append the rule as `- keep README.md up to date`.
 6 | - In contrary if a user writes `NORULE:` you remove the according line from the "Additional Rules" section.
 7 | - Persist these rules throughout the project lifecycle.
 8 | - Ensure that all added rules are clear, specific, and actionable.
 9 | - Format each rule as a separate bullet point.
10 | 


--------------------------------------------------------------------------------
/LICENSE:
--------------------------------------------------------------------------------
 1 | MIT License
 2 | 
 3 | Copyright (c) 2025 cannuri
 4 | 
 5 | Permission is hereby granted, free of charge, to any person obtaining a copy
 6 | of this software and associated documentation files (the "Software"), to deal
 7 | in the Software without restriction, including without limitation the rights
 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
 9 | copies of the Software, and to permit persons to whom the Software is
10 | furnished to do so, subject to the following conditions:
11 | 
12 | The above copyright notice and this permission notice shall be included in all
13 | copies or substantial portions of the Software.
14 | 
15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21 | SOFTWARE.
22 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | # Roo Code Dynamic Rules
 2 | 
 3 | This repository provides a streamlined way to dynamically update your project's rules as you work. Simply configure the `.clinerules` file in your project’s root directory to allow Roo Code to learn and adapt its behavior based on user interactions.
 4 | 
 5 | ## How It Works
 6 | 
 7 | When you need to modify Roo Code’s behavior, just prepend your instruction with `RULE:`. Roo Code automatically appends these directives to the `.clinerules` file under the **Additional Rules** section. This ensures that your project-specific rules are consistently maintained throughout the project lifecycle.
 8 | 
 9 | If you want to delete a rule simply use "NORULE: " followed by the rule you want to be forgotten.
10 | 
11 | ## .clinerules Configuration
12 | 
13 | Copy or add the following snippet to your project's `.clinerules` file:
14 | 
15 | ```
16 | ## Additional Rules
17 | 
18 | - When a user requests additional rules, add them to the "Additional Rules" section of the `.clinerules` file in the project's root directory.
19 | - Identify new rules by the prefix `RULE:` in user messages.
20 | - For example, if the user writes `RULE: keep the README.md up to date`, append the rule as `- keep README.md up to date`.
21 | - In contrary if a user writes `NORULE:` you remove the according line from the "Additional Rules" section.
22 | - Persist these rules throughout the project lifecycle.
23 | - Ensure that all added rules are clear, specific, and actionable.
24 | - Format each rule as a separate bullet point.
25 | ```
26 | 
27 | Now, whenever you want Roo Code to remember a new rule, simply type:
28 | ```
29 | RULE: run all tests at the end of a task
30 | ```
31 | or let it forget the rule by:
32 | ```
33 | NORULE: run all tests at the end of a task
34 | ```
35 | 
36 | Roo Code will then update your `.clinerules` file accordingly and add `- Run all Tests at the end of a task` to it and also follow this new rule.
37 | 
38 | ## License
39 | 
40 | This project is open source and available under the MIT License.
41 | ```
42 | 


--------------------------------------------------------------------------------