Rules

Custom rules for the project are shared alongside the code repository, helping project members work consistently and efficiently under common guidelines.

1. Log in to CodeArts Agent IDE as instructed in Quick Start.
2. Click in the upper right corner to open the global setting page.
3. In the navigation pane on the left, choose Skills and Rules. The Installed tab is displayed.
4. On the Project tab, click next to a rule.
5. Set parameters for creating a local project rule as instructed in Table 3.
   Figure 1 Creating a project rule
   

   Table 3 Parameters for creating a local project rule

   Parameter	Description
   Rule Name	Name of the rule to be created. Naming rules: Enter 1 to 64 characters. The following special characters are not allowed: \/:*?"<>|
   Applicable Scope	Application scope of a rule, that is, where the rule takes effect. Auto Apply: The rule applies to all chats by default and is automatically identified by the system. Manual Call: The rule does not take effect automatically. To use the rule, on the chat panel, enter # in the input box or click and choose Add Context. Then click Rules and select a rule from the list.
   Description	(Optional) Description of the rule. Enter up to 200 characters.
   Content	Rule content, instructing the agent to respond consistently and predictably in certain situations. Enter up to 50,000 characters.

6. Click OK to complete the rule creation.

   On the Project tab, view the created local project rule. It is stored in the ./.codeartsdoer/rule directory of the project root directory.

User rules are created according to personal habits and preferences. CodeArts Agent applies these rules consistently across all projects to deliver results tailored to user style.

1. Log in to CodeArts Agent IDE as instructed in Quick Start.
2. Click in the upper right corner to open the global setting page.
3. In the navigation pane on the left, choose Skills and Rules. The Installed tab is displayed.
4. On the User tab, click next to a rule.
5. Set parameters for creating a local user rule as instructed in Table 4.
   Figure 2 Creating a local user rule
   

   Table 4 Parameters for creating a local user rule

   Parameter	Description
   Rule Name	Name of the rule to be created. Naming rules: Enter 1 to 64 characters. Only letters, digits, underscores (_), hyphens (-), and periods (.) are allowed.
   Applicable Scope	Application scope of a rule, that is, where the rule takes effect. Auto Apply: The rule applies to all chats by default and is automatically identified by the system. Manual Call: The rule does not take effect automatically. To use the rule, on the chat panel, enter # in the input box or click and choose Add Context. Then click Rules and select a rule from the list.
   Type	Location where the rule is stored. If you select Local, the user rule is stored locally.
   Description	(Optional) Description of the rule. Enter up to 200 characters.
   Content	Rule content, instructing the agent to respond consistently and predictably in certain situations. Enter up to 50,000 characters.

6. Click OK to complete the rule creation.

   On the User tab, view the created local user rule. It is stored in the %USERPROFILE%/.codeartsdoer/rule directory.

CodeArts Agent rules are compatible with the AGENTS.md file. You only need to place the AGENTS.md file into the corresponding directory, and CodeArts Agent will automatically recognize and apply the rules defined in the file.

The following describes how to create a project AGENTS.md to customize rules and their invocation effects.

1. Create AGENTS.md in the project root directory in either of the following ways:
   • Local creation: Locate the target project folder on the local machine. Create a file named AGENTS.md in the root directory of the project.
   • Creation on CodeArts Agent: Log in to CodeArts Agent IDE as instructed in Quick Start. In the explorer, locate the target project. Create a file named AGENTS.md in the project directory.

   Example configuration of AGENTS.md:

   # Project Agent Code of Conduct
   ## 1. Scope Declaration
   This rule takes effect only for chats within the current project context.
   ## 2. Core Response Constraints
   - Structured expression: Responses must adopt a clear hierarchical structure (such as lists, headings, and bold text) to avoid large blocks of unformatted text. The logic needs to progress step by step, with key points highlighted.
   - Factual rigor: Fabricating uncertain information is strictly prohibited. For professional domain content, accuracy must be ensured. If information is missing, explicitly state "unable to confirm" instead of making guesses.
   - Tone and style: Keep the tone professional yet friendly, and appropriately use relaxed and natural expressions.
   ## 3. Mandatory Requirements
   After each response ends, the following fixed closing statement must and can only be added, and no other content shall be modified, omitted, or added:
   The answer is complete. If you have any other questions, feel free to let me know at any time.

2. Initiate a chat in the agent to verify the output effect.

   The output of the agent strictly complies with the style requirements defined in Core Response Constraints. In addition, the standard closing statement "The answer is complete. If you have any other questions, feel free to let me know at any time." is automatically appended to the end of the session. This indicates that the custom rules in AGENTS.md have been successfully loaded and taken effect.

   Figure 3 Custom rules loaded and taken effect