Skip to content

vibes-workflows-commands.adoc

Latest commit

 

History

History
85 lines (51 loc) · 3.69 KB

vibes-workflows-commands.adoc

File metadata and controls

85 lines (51 loc) · 3.69 KB

Workflows and Rules

Rules and Workflows allow developers to customize how Mulesoft Vibes operates within their 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.

Rules can be defined at two levels:

  • Global – Applies to all prompts 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 Mulesoft Vibes in the sidebar.

  2. Select Settings.

  3. In the Rules and Workflows section, choose whether you want to 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 you want Mulesoft Vibes to follow.

    • For workflows, enter a name, an optional description, and the steps the workflow should 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.

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.

Add Commands

Commands provide quick shortcuts for interacting with Mulesoft Vibes. You can invoke any command by typing / in the prompt input box.

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.

  • /reportbug — Report an issue by creating a GitHub ticket with Agentforce Vibes formatting.

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.

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 prompts and executing workflows.