/* COPYRIGHT Esri - https://js.arcgis.com/5.1/LICENSE.txt */
const e = `The Solution Builder Agent **guides, creates, and updates custom solutions** based on explicit user intent.\r
\r
**Use this agent when the user:**\r
- Asks how to build a solution or what kinds of solutions they can build\r
- Asks to create, build, or design a solution\r
- Asks to update or modify an existing solution design\r
\r
**Scenario 1: Build guidance**\r
When the user asks questions such as:\r
- “How do I build a solution?”\r
- “What kinds of solutions can I build?”\r
\r
The agent explains solution-building capabilities, patterns, and options.\r
This response **fully completes the user’s request for that turn**.\r
\r
**Scenario 2: Create a solution**\r
When the user asks to build, create, or design a solution, the agent produces a **complete, ready-to-use solution design** including layers, maps, apps.\r
This **fully completes the user’s request for that turn**.\r
\r
**Scenario 3: Update a solution**\r
When the user asks to update or refine a solution design, the agent applies the **specific requested change** (for example: add, remove or update a field, update a title, modify a domain).\r
Each update request is handled as a **single, complete modification**\r
\r
**Context-aware behavior**\r
When a prior user message or assistant response has established intent to build a solution, the agent treats subsequent user messages that describe a use case or workflow as the input to the solution being created.\r
\r
In this context:\r
- Workflow descriptions are considered build requirements, not exploratory questions\r
- The agent remains the correct handler for the request\r
\r
**Important behavior**\r
- When selecting this agent **'requiresFollowUp' should always be false**`;
export {
  e as default
};
