--- schema_version: "1" id: 9c2acde699da3368d87597c750a2d7934a354f226dad34214664131090919b07 title: Workflows and Rules collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/anypoint-code-builder/vibes-workflows-commands.md canonical_url: https://docs.mulesoft.com/anypoint-code-builder/vibes-workflows-commands source_site: docs.mulesoft.com content_type: documentation content_hash: f06dc2f2e7e9de5df71408d7e2aa840c9280ea45881a24091ed9fbf512e2f1c7 description: MuleSoft Documentation Site latest: true --- --- product: Anypoint Code Builder version: master --- # Workflows and Rules > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Use workflows and rules to customize how MuleSoft Vibes operates within your project. Rules define natural-language constraints that MuleSoft Vibes follows when generating content. Use rules to enforce organizational conventions, ensure consistent error handling, and maintain coding standards across your workspace. You can define rules at two levels: - **Global** – Applies to all messages sent to Mulesoft Vibes. - **Workspace** – Applies only to the active workspace. Workflows create predefined multi-step tasks that MuleSoft Vibes executes automatically. 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 1. Open MuleSoft Vibes in the sidebar. 2. Select **Settings**. 3. In the **Rules and Workflows** section, add a rule or a workflow. 4. Select **Add Rule** or **Add Workflow**. 5. Provide the required information: - For rules, enter the natural-language instruction to follow. - For workflows, enter a name, an optional description, and the steps the workflow must run. 6. Select **Save**. You can edit or delete existing rules and workflows from the same section. ### Rule Examples You can use rules to guide how MuleSoft Vibes generates or validates content. For example: - **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 MuleSoft Vibes to flag endpoints that expose sensitive data without authentication. Example rule text to enter in **Add Rule**: ```text When generating RAML files, enforce this naming pattern: --api. If the API title or baseUri doesn't follow the pattern, return a warning and suggest a corrected value. ``` #### Workflow Examples 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. - **API creation workflow**: Generate an API specification, apply validation rules, suggest improvements, and save the final version to the workspace. - **Troubleshooting workflow**: Analyze an error, identify the root cause, propose a fix, and update the configuration if needed. Example workflow definition to enter in **Add Workflow**: ```text Name: api-design-review Description: Run governance checks before publishing a RAML spec. Steps: 1. Validate RAML syntax and required metadata. 2. Check naming conventions from workspace rules. 3. Check for unsecured endpoints that expose sensitive fields. 4. Summarize findings with required fixes and suggested improvements. ``` ## Add Commands Commands provide quick shortcuts for interacting with MuleSoft Vibes. You can invoke any command by typing `/` in the message input box. MuleSoft Vibes includes several built-in commands.
CommandDescription

/newrule

Create a new rule based on the current conversation.

/newchat

Start a new chat that carries over context from your current task.

/reportbug

Report a malfunctioning output by creating a GitHub issue with the MuleSoft Vibes format.

Workflows that you define also appear as commands under **Workflow Commands**. You can trigger them the same way by typing `/` followed by the workflow name. Example command usage: - ```command /api-design-review ``` ## Enforce Organizational Conventions with Rulesets Define and apply organizational conventions with rulesets across your development workflows using natural language. By creating rules at the global or workspace level, you can standardize how MuleSoft Vibes generates APIs, integrations, and related assets. Rulesets help you: - Enforce naming and design standards across teams - Apply consistent validation and security requirements - Reduce manual review by guiding generation upfront Because rules are written in natural language, you can describe expectations without needing formal configuration or code. MuleSoft Vibes applies these rules automatically when processing messages and executing workflows. To share workspace rules and skills from GitHub, see [Sharing Rules and Skills from GitHub with MuleSoft Vibes](https://docs.mulesoft.com/anypoint-code-builder/vibes-share-rules-skills-github).