Update a4d-workflows-commands.adoc

Author: failup

modules/ROOT/pages/a4d-workflows-commands.adoc

@@ -1,46 +1,46 @@
 = Workflows and Rules 
 
-Rules and Workflows allow developers to customize how MuleSoft Dev Agent operates within their project.
+Rules and Workflows allow developers to customize how Mulesoft Vibes operates within their project.
 
-Rules Define natural-language constraints or guidelines for how Dev Agent should generate content.  
+Rules Define natural-language constraints or guidelines for how Mulesoft Vibes should generate content.  
 
 You can use rules to enforce naming conventions, ensure consistent error handling, or maintain coding standards across your workspace.  
 Rules can be defined at two levels:  
 
-* *Global* – Applies to all prompts sent to Dev Agent.  
+* *Global* – Applies to all prompts sent to Mulesoft Vibes.  
 
 * *Workspace* – Applies only to the active workspace.
 
 Workflows create predefined multi-step tasks that Dev Agent executes automatically.  
 
-Workflows let you streamline repeated development steps and can be triggered using slash commands (for example, `/workflow-name`) in the Dev Agent panel.
+Workflows let you streamline repeated development steps and can be triggered using slash commands (for example, `/workflow-name`) in the Mulesoft Vibes panel.
 
 == Add Workflows or Rules
 
-. Open MuleSoft Dev Agent in the sidebar.
+. Open MuleSoft Mulesoft Vibes in the sidebar.
 . Select *Settings*.
 . In the *Rules and Workflows* section, choose whether you want to add a rule or a workflow.
 . Select *Add Rule* or *Add Workflow*.
 . Provide the required information:
-* For rules, enter the natural-language instruction you want Dev Agent to follow.
+* For rules, enter the natural-language instruction you want Mulesoft Vibes to follow.
 * For workflows, enter a name, an optional description, and the steps the workflow should run.
 . Select *Save*.
 
 You can edit or delete existing rules and workflows from the same section.
 
 === Rule examples
 
-You can use rules to guide how Dev Agent generates or validates content. For example:
+You can use rules to guide how Mulesoft Vibes generates or validates content. For example:
 
-* *Naming convention rule*: Instruct Dev Agent to ensure that all API names follow your organization’s naming standards.
+* *Naming convention rule*: Instruct Mulesoft Vibes to ensure that all API names follow your organization’s naming standards.
 
 * *Validation rule*: Require that every API specification includes version information before generating related files.
 
-* *Security rule*: Ask Dev Agent to flag endpoints that expose sensitive data without authentication.
+* *Security rule*: Ask Mulesoft Vibes to flag endpoints that expose sensitive data without authentication.
 
 ==== Workflow examples
 
-Workflows define a sequence of steps that Dev Agent executes to complete a task. For example:
+Workflows define a sequence of steps that Mulesoft Vibes executes to complete a task. For example:
 
 * *API design validation workflow*:  Validate an API specification, check naming conventions, verify security requirements, and generate a summary of issues.
 
@@ -50,10 +50,10 @@ Workflows define a sequence of steps that Dev Agent executes to complete a task.
 
 == Add Commands
 
-Commands provide quick shortcuts for interacting with MuleSoft Dev Agent.  
+Commands provide quick shortcuts for interacting with Mulesoft Vibes.  
 You can invoke any command by typing `/` in the prompt input box.
 
-Dev Agent includes several built-in commands:
+Mulesoft Vibes includes several built-in commands:
 
 * `/newrule` — Create a new rule based on the current conversation.
 * `/newchat` — Start a new chat that carries over context from your current task.