diff --git a/modules/ROOT/pages/af-agent-networks.adoc b/modules/ROOT/pages/af-agent-networks.adoc index 46b6d4e50..d72d9f8a8 100644 --- a/modules/ROOT/pages/af-agent-networks.adoc +++ b/modules/ROOT/pages/af-agent-networks.adoc @@ -170,7 +170,7 @@ a| * For complex reasoning: Gemini 3 Pro (Deep Think capabilities) |=== -Agent networks support text-based prompts and responses. Image and binary message types aren't supported. +Agent networks support text-based messages and responses. Image and binary message types aren't supported. [[a2a-protocol]] == A2A Protocol diff --git a/modules/ROOT/pages/af-create-agent-network.adoc b/modules/ROOT/pages/af-create-agent-network.adoc index b6c4ab78b..7858d3ea2 100644 --- a/modules/ROOT/pages/af-create-agent-network.adoc +++ b/modules/ROOT/pages/af-create-agent-network.adoc @@ -16,7 +16,7 @@ MuleSoft Vibes can help you create your project. For more information, see xref: . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18]. . Describe your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. MuleSoft Vibes does the rest. -To get started, try one of these suggested prompts. +To get started, try one of these suggested messages. * Create a new agent network project called "Employee Onboarding." Add HR agent and CRM agent. * Build a travel planner broker that plans multi-city trips and generate a new agent network. diff --git a/modules/ROOT/pages/af-define-your-agent-network-specification.adoc b/modules/ROOT/pages/af-define-your-agent-network-specification.adoc index ebc7e7679..5e5be9967 100644 --- a/modules/ROOT/pages/af-define-your-agent-network-specification.adoc +++ b/modules/ROOT/pages/af-define-your-agent-network-specification.adoc @@ -19,7 +19,7 @@ MuleSoft Vibes can help you configure your agent network specification. For more . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18]. . Give the agent information about your agent network, including the brokers, agents, MCP servers, and LLMs you want to connect. -To get started, try one of these suggested prompts. +To get started, try one of these suggested messages. * Help me build an agent network configuration for my Employee Onboarding project. * Revise my Employee Onboarding agent network project. Use OpenAI for the LLM. @@ -47,7 +47,7 @@ If you have existing Exchange assets to use in your agent network, add them to t . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18]. . Tell the agent that you want to add Exchange assets to your project. MuleSoft Vibes does the rest. -To get started, try one of these suggested prompts. +To get started, try one of these suggested messages. * Add tools for background check processing in my Employee Onboarding project. * Add a Talent Pool MCP server to my Employee Onboarding agent network project. diff --git a/modules/ROOT/pages/af-deploy-agent-network-targets.adoc b/modules/ROOT/pages/af-deploy-agent-network-targets.adoc index faf2890a9..cac03fb6a 100644 --- a/modules/ROOT/pages/af-deploy-agent-network-targets.adoc +++ b/modules/ROOT/pages/af-deploy-agent-network-targets.adoc @@ -51,7 +51,7 @@ MuleSoft Vibes can help you deploy your agent network instances. For more inform . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18]. . Tell the agent that you want to deploy your agent network. MuleSoft Vibes does the rest. -To get started, try one of these suggested prompts. +To get started, try one of these suggested messages. * Deploy my agent network project to the production environment. * Deploy the hello-world-network project to staging. diff --git a/modules/ROOT/pages/af-project-files.adoc b/modules/ROOT/pages/af-project-files.adoc index bd8b3736d..04265ddb3 100644 --- a/modules/ROOT/pages/af-project-files.adoc +++ b/modules/ROOT/pages/af-project-files.adoc @@ -13,7 +13,7 @@ The agent network YAML file defines a structured configuration for multi-agent s For example, think of the YAML as your organizational chart for digital labor. Each internal organization (for example, HR, IT, Sales, or Engineering) has a hierarchical structure through which actors collaborate. Jobs are split into tasks and assigned. -Just like with human labor, digital agents require coordination. We call these coordinators "brokers". These are special types of agents in your agent network capable of receiving a user prompt, identifying the goal, determining the necessary steps to be carried out, and delegating each step to the proper agent, even if the agent is part of a different broker. +Just like with human labor, digital agents require coordination. We call these coordinators "brokers". These are special types of agents in your agent network capable of receiving a user message, identifying the goal, determining the necessary steps to be carried out, and delegating each step to the proper agent, even if the agent is part of a different broker. The `agent-network.yaml` file uses these sections. @@ -311,7 +311,7 @@ Here's another example of instructions for a customer service broker. This broke 5. Summarize actions: Provide a clear, human-readable summary of the steps performed, including information about the created Slack channel and the on-call engineer assigned. ---- -You don't have to provide instructions like "split the prompt into tasks", or "select the best tool". The broker does that on its own. +You don't have to provide instructions like "split the message into tasks", or "select the best tool". The broker does that on its own. The `instructions` element has these properties. diff --git a/modules/ROOT/pages/af-publish-agent-network-assets.adoc b/modules/ROOT/pages/af-publish-agent-network-assets.adoc index a470b801b..ce32d4ac1 100644 --- a/modules/ROOT/pages/af-publish-agent-network-assets.adoc +++ b/modules/ROOT/pages/af-publish-agent-network-assets.adoc @@ -20,7 +20,7 @@ MuleSoft Vibes can help you publish your agent network specification to Anypoint . In the Anypoint Code Builder activity bar, click the agent icon image:af-acb-dev-agent-icon.png["",18,18]. . Tell the agent that you want to publish your agent network. MuleSoft Vibes does the rest. -To get started, try one of these suggested prompts. +To get started, try one of these suggested messages. * Publish my Employee Onboarding project. * Publish my agent network project version 1.0.0. diff --git a/modules/ROOT/pages/int-ai-developing-integrations.adoc b/modules/ROOT/pages/int-ai-developing-integrations.adoc index f81c2cd91..58e4393ab 100644 --- a/modules/ROOT/pages/int-ai-developing-integrations.adoc +++ b/modules/ROOT/pages/int-ai-developing-integrations.adoc @@ -9,7 +9,7 @@ To develop, manage, or maintain your applications, use MuleSoft Vibes in Anypoin * Deploying and managing instances * Managing custom metadata -All of these actions are driven by natural language prompts. +All of these actions are driven by natural language messages. When you generate an integration, MuleSoft Vibes transforms your business logic into a Mule application. The generated application includes: @@ -49,7 +49,7 @@ For details on configuring permissions and server connections, see xref:troubles == Provide Additional Context You can improve the accuracy of generated outputs by adding extra context to MuleSoft Vibes. -In addition to prompts, it accepts these types of input: +Besides the message you send in the panel, you can attach these types of input: * **Files** – Add a requirements file or other reference documents. * **Folders** – Provide an entire project folder for MuleSoft Vibes to consider. diff --git a/modules/ROOT/pages/mulesoft-vibes.adoc b/modules/ROOT/pages/mulesoft-vibes.adoc index d172c435d..9e4467630 100644 --- a/modules/ROOT/pages/mulesoft-vibes.adoc +++ b/modules/ROOT/pages/mulesoft-vibes.adoc @@ -4,7 +4,7 @@ MuleSoft Vibes is a purpose-built assistant for the development lifecycle, available directly in Anypoint Code Builder. -MuleSoft Vibes enables you to build, deploy, and manage your projects using natural language prompts. +MuleSoft Vibes enables you to build, deploy, and manage your projects using natural language messages. MuleSoft Vibes integrates with the xref:mulesoft-mcp-server::index.adoc[MuleSoft MCP Server], which provides a set of agentic tools that connect MuleSoft Vibes directly to your MuleSoft environment. Through this integration, MuleSoft Vibes can perform actions and retrieve data on your behalf, enabling capabilities such as: diff --git a/modules/ROOT/pages/start-workspaces.adoc b/modules/ROOT/pages/start-workspaces.adoc index f23e536b9..e24424274 100644 --- a/modules/ROOT/pages/start-workspaces.adoc +++ b/modules/ROOT/pages/start-workspaces.adoc @@ -79,7 +79,7 @@ image::imp-local-api-open-workspace.png["A multi-root workspace in Explorer view === Open a Workspace with MuleSoft Vibes -You can ask MuleSoft Vibes to switch workspaces using natural language prompts, such as: +You can ask MuleSoft Vibes to switch workspaces using natural language, such as: * "Open my Orders API workspace" * "Switch to the `` workspace" diff --git a/modules/ROOT/pages/troubleshoot-generative-ai.adoc b/modules/ROOT/pages/troubleshoot-generative-ai.adoc index 060d2f5a2..3582ae16d 100644 --- a/modules/ROOT/pages/troubleshoot-generative-ai.adoc +++ b/modules/ROOT/pages/troubleshoot-generative-ai.adoc @@ -4,7 +4,7 @@ The following errors sometimes occur when you use MuleSoft Vibes in Anypoint Cod == Unexpected Results When Using Mulesoft Vibes -If the generated flow doesn't return accurate or useful results for your prompt, try rewriting your prompt and follow the guidelines to xref:vibes-create-integrations.adoc#craft-ai-prompt[write an effective prompt]. +If the generated flow doesn't return accurate or useful results for your message, try rewriting your message and follow the guidelines to xref:vibes-create-integrations.adoc#craft-ai-prompt[write an effective message]. If results are still inconsistent, verify that your project context and Mulesoft Vibes settings are correctly configured. diff --git a/modules/ROOT/pages/vibes-api-ai-create-spec.adoc b/modules/ROOT/pages/vibes-api-ai-create-spec.adoc index 183d80936..761ab8005 100644 --- a/modules/ROOT/pages/vibes-api-ai-create-spec.adoc +++ b/modules/ROOT/pages/vibes-api-ai-create-spec.adoc @@ -2,9 +2,9 @@ :page-deployment-options: cloud-ide, desktop-ide :page-aliases: api-ai-create-spec.adoc -MuleSoft Vibes is a purpose-built assistant for the development lifecycle, available directly in Anypoint Code Builder. It provides a unified panel that lets you interact with AI features using natural language prompts. Mulesoft Vibes works with the embedded MuleSoft MCP Server (see xref:mulesoft-mcp-server::index.adoc[Mulesoft MCP Server]) to support capabilities such as deploying applications, managing instances, and creating new projects. +MuleSoft Vibes is a purpose-built assistant for the development lifecycle, available directly in Anypoint Code Builder. It provides a unified panel that lets you interact with AI features using natural language. Mulesoft Vibes works with the embedded MuleSoft MCP Server (see xref:mulesoft-mcp-server::index.adoc[Mulesoft MCP Server]) to support capabilities such as deploying applications, managing instances, and creating new projects. -One of these capabilities is AI-powered API specification generation. With Mulesoft Vibes, you can generate and mock API specifications from natural language prompts. This feature reduces the time spent on API design by simplifying the creation of syntax-heavy specifications. +One of these capabilities is AI-powered API specification generation. With Mulesoft Vibes, you can generate and mock API specifications from natural language. This feature reduces the time spent on API design by simplifying the creation of syntax-heavy specifications. [[before-you-begin]] == Before You Begin @@ -27,7 +27,7 @@ NOTE: Authentication happens through the user logged into Anypoint Code Builder. To design an API spec with Mulesoft Vibes: . Open Mulesoft Vibes from the toolbar or from the *Build Your Ecosystem with AI* card in the canvas. -. Enter a prompt that describes your API specification. +. Enter a message that describes your API specification. + Include these required details and consider including optional details to generate a more precise spec: + @@ -164,7 +164,7 @@ Optionally, provide a description, format, minimum and maximum length, default v Governance isn't included in the validation. [start=3] -. Enter your prompt in Mulesoft Vibes and submit it. +. Enter your message in Mulesoft Vibes and submit it. . Review the generated specification. . If *Auto-approve* is enabled, Mulesoft Vibes writes the generated API spec directly into your project files. . If *Auto-approve* is disabled, Mulesoft Vibes prompts you to approve or reject each file change before applying it. diff --git a/modules/ROOT/pages/vibes-create-integrations.adoc b/modules/ROOT/pages/vibes-create-integrations.adoc index 3079e086b..db3a76db1 100644 --- a/modules/ROOT/pages/vibes-create-integrations.adoc +++ b/modules/ROOT/pages/vibes-create-integrations.adoc @@ -58,17 +58,17 @@ The integration builder canvas appears with starting cards. To generate an integration with AI, click *Use Mulesoft Vibes* in the *Build an Ecosystem with AI* card. [[craft-ai-prompt]] -== Write Your Prompt +== Write Your Message -Before you create an integration, define what you want to achieve with the integration, for example, optimizing a business process. In the Mulesoft Vibes panel, enter your prompt using natural language. The clearer and more specific your prompt, the more accurate the generated integration. +Before you create an integration, define what you want to achieve with the integration, for example, optimizing a business process. In the Mulesoft Vibes panel, describe what you need using natural language. The clearer and more specific your message, the more accurate the generated integration. -Best practices for prompts: +Best practices for messages: * Be clear and precise. * Include triggering events (for example, sending an email when a new case is created). * Emphasize key MuleSoft components and connector operations (for example, HTTP Connector *Listener* and Email Connector *Send*). * Specify the data objects (for example, *Salesforce Account object*). -* Review your prompt before submitting it. +* Review your message before you submit it. After Mulesoft Vibes generates the initial integration, the code is written directly into your project. You can further customize it to fit your requirements. diff --git a/modules/ROOT/pages/vibes-get-started.adoc b/modules/ROOT/pages/vibes-get-started.adoc index abca878aa..2be4eb7e5 100644 --- a/modules/ROOT/pages/vibes-get-started.adoc +++ b/modules/ROOT/pages/vibes-get-started.adoc @@ -1,7 +1,7 @@ = Get Started with MuleSoft Vibes :page-aliases: a4d-get-started.adoc -MuleSoft Vibes helps you build APIs and integrations using natural language prompts directly in your development environment. +MuleSoft Vibes helps you build APIs and integrations by sending natural language messages directly in your development environment. == Use MuleSoft Vibes @@ -11,7 +11,7 @@ You can open MuleSoft Vibes from the: * Top navigation bar * *Build with AI* card in the project canvas -When you submit a prompt, MuleSoft Vibes processes it using the MuleSoft MCP Server and performs actions such as generating API specifications or integration flows. +When you send a message, MuleSoft Vibes processes it using the MuleSoft MCP Server and performs actions such as generating API specifications or integration flows. Depending on your configuration, MuleSoft Vibes can: @@ -23,7 +23,7 @@ Depending on your configuration, MuleSoft Vibes can: MuleSoft Vibes operates in two modes: * *Plan Mode* -MuleSoft Vibes analyzes your prompt and produces a step-by-step plan describing how it will accomplish the task. No actions are executed automatically in this mode. +MuleSoft Vibes analyzes your message and produces a step-by-step plan describing how it will accomplish the task. No actions are executed automatically in this mode. * *Act Mode* MuleSoft Vibes attempts to perform the actions outlined in the plan by using the MuleSoft MCP Server tools to modify files, create resources, or execute changes to your project. @@ -38,13 +38,13 @@ MuleSoft Vibes uses MuleSoft-optimized AI pipelines to generate high-quality cod The pipelines are exposed to MuleSoft Vibes through these MCP tools: * `generate_mule_flow` – Generates Mule integration flows. -* `generate_api_spec` – Generates API specifications from natural language prompts. +* `generate_api_spec` – Generates API specifications from natural language. Because these tools run on pipelines optimized specifically for MuleSoft use cases, users typically receive higher-quality code outputs (on average, 60% better) compared to generic generation. To ensure the best results: -* Verify that the MuleSoft MCP Server is loaded in MuleSoft Vibes prior to sending a prompt. +* Verify that the MuleSoft MCP Server is loaded in MuleSoft Vibes before you send a message. * Make sure MuleSoft Vibes is invoking these specialized tools. * Verify that all required prerequisites for MuleSoft Vibes and MCP Server are enabled in your environment. @@ -62,7 +62,7 @@ To add context: . Select files or folders to attach, paste the input or output from terminal, or paste a URL. . Confirm to add the context to your current task. -You can also add context directly from the prompt input box by typing `@`, which opens the same context selector. +You can also add context directly from the message input box by typing `@`, which opens the same context selector. These inputs are used as contextual references during generation. @@ -86,4 +86,4 @@ The available options include: == Skills in MuleSoft Vibes -xref:vibes-skills.adoc[Skills] are reusable instruction sets that load when your prompt matches a skill's description. For information about skills and MCP tools, see xref:vibes-skills.adoc[]. +xref:vibes-skills.adoc[Skills] are reusable instruction sets that load when your message matches a skill's description. For information about skills and MCP tools, see xref:vibes-skills.adoc[]. diff --git a/modules/ROOT/pages/vibes-prompt-examples.adoc b/modules/ROOT/pages/vibes-prompt-examples.adoc index 27a6775f8..6d14fd7bf 100644 --- a/modules/ROOT/pages/vibes-prompt-examples.adoc +++ b/modules/ROOT/pages/vibes-prompt-examples.adoc @@ -1,8 +1,8 @@ -= Mulesoft Vibes Example Prompts += Mulesoft Vibes Example Messages :page-aliases: a4d-prompt-examples.adoc -Use these example prompts to guide Mulesoft Vibes in completing common tasks. Customize the values to match your project or environment. +Use these example messages to guide Mulesoft Vibes in completing common tasks. Customize the values to match your project or environment. include::mulesoft-mcp-server::partial$agent-prompts.adoc[tag=app-deployment,leveloffset=+1] diff --git a/modules/ROOT/pages/vibes-skills.adoc b/modules/ROOT/pages/vibes-skills.adoc index ebdcb80ed..d5059a2d5 100644 --- a/modules/ROOT/pages/vibes-skills.adoc +++ b/modules/ROOT/pages/vibes-skills.adoc @@ -1,7 +1,7 @@ = Use Skills with MuleSoft Vibes :page-deployment-options: cloud-ide, desktop-ide -Skills are reusable instruction sets that MuleSoft Vibes activates only when they apply to your task. Each skill packages guidance and optional resources so MuleSoft Vibes can follow a consistent workflow without loading that material for unrelated prompts. +Skills are reusable instruction sets that MuleSoft Vibes activates only when they apply to your task. Each skill packages guidance and optional resources so MuleSoft Vibes can follow a consistent workflow without loading that material for unrelated messages. When your request matches a skill's description, MuleSoft Vibes uses the `use_skill` tool to load the full instructions and run them for that task. Unlike workspace rules that stay active across conversations, skills load as needed, which leaves more context available for other work. diff --git a/modules/ROOT/pages/vibes-workflows-commands.adoc b/modules/ROOT/pages/vibes-workflows-commands.adoc index a7ba3c00a..0d8621c56 100644 --- a/modules/ROOT/pages/vibes-workflows-commands.adoc +++ b/modules/ROOT/pages/vibes-workflows-commands.adoc @@ -10,7 +10,7 @@ Use rules to enforce organizational conventions, ensure consistent error handlin Rules can be defined at two levels: -* *Global* – Applies to all prompts sent to Mulesoft Vibes. +* *Global* – Applies to all messages sent to Mulesoft Vibes. * *Workspace* – Applies only to the active workspace. @@ -54,7 +54,7 @@ Workflows define a sequence of steps that Mulesoft Vibes executes to complete a == Add Commands Commands provide quick shortcuts for interacting with Mulesoft Vibes. -You can invoke any command by typing `/` in the prompt input box. +You can invoke any command by typing `/` in the message input box. Mulesoft Vibes includes several built-in commands: @@ -79,4 +79,4 @@ Rulesets help you: 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. \ No newline at end of file +MuleSoft Vibes applies these rules automatically when processing messages and executing workflows. \ No newline at end of file