sfdx-hardis 5.32.1 → 5.33.0

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_AUTORESPONSE_RULES.js

@@ -0,0 +1,42 @@
+const template = {
+    variables: [
+        {
+            name: "AUTORESPONSERULES_NAME",
+            description: "The name of the Salesforce AutoResponse Rules to describe.",
+            example: "Case_AutoResponse_Rules"
+        },
+        {
+            name: "AUTORESPONSERULES_XML",
+            description: "The XML metadata for the Salesforce AutoResponse Rules.",
+            example: "<AutoResponseRules>...</AutoResponseRules>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled business analyst working on a Salesforce project. Your goal is to summarize the content and behavior of the Salesforce AutoResponse Rules "{{AUTORESPONSERULES_NAME}}" in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by explaining the role of the Salesforce AutoResponse Rules that you can guess according to the content of the XML and the name.
+    Try to guess the role of users assigned to this AutoResponse rule. Do not mention the email of assigned users, but you can mention type of assigned users.
+    - Analyze all the AutoResponse rules for objects and in the description tell what are the aim of those rules. What is the role of the object in the system, based by the AutoResponse rules.
+    - Based by Criteria items, explain what would be the response to the user, if the criteria are met.
+
+    2. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+    ### Reference Data:
+
+    - The metadata XML for Salesforce AutoResponse Rule "{{AUTORESPONSERULES_NAME}}" is:
+{{AUTORESPONSERULES_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_AUTORESPONSE_RULES.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_AUTORESPONSE_RULES.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_AUTORESPONSE_RULES.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_AUTORESPONSE_RULES.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,wBAAwB;YAC9B,WAAW,EAAE,4DAA4D;YACzE,OAAO,EAAE,yBAAyB;SACnC;QACD;YACE,IAAI,EAAE,uBAAuB;YAC7B,WAAW,EAAE,yDAAyD;YACtE,OAAO,EAAE,4CAA4C;SACtD;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;CAuBT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_ESCALATION_RULES.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_ESCALATION_RULES.js

@@ -0,0 +1,40 @@
+const template = {
+    variables: [
+        {
+            name: "ESCALATIONRULES_NAME",
+            description: "The name of the Salesforce Escalation Rule to describe.",
+            example: "Case_Escalation_Rule"
+        },
+        {
+            name: "ESCALATIONRULES_XML",
+            description: "The XML metadata for the Salesforce Escalation Rule.",
+            example: "<EscalationRules>...</EscalationRules>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled business analyst working on a Salesforce project. Your goal is to explain the what is the Salesforce Escalation Rule "{{ESCALATIONRULES_NAME}}" about in plain English, provide a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the purpose of the escalation rule.
+    - List the key functionalities and business logic implemented in the escalation rule.
+
+2. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The metadata XML for Escalation Rule "{{ESCALATIONRULES_NAME}}" is:
+{{ESCALATIONRULES_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_ESCALATION_RULES.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_ESCALATION_RULES.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_ESCALATION_RULES.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_ESCALATION_RULES.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,sBAAsB;YAC5B,WAAW,EAAE,yDAAyD;YACtE,OAAO,EAAE,sBAAsB;SAChC;QACD;YACE,IAAI,EAAE,qBAAqB;YAC3B,WAAW,EAAE,sDAAsD;YACnE,OAAO,EAAE,wCAAwC;SAClD;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;CAqBT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW.js

@@ -0,0 +1,40 @@
+const template = {
+    variables: [
+        {
+            name: "FLOW_XML",
+            description: "The XML definition of the Salesforce Flow to describe.",
+            example: "<Flow>...</Flow>"
+        }
+    ],
+    text: {
+        "en": `You are a business analyst working on a Salesforce project. Your goal is to describe the Salesforce Flow in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the purpose and business context of the flow.
+    - Explain what business process or automation this flow supports.
+
+2. **Step-by-Step Description**:
+    - Describe the main steps, decisions, and actions in the flow.
+    - Use plain English and avoid technical jargon when possible.
+    - If there are sub-flows or important conditions, mention them clearly.
+
+3. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (##).
+    - Add a new line before starting a bullet list so mkdocs-material displays it correctly, including for sub-bullets.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The flow XML is:
+{{FLOW_XML}}
+
+Caution: If the XML contains secret tokens or passwords, please replace them with a placeholder (e.g., [REDACTED]). Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_FLOW.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_FLOW.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,wDAAwD;YACrE,OAAO,EAAE,kBAAkB;SAC5B;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;CA0BT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW_DIFF.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW_DIFF.js

@@ -0,0 +1,50 @@
+const template = {
+    variables: [
+        {
+            name: "FLOW_XML_NEW",
+            description: "The XML definition of the new version of the Salesforce Flow.",
+            example: "<Flow>...</Flow>"
+        },
+        {
+            name: "FLOW_XML_PREVIOUS",
+            description: "The XML definition of the previous version of the Salesforce Flow.",
+            example: "<Flow>...</Flow>"
+        }
+    ],
+    text: {
+        "en": `You are a business analyst working on a Salesforce project. Your goal is to describe the differences between the new and previous versions of a Salesforce Flow in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the purpose of the flow and the context for the changes.
+    - Explain why a new version was created if possible.
+
+2. **Describe the Differences**:
+    - List and explain the key changes between the new and previous versions.
+    - Ignore tags related to location attributes (locationX and locationY) or positions: do not mention them in your response.
+    - Ignore nodes and elements that have not changed: do not mention them in your response.
+    - Ignore connector changes: do not mention them in your response.
+    - Use plain English and avoid technical jargon when possible.
+
+3. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (##).
+    - Add a new line before starting a bullet list so mkdocs-material displays it correctly, including for sub-bullets and sub-sub-bullets.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The new version flow XML is:
+{{FLOW_XML_NEW}}
+
+- The previous version flow XML is:
+{{FLOW_XML_PREVIOUS}}
+
+Caution: If the XML contains secret tokens or passwords, please replace them with a placeholder (e.g., [REDACTED]). Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_FLOW_DIFF.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW_DIFF.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_FLOW_DIFF.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_FLOW_DIFF.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,cAAc;YACpB,WAAW,EAAE,+DAA+D;YAC5E,OAAO,EAAE,kBAAkB;SAC5B;QACD;YACE,IAAI,EAAE,mBAAmB;YACzB,WAAW,EAAE,oEAAoE;YACjF,OAAO,EAAE,kBAAkB;SAC5B;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+BT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_LWC.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_LWC.js

@@ -0,0 +1,68 @@
+const template = {
+    variables: [
+        {
+            name: "LWC_NAME",
+            description: "The name of the Lightning Web Component to describe.",
+            example: "myCustomComponent"
+        },
+        {
+            name: "LWC_JS_CODE",
+            description: "The JavaScript code of the Lightning Web Component.",
+            example: "import { LightningElement } from 'lwc'; ..."
+        },
+        {
+            name: "LWC_HTML_CODE",
+            description: "The HTML template code of the Lightning Web Component.",
+            example: "<template>...</template>"
+        },
+        {
+            name: "LWC_JS_META",
+            description: "The meta configuration file for the Lightning Web Component.",
+            example: "<LightningComponentBundle>...</LightningComponentBundle>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled Salesforce developer working on a Lightning Web Components (LWC) project. Your goal is to explain the Salesforce Lightning Web Component "{{LWC_NAME}}" in plain English, providing a detailed explanation suitable for other developers and business users.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the purpose and functionality of the Lightning Web Component.
+    - Describe the key features and capabilities it provides to users.
+    - Explain how it interacts with Salesforce data or other components.
+
+2. **Technical Analysis**:
+    - Describe the main JavaScript methods and their purposes.
+    - Explain how the component handles data binding and events.
+    - Mention any wire services, apex methods, or external services the component uses.
+    - Identify any custom properties or special configurations.
+
+3. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The HTML template for component "{{LWC_NAME}}":
+\`\`\`
+{{LWC_HTML_CODE}}
+\`\`\`
+
+- The JavaScript controller for component "{{LWC_NAME}}":
+\`\`\`
+{{LWC_JS_CODE}}
+\`\`\`
+
+- The metadata configuration for component "{{LWC_NAME}}":
+\`\`\`
+{{LWC_JS_META}}
+\`\`\`
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_LWC.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_LWC.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_LWC.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_LWC.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,sDAAsD;YACnE,OAAO,EAAE,mBAAmB;SAC7B;QACD;YACE,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,qDAAqD;YAClE,OAAO,EAAE,6CAA6C;SACvD;QACD;YACE,IAAI,EAAE,eAAe;YACrB,WAAW,EAAE,wDAAwD;YACrE,OAAO,EAAE,0BAA0B;SACpC;QACD;YACE,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,8DAA8D;YAC3E,OAAO,EAAE,0DAA0D;SACpE;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAuCT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_OBJECT.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_OBJECT.js

@@ -0,0 +1,66 @@
+const template = {
+    variables: [
+        {
+            name: "OBJECT_NAME",
+            description: "The API name of the Salesforce object to describe.",
+            example: "Account"
+        },
+        {
+            name: "OBJECT_XML",
+            description: "The XML metadata definition of the Salesforce object.",
+            example: "<CustomObject>...</CustomObject>"
+        },
+        {
+            name: "ALL_OBJECTS_LIST",
+            description: "A list of all objects in the Salesforce org.",
+            example: "Account, Contact, Opportunity, ..."
+        },
+        {
+            name: "ALL_OBJECT_LINKS",
+            description: "The object model (MasterDetail and Lookup relationships) for all objects.",
+            example: "Account->Contact (Lookup), Opportunity->Account (MasterDetail)"
+        }
+    ],
+    text: {
+        "en": `You are a business analyst working on a Salesforce project. Your goal is to describe the Salesforce object "{{OBJECT_NAME}}" in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the role and purpose of the object "{{OBJECT_NAME}}" in the Salesforce org.
+    - Explain its significance in the project, its purpose in the org's implementation, and any key business processes it supports.
+
+2. **Relationships**:
+    - Use the provided object model data to describe how "{{OBJECT_NAME}}" relates to other objects.
+    - Include:
+        - Direct relationships (MasterDetail and Lookup fields on the object).
+        - Inverse relationships (other objects referencing "{{OBJECT_NAME}}").
+        - Highlight any key dependencies or implications of these relationships in plain English.
+
+3. **Additional Guidance**:
+    - **Do NOT include** fields table or validation rules table in the response
+    - Use the acronyms provided to interpret metadata names (e.g., TR: Trigger, VR: Validation Rule, WF: Workflow).
+    - If the XML metadata contains sensitive information (e.g., tokens, passwords), replace them with a placeholder (e.g., \`[REDACTED]\`).
+
+4. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The list of all objects in the Salesforce org is: {{ALL_OBJECTS_LIST}}
+
+- The object model (MasterDetail and Lookup relationships) is: {{ALL_OBJECT_LINKS}}
+
+- The metadata XML for "{{OBJECT_NAME}}" is:
+{{OBJECT_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_OBJECT.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_OBJECT.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_OBJECT.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_OBJECT.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACvC,SAAS,EAAE;QACP;YACI,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,oDAAoD;YACjE,OAAO,EAAE,SAAS;SACrB;QACD;YACI,IAAI,EAAE,YAAY;YAClB,WAAW,EAAE,uDAAuD;YACpE,OAAO,EAAE,kCAAkC;SAC9C;QACD;YACI,IAAI,EAAE,kBAAkB;YACxB,WAAW,EAAE,8CAA8C;YAC3D,OAAO,EAAE,oCAAoC;SAChD;QACD;YACI,IAAI,EAAE,kBAAkB;YACxB,WAAW,EAAE,2EAA2E;YACxF,OAAO,EAAE,gEAAgE;SAC5E;KACJ;IACD,IAAI,EAAE;QACF,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAqCb;KACI;CACJ,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PAGE.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PAGE.js

@@ -0,0 +1,40 @@
+const template = {
+    variables: [
+        {
+            name: "PAGE_NAME",
+            description: "The name of the Salesforce Lightning Page to describe.",
+            example: "Account_Record_Page"
+        },
+        {
+            name: "PAGE_XML",
+            description: "The XML metadata for the Lightning Page.",
+            example: "<FlexiPage>...</FlexiPage>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled business analyst working on a Salesforce project. Your goal is to summarize the content and behavior of the Salesforce Lightning Page "{{PAGE_NAME}}" in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the role of the lightning page.
+    - List the key tabs, sections, views, related lists and actions described in the lightning page.
+
+2. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The metadata XML for Lightning page "{{PAGE_NAME}}" is:
+{{PAGE_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_PAGE.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PAGE.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_PAGE.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PAGE.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,WAAW;YACjB,WAAW,EAAE,wDAAwD;YACrE,OAAO,EAAE,qBAAqB;SAC/B;QACD;YACE,IAAI,EAAE,UAAU;YAChB,WAAW,EAAE,0CAA0C;YACvD,OAAO,EAAE,4BAA4B;SACtC;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;CAqBT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET.js

@@ -0,0 +1,43 @@
+const template = {
+    variables: [
+        {
+            name: "PERMISSIONSET_NAME",
+            description: "The name of the Salesforce Permission Set to describe.",
+            example: "PS_CloudityAccount"
+        },
+        {
+            name: "PERMISSIONSET_XML",
+            description: "The XML metadata for the Salesforce Permission Set.",
+            example: "<PermissionSet>...</PermissionSet>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled business analyst working on a Salesforce project. Your goal is to summarize the content and behavior of the Salesforce PermissionSet "{{PERMISSIONSET_NAME}}" in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the role of the Salesforce PermissionSet that you can guess according to the content of the XML. Try to guess the role of users assigned to this permission set according to applicationVisibilities, objectVisibilities and userPermissions.
+    - List the key features of the Permission Set.
+      - The most important features are License, Applications, User Permissions ,features with default values ,Custom Objects and Record Types
+      - Ignore Apex classes and Custom Fields
+      - Ignore blocks who has access or visibility set to "false"
+
+2. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The metadata XML for Salesforce Permission Set "{{PERMISSIONSET_NAME}}" is:
+{{PERMISSIONSET_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_PERMISSION_SET.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_PERMISSION_SET.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,oBAAoB;YAC1B,WAAW,EAAE,wDAAwD;YACrE,OAAO,EAAE,oBAAoB;SAC9B;QACD;YACE,IAAI,EAAE,mBAAmB;YACzB,WAAW,EAAE,qDAAqD;YAClE,OAAO,EAAE,oCAAoC;SAC9C;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;CAwBT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET_GROUP.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET_GROUP.js

@@ -0,0 +1,40 @@
+const template = {
+    variables: [
+        {
+            name: "PERMISSIONSETGROUP_NAME",
+            description: "The name of the Salesforce Permission Set Group to describe.",
+            example: "PS_CloudityAdmin"
+        },
+        {
+            name: "PERMISSIONSETGROUP_XML",
+            description: "The XML metadata for the Salesforce Permission Set Group.",
+            example: "<PermissionSetGroup>...</PermissionSetGroup>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled business analyst working on a Salesforce project. Your goal is to summarize the content and behavior of the Salesforce PermissionSetGroup "{{PERMISSIONSETGROUP_NAME}}" in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the role of the Salesforce PermissionSetGroup that you can guess according to the content of the XML. Try to guess the role of users assigned to this permission set group according to the name, description and related Permission Sets
+    - List the key features of the Permission Set.
+
+2. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The metadata XML for Salesforce Permission Set Group "{{PERMISSIONSETGROUP_NAME}}" is:
+{{PERMISSIONSETGROUP_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_PERMISSION_SET_GROUP.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET_GROUP.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_PERMISSION_SET_GROUP.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PERMISSION_SET_GROUP.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,yBAAyB;YAC/B,WAAW,EAAE,8DAA8D;YAC3E,OAAO,EAAE,kBAAkB;SAC5B;QACD;YACE,IAAI,EAAE,wBAAwB;YAC9B,WAAW,EAAE,2DAA2D;YACxE,OAAO,EAAE,8CAA8C;SACxD;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;CAqBT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PROFILE.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PROFILE.js

@@ -0,0 +1,43 @@
+const template = {
+    variables: [
+        {
+            name: "PROFILE_NAME",
+            description: "The name of the Salesforce Profile to describe.",
+            example: "Cloudity Sales"
+        },
+        {
+            name: "PROFILE_XML",
+            description: "The XML metadata for the Salesforce Profile.",
+            example: "<Profile>...</Profile>"
+        }
+    ],
+    text: {
+        "en": `You are a skilled business analyst working on a Salesforce project. Your goal is to summarize the content and behavior of the Salesforce Profile "{{PROFILE_NAME}}" in plain English, providing a detailed explanation suitable for a business user.
+
+### Instructions:
+
+1. **Contextual Overview**:
+    - Begin by summarizing the role of the Salesforce Profile that you can guess according to the content of the XML. Try to guess the role of users assigned to this profile according to applicationVisibilities, objectVisibilities and userPermissions.
+    - List the key features of the Profiles.
+      - The most important features are License, Applications, User Permissions ,features with default values ,Custom Objects and Record Types
+      - Ignore Apex classes and Custom Fields
+      - Ignore blocks who has access or visibility set to "false"
+
+2. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (\`##\`).
+    - Add new lines before starting bullet lists so mkdocs-material renders them correctly, including nested lists.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The metadata XML for Salesforce Profile "{{PROFILE_NAME}}" is:
+{{PROFILE_XML}}
+
+Caution: Redact any sensitive information and replace with \`[REDACTED]\`. Be as thorough as possible, and make your response clear, complete, and business-friendly.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_DESCRIBE_PROFILE.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PROFILE.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_DESCRIBE_PROFILE.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_DESCRIBE_PROFILE.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,cAAc;YACpB,WAAW,EAAE,iDAAiD;YAC9D,OAAO,EAAE,gBAAgB;SAC1B;QACD;YACE,IAAI,EAAE,aAAa;YACnB,WAAW,EAAE,8CAA8C;YAC3D,OAAO,EAAE,wBAAwB;SAClC;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;CAwBT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/PROMPT_SOLVE_DEPLOYMENT_ERROR.d.ts

@@ -0,0 +1,3 @@
+import { PromptTemplateDefinition } from "./types.js";
+declare const template: PromptTemplateDefinition;
+export default template;

package/lib/common/aiProvider/promptTemplates/PROMPT_SOLVE_DEPLOYMENT_ERROR.js

@@ -0,0 +1,40 @@
+const template = {
+    variables: [
+        {
+            name: "ERROR",
+            description: "The Salesforce deployment error message to analyze and solve.",
+            example: "Cannot deploy component: missing field 'X' on object 'Y'"
+        }
+    ],
+    text: {
+        "en": `You are a Salesforce release manager using Salesforce CLI commands to perform deployments. Your goal is to help solve the following Salesforce deployment error in a clear, actionable way for a technical user.
+
+### Instructions:
+
+1. **Error Analysis**:
+    - Analyze the error message and identify the root cause.
+    - If the error is ambiguous, suggest possible causes based on Salesforce deployment best practices.
+
+2. **Solution Proposal**:
+    - Provide a step-by-step solution to resolve the error.
+    - If applicable, include the correct sfdx source format or XML example.
+    - Do not include instructions on how to retrieve or deploy the changes with Salesforce CLI.
+
+3. **Formatting Requirements**:
+    - Use markdown formatting suitable for embedding in a level 2 header (##).
+    - Add new lines before starting bullet lists so mkdocs-material displays them correctly, including for sub-bullets.
+    - Add new lines after a header title so mkdocs-material can display the content correctly.
+    - Never truncate any information in the response.
+    - Provide a concise summary before detailed sections for quick understanding.
+
+### Reference Data:
+
+- The deployment error returned by Salesforce CLI is:
+{{ERROR}}
+
+Caution: If the error message contains secret tokens or passwords, please replace them with a placeholder (e.g., [REDACTED]). Be as thorough as possible, and make your response clear, complete, and actionable.
+`,
+    },
+};
+export default template;
+//# sourceMappingURL=PROMPT_SOLVE_DEPLOYMENT_ERROR.js.map

package/lib/common/aiProvider/promptTemplates/PROMPT_SOLVE_DEPLOYMENT_ERROR.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"PROMPT_SOLVE_DEPLOYMENT_ERROR.js","sourceRoot":"","sources":["../../../../src/common/aiProvider/promptTemplates/PROMPT_SOLVE_DEPLOYMENT_ERROR.ts"],"names":[],"mappings":"AAEA,MAAM,QAAQ,GAA6B;IACzC,SAAS,EAAE;QACT;YACE,IAAI,EAAE,OAAO;YACb,WAAW,EAAE,+DAA+D;YAC5E,OAAO,EAAE,0DAA0D;SACpE;KACF;IACD,IAAI,EAAE;QACJ,IAAI,EAAE;;;;;;;;;;;;;;;;;;;;;;;;;;CA0BT;KACE;CACF,CAAC;AAEF,eAAe,QAAQ,CAAC"}

package/lib/common/aiProvider/promptTemplates/index.d.ts

@@ -0,0 +1,2 @@
+import { PromptTemplateDefinition } from "./types.js";
+export declare const PROMPT_TEMPLATES: Record<string, PromptTemplateDefinition>;