RooCodeInc
diff --git a/‎docs/basic-usage/using-modes.md‎
Lines changed: 8 additions & 8 deletions b/‎docs/basic-usage/using-modes.md‎
Lines changed: 8 additions & 8 deletions
diff --git a/‎docs/features/custom-modes.mdx‎
Lines changed: 33 additions & 54 deletions b/‎docs/features/custom-modes.mdx‎
Lines changed: 33 additions & 54 deletions
@@ -19,11 +19,11 @@ Four ways to switch modes:
 
 1. **Dropdown menu:** Click the selector to the left of the chat input
 
-   <img src="/img/modes/modes.png" alt="Using the dropdown menu to switch modes" width="400" />
+   <img src="/img/using-modes/using-modes.png" alt="Using the dropdown menu to switch modes" width="400" />
 
 2. **Slash command:** Type `/architect`, `/ask`, `/debug`, `/code`, or `/orchestrator` in the chat input
 
-   <img src="/img/modes/modes-1.png" alt="Using slash commands to switch modes" width="400" />
+   <img src="/img/using-modes/using-modes-1.png" alt="Using slash commands to switch modes" width="400" />
 
 3. **Toggle command/Keyboard shortcut:** Use the keyboard shortcut below, applicable to your operating system. Each press cycles through the available modes in sequence, wrapping back to the first mode after reaching the end.
 
@@ -35,7 +35,7 @@ Four ways to switch modes:
 
 4. **Accept suggestions:** Click on mode switch suggestions that Roo offers when appropriate
 
-    <img src="/img/modes/modes-2.png" alt="Accepting a mode switch suggestion from Roo" width="400" />
+    <img src="/img/using-modes/using-modes-2.png" alt="Accepting a mode switch suggestion from Roo" width="400" />
 
 ## Built-in Modes
 
@@ -54,10 +54,10 @@ Four ways to switch modes:
 | Aspect | Details |
 |--------|---------|
 | **Name** | `❓ Ask` |
-| **Description** | A knowledgeable technical assistant focused on answering questions without changing your codebase |
+| **Description** | A knowledgeable technical assistant focused on providing thorough and complete answers. It's less inclined to switch to implementing code unless explicitly requested and may use diagrams for clarification. |
 | **Tool Access** | Limited access: `read`, `browser`, `mcp` only (cannot edit files or run commands) |
 | **Ideal For** | Code explanation, concept exploration, and technical learning |
-| **Special Features** | Optimized for informative responses without modifying your project |
+| **Special Features** | Optimized for detailed, informative responses, often using diagrams for clarity, without modifying your project. |
 
 ### Architect Mode
 
@@ -84,11 +84,11 @@ Four ways to switch modes:
 | Aspect | Details |
 |--------|---------|
 | **Name** | `🪃 Orchestrator` |
-| **Description** | A strategic workflow orchestrator (aka Boomerang Mode) that breaks down complex tasks and delegates them to specialized modes |
+| **Description** | A strategic workflow orchestrator (aka Boomerang Mode) that breaks down complex tasks and delegates them to specialized modes. Learn more about [Boomerang Tasks](/features/boomerang-tasks). |
 | **Tool Access** | Access to `read`, `browser`, `command`, `mcp`, and restricted `edit` (mode configuration files only: `.roomodes`, `custom_modes.json`) |
 | **Ideal For** | Managing multi-step projects, coordinating work across different modes, and automating complex workflows |
 | **Special Features** | Uses the [`new_task`](/advanced-usage/available-tools/new-task) tool to delegate subtasks to other modes. |
 
-## Custom Modes
+## Customizing Modes
 
-Create your own specialized assistants by defining tool access, file permissions, and behavior instructions. Custom modes help enforce team standards or create purpose-specific assistants. See [Custom Modes documentation](/features/custom-modes) for setup instructions.
+Tailor Roo Code's behavior by customizing existing modes or creating new specialized assistants. Define tool access, file permissions, and behavior instructions to enforce team standards or create purpose-specific assistants. See [Custom Modes documentation](/features/custom-modes) for setup instructions.
@@ -31,21 +31,22 @@ Each mode—including custom ones—features **Sticky Models**. This means Roo C
 *   **Experimentation:** Safely experiment with different prompts and configurations without affecting other modes
 *   **Team Collaboration:** Share custom modes with your team to standardize workflows
 
-<img src="/img/custom-modes/custom-modes-1.png" alt="Overview of custom modes interface" width="400" />
+<img src="/img/custom-modes/custom-modes-3.png" alt="Overview of custom modes interface" width="500" />
 
     *Roo Code's interface for creating and managing custom modes.*
 
 ## What's Included in a Custom Mode?
 
 Custom modes are defined by several key properties. Understanding these concepts will help you tailor Roo's behavior effectively before diving into the JSON configuration.
 
-| Property             | Conceptual Description                                                                                                                                                                                                                                                                                                                                                                                       |
-| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| `slug`               | A **unique internal identifier** for the mode. It's used by Roo Code to reference the mode, especially for associating [mode-specific instruction files](#mode-specific-instructions-via-filesdirectories).                                                                                                                                                                                                   |
-| `name`               | The **display name** for the mode as it appears in the Roo Code user interface. This should be human-readable and descriptive.                                                                                                                                                                                                                                                                               |
-| `roleDefinition`     | The **core identity and expertise** of the mode. This text is placed at the beginning of the system prompt to define Roo's personality and primary function for this mode.<br />- **Critical First Sentence:** The first sentence (up to the first period `.`) is vital. It serves as a concise summary for Roo to understand the mode's purpose, even when it's not the active one. The entire definition is used when the mode is active. |
-| `groups`             | Defines the **allowed toolsets and file access permissions** for the mode. You can specify which general categories of tools (like reading files, editing files, browsing, or executing commands) the mode can use. For editing, you can also specify restrictions on which file types are permissible.                                                                                                    |
-| `customInstructions` | **Specific behavioral guidelines** or rules for the mode. These instructions are added near the end of the system prompt to further refine Roo's behavior beyond the `roleDefinition`. This can be provided directly in the configuration or via separate instruction files.                                                                                                                               |
+| UI Field / JSON Property                 | Conceptual Description                                                                                                                                                                                                                                                                                                                                                                                       |
+| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Slug (`slug`)                            | A **unique internal identifier** for the mode. It's used by Roo Code to reference the mode, especially for associating [mode-specific instruction files](#mode-specific-instructions-via-filesdirectories).                                                                                                                                                                                                   |
+| Name (`name`)                            | The **display name** for the mode as it appears in the Roo Code user interface. This should be human-readable and descriptive.                                                                                                                                                                                                                                                                               |
+| Role Definition (`roleDefinition`)       | Defines the **core identity and expertise** of the mode. This text is placed at the beginning of the system prompt.<br />- Its primary function is to define Roo's personality and behavior when this mode is active.<br />- The **first sentence** (up to the first period `.`) serves as a default concise summary for Roo to understand the mode's general purpose. <br />- **However, if the `whenToUse` property is defined, `whenToUse` takes precedence** for summarizing the mode's function, especially in contexts like task orchestration or mode switching. In such cases, the first sentence of `roleDefinition` is less critical for this specific summarization task, though the entire `roleDefinition` is still used when the mode is active to guide its overall behavior. |
+| Available Tools (`groups`)               | Defines the **allowed toolsets and file access permissions** for the mode.<br />- In the UI, this corresponds to selecting which general categories of tools (like reading files, editing files, browsing, or executing commands) the mode can use.<br />- File type restrictions for the "edit" group are typically managed via manual JSON configuration or by asking Roo to set them up, as detailed in the [JSON Property Details for `groups`](#groups). |
+| When to Use (optional) (`whenToUse`)     | (Optional) Provides **guidance for Roo to understand the mode's purpose**, especially for automated decisions.<br />- This text is used by Roo, particularly the [`🪃 Orchestrator`](/basic-usage/using-modes#orchestrator-mode-aka-boomerang-mode) mode, for [orchestrating tasks](/features/boomerang-tasks) (e.g., via the [`new_task`](/advanced-usage/available-tools/new-task) tool).<br />- It also helps Roo decide which mode is appropriate when [switching modes](/basic-usage/using-modes#switching-between-modes) (e.g., via the [`switch_mode`](/advanced-usage/available-tools/switch-mode) tool).<br />- If populated, this description is used by Roo to understand the mode's function; otherwise, the first sentence of the `roleDefinition` is used by default. |
+| Custom Instructions (optional) (`customInstructions`) | **Specific behavioral guidelines** or rules for the mode.<br />- These instructions are added near the end of the system prompt to further refine Roo's behavior beyond the `roleDefinition`.<br />- This can be provided directly in the configuration or via separate instruction files.                                                                                                                               |
 
 ## Methods for Creating and Configuring Custom Modes
 
@@ -65,10 +66,11 @@ Roo Code will guide you through the process, prompting for necessary information
 2.  **Create New Mode:** Click the <Codicon name="add" /> button to the right of the Modes heading.
 3.  **Fill in Fields:**
 
-<img src="/img/custom-modes/custom-modes-2.png" alt="Custom mode creation interface in the Prompts tab" width="600" />
-*The custom mode creation interface showing fields for name, slug, save location, role definition, available tools, and custom instructions.*
+<img src="/img/custom-modes/custom-modes-4.png" alt="Custom mode creation interface in the Prompts tab" width="600" />
 
-    The interface provides fields for `Name`, `Slug`, `Save Location`, `Role Definition`, `Available Tools`, and `Custom Instructions`. After filling these, click the "Create Mode" button.
+*The custom mode creation interface showing fields for name, slug, save location, role definition, available tools, custom instructions.*
+
+    The interface provides fields for `Name`, `Slug`, `Save Location`, `Role Definition`, `When to Use (optional)`, `Available Tools`, and `Custom Instructions`. After filling these, click the "Create Mode" button.
 
 *Refer to the [What's Included in a Custom Mode?](#whats-included-in-a-custom-mode) table for conceptual explanations of each property. File type restrictions for the "edit" tool group can be added by asking Roo or through manual JSON configuration.*
 
@@ -88,11 +90,15 @@ Both files use the same JSON format. Each configuration file contains a `customM
       "slug": "mode-slug-example",
       "name": "Example Mode Display Name",
       "roleDefinition": "This mode's role and capabilities are defined here.",
+      "whenToUse": "Describe when this mode is most appropriate here.",
+      "customInstructions": "Additional guidelines for this example mode.",
       "groups": [
         "read",
-        ["edit", { "fileRegex": "\\.txt$", "description": "Text files only" }]
-      ],
-      "customInstructions": "Additional guidelines for this example mode."
+        "edit", // Can also be ["edit", { "fileRegex": "\\.md$", "description": "Markdown only" }]
+        "browser",
+        "command",
+        "mcp"
+      ]
     }
   ]
 }
@@ -115,7 +121,7 @@ Both files use the same JSON format. Each configuration file contains a `customM
 ##### `roleDefinition`
 *   **Purpose:** Detailed description of the mode's role, expertise, and personality.
 *   **Placement:** This text is placed at the beginning of the system prompt when the mode is active.
-*   **Critical First Sentence:** As noted in the table above, the first sentence is crucial for summarizing the mode's function.
+*   **Important First Sentence:** The first sentence (up to the first period `.`) serves as a default concise summary for Roo to understand the mode's general purpose. **However, if the `whenToUse` property is defined, `whenToUse` takes precedence** for summarizing the mode's function, especially in contexts like task orchestration or mode selection. In such cases, the first sentence of `roleDefinition` is less critical for this specific summarization task, though the entire `roleDefinition` is still used when the mode is active to guide its overall behavior.
 *   *JSON Example:* `"roleDefinition": "You are a technical writer specializing in clear documentation."`
 
 ##### `groups`
@@ -135,6 +141,12 @@ Both files use the same JSON format. Each configuration file contains a `customM
     ]
     ```
 
+##### `whenToUse`
+*   **Purpose:** (Optional) Provides guidance for Roo to understand what this mode does. This is primarily used by the [`🪃 Orchestrator`](/basic-usage/using-modes#orchestrator-mode-aka-boomerang-mode) mode for [orchestrating tasks](/features/boomerang-tasks) (e.g., via the [`new_task`](/advanced-usage/available-tools/new-task) tool) and for determining the appropriate mode when [switching modes](/basic-usage/using-modes#switching-between-modes) (e.g., via the [`switch_mode`](/advanced-usage/available-tools/switch-mode) tool).
+*   **Format:** A string describing ideal scenarios or task types for this mode.
+*   **Usage:** If populated, Roo uses this description to understand the mode's function. Otherwise, the first sentence of the `roleDefinition` is used by default.
+*   **JSON Example:** `"whenToUse": "This mode is best for refactoring Python code to improve performance and readability."`
+
 ##### `customInstructions`
 *   **Purpose:** A string containing additional behavioral guidelines for the mode.
 *   **Placement:** This text is added near the end of the system prompt.
@@ -225,11 +237,12 @@ To customize a default mode across all your projects:
     "slug": "code", // Matches the default 'code' mode slug
     "name": "💻 Code (Global Override)", // Custom display name
     "roleDefinition": "You are a software engineer with global-specific constraints",
+    "whenToUse": "This globally overridden code mode is for JS/TS tasks.",
+    "customInstructions": "Focus on project-specific JS/TS development",
     "groups": [
       "read",
       ["edit", { "fileRegex": "\\.(js|ts)$", "description": "JS/TS files only" }]
-    ],
-    "customInstructions": "Focus on project-specific JS/TS development"
+    ]
   }]
 }
 ```
@@ -251,11 +264,12 @@ To override a default mode for just one project:
     "slug": "code", // Matches the default 'code' mode slug
     "name": "💻 Code (Project-Specific)", // Custom display name
     "roleDefinition": "You are a software engineer with project-specific constraints",
+    "whenToUse": "This project-specific code mode is for JS/TS tasks within this project.",
+    "customInstructions": "Focus on project-specific JS/TS development",
     "groups": [
       "read",
       ["edit", { "fileRegex": "\\.(js|ts)$", "description": "JS/TS files only" }]
-    ],
-    "customInstructions": "Focus on project-specific JS/TS development"
+    ]
   }]
 }
 ```
@@ -326,40 +340,5 @@ Before applying a regex pattern:
 2.  Remember the double backslash rule for JSON.
 3.  Start with simpler patterns and build complexity gradually.
 
-## Example Configurations
-
-Each example shows different aspects of mode configuration:
-
-### Basic Documentation Writer
-```json
-{
-  "customModes": [{
-    "slug": "docs-writer",
-    "name": "Documentation Writer",
-    "roleDefinition": "You are a technical writer specializing in clear documentation",
-    "groups": [
-      "read",
-      ["edit", { "fileRegex": "\\.md$", "description": "Markdown files only" }]
-    ],
-    "customInstructions": "Focus on clear explanations and examples"
-  }]
-}
-```
-
-### Test Engineer with File Restrictions
-```json
-{
-  "customModes": [{
-    "slug": "test-engineer",
-    "name": "Test Engineer",
-    "roleDefinition": "You are a test engineer focused on code quality",
-    "groups": [
-      "read",
-      ["edit", { "fileRegex": "\\.(test|spec)\\.(js|ts)$", "description": "Test files only" }]
-    ]
-  }]
-}
-```
-
 ## Community Gallery
 Ready to explore more? Check out the [Custom Modes Gallery](/community/#custom-modes-gallery) section on the main community page to discover and share custom modes created by the community!