@salesforce/afv-skills 1.39.0 → 1.40.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.39.0",
+  "version": "1.40.0",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [
@@ -11,8 +11,8 @@
     "registry": "https://registry.npmjs.org"
   },
   "devDependencies": {
-    "@salesforce/ui-bundle-template-app-react-sample-b2e": "^10.2.2",
-    "@salesforce/ui-bundle-template-app-react-sample-b2x": "^10.2.2",
+    "@salesforce/ui-bundle-template-app-react-sample-b2e": "^11.57.2",
+    "@salesforce/ui-bundle-template-app-react-sample-b2x": "^11.57.2",
     "@salesforce/webapp-template-app-react-sample-b2e-experimental": "^1.117.1",
     "@salesforce/webapp-template-app-react-sample-b2x-experimental": "^1.117.1",
     "@types/js-yaml": "^4.0.9",

package/skills/agentforce-architecture-analyze/SKILL.md

@@ -3,6 +3,7 @@ name: agentforce-architecture-analyze
 description: "Declared architecture snapshot for one Agentforce agent: planner, topics, actions, flows, Apex, prompt templates, and NGA plugins. Renders a human-readable architecture document and Mermaid invocation graph from design-time metadata (not runtime audit rows). TRIGGER when user asks to describe, diagram, inventory, audit, document, or diff (e.g. v3 vs v5) the architecture / action tree / topic structure / tool inventory of a specific agent by agent API name in a specific org. DO NOT TRIGGER for runtime session traces, conversation transcripts, generation timings, or gateway audit chains — this skill reads design-time metadata only (use agentforce-d360-analyze for session traces)."
 metadata:
   version: "1.0"
+  domains: ["Agentforce"]
   minApiVersion: "64.0"
   relatedSkills:
     - "agentforce-d360-analyze"

package/skills/agentforce-bot-upgrade/SKILL.md

@@ -4,6 +4,7 @@ description: "Use this skill to Upgrade Einstein Bots into Agentforce agents end
 argument-hint: "[--mode <online|offline>] [--org-alias <org-alias> --bots <bot1:v1,bot2:v2,...> | --offline-dir <offline-dir> [--bots <bot1,bot2,...>]] [--interactive <true|false>]"
 metadata:
   version: "1.0"
+  domains: ["Agentforce"]
   minApiVersion: "63.0"
   relatedSkills:
     - "agentforce-generate"

package/skills/agentforce-d360-analyze/SKILL.md

@@ -3,6 +3,7 @@ name: agentforce-d360-analyze
 description: "Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud."
 metadata:
   version: "1.0"
+  domains: ["Agentforce", "Data 360"]
   minApiVersion: "66.0"
   relatedSkills:
     - "agentforce-architecture-analyze"

package/skills/agentforce-generate/SKILL.md

@@ -3,6 +3,7 @@ name: agentforce-generate
 description: "Build, modify, audit, repair, optimize, debug, and deploy agents with Agentforce Agent Script. TRIGGER when: user creates, reviews, or changes .agent files or aiAuthoringBundle metadata; asks to fix AgentScript, audit an existing agent, run an AgentScript health check, common-pitfall review, or baseline-versus-candidate repair loop; changes a response, action, subagent, route, state flow, or Agent Spec; previews, debugs, deploys, publishes, or tests agents; uses sf agent generate/preview/publish/test; or manages Agentforce MCP servers, tools, assets, or authentication. DO NOT TRIGGER when: Apex, Flow, Prompt Template, Experience Cloud, or general Salesforce CLI work is unrelated to Agent Script; or the primary input is a production session or trace ID rather than an agent artifact."
 metadata:
   version: "0.11"
+  domains: ["Agentforce"]
   minApiVersion: "66.0"
   relatedSkills:
     - "agentforce-observe"

package/skills/agentforce-observe/SKILL.md

@@ -7,6 +7,7 @@ metadata:
     - "agentforce-generate"
     - "agentforce-test"
   version: "0.8"
+  domains: ["Agentforce", "Data 360"]
   cliTools:
     - tool: ["git"]
       semver: ">=2.0.0"

package/skills/agentforce-test/SKILL.md

@@ -7,6 +7,7 @@ metadata:
     - "agentforce-generate"
     - "agentforce-observe"
   version: "0.8"
+  domains: ["Agentforce"]
   cliTools:
     - tool: ["curl"]
       semver: ">=7.0.0"

package/skills/automation-flow-generate/SKILL.md

@@ -3,6 +3,7 @@ name: automation-flow-generate
 description: "Generate Salesforce Flows using the MCP tool execute_metadata_action. Use when the user asks to create, build, or generate a flow — including Screen, Autolaunched, Record-Triggered (before/after-save), Scheduled. Also trigger for flow-like requests such as \"when a record is created\", \"trigger daily at\", \"send an email when\", \"update the field when\", \"automate\", \"workflow\", or \"flow XML/metadata\". This is the only skill for Salesforce Flow generation."
 metadata:
   version: "1.0"
+  domains: ["Automation"]
   minApiVersion: "60.0"
 ---
 

package/skills/automation-sandbox-post-copy-config-generate/SKILL.md

@@ -3,6 +3,7 @@ name: automation-sandbox-post-copy-config-generate
 description: "Generate the JSON config file that the Salesforce sandbox post-copy automation tool consumes, from a customer SOP in any format (PDF, xlsx, csv, JSON, docx, Markdown, plain text, or a screenshot of an endpoint table). Use when the user asks to create, build, generate, produce, or convert a post-copy or post-refresh automation config — turning a sandbox-refresh SOP into a JSON array of OutboundMessages and RemoteSiteSettings entries with ConfigurationName, Label, Fields, IsActive, and ExecutionOrder. Also trigger for phrasings like \"post-copy config\", \"post-refresh automation JSON\", \"update the outbound message (OBM) endpoints after refresh\", \"convert this SOP to config\", \"remote site settings JSON\", \"refresh planner to JSON\", or \"sandbox refresh config\". DO NOT TRIGGER when: user wants to deploy the generated config to an org (use platform-metadata-deploy), or apply/execute/run/dry-run the post-copy automation JSON against a sandbox (use automation-sandbox-post-copy-configure)."
 metadata:
   version: "1.0"
+  domains: ["Automation"]
 ---
 
 # Automation: Sandbox Post-Copy Config Generate

package/skills/automation-sandbox-post-copy-configure/SKILL.md

@@ -4,6 +4,7 @@ description: "Apply a Salesforce sandbox post-copy automation JSON config agains
 allowed-tools: Bash Read Write
 metadata:
   version: "1.0"
+  domains: ["Automation"]
   cliTools:
     - tool: ["curl"]
       semver: ">=7.0.0"

package/skills/commerce-b2b-open-code-components-integrate/SKILL.md

@@ -4,6 +4,7 @@ description: "Integrate Salesforce B2B Commerce open source components from GitH
 allowed-tools: Bash(git clone:*) Bash(cp:*) Read
 metadata:
   version: "1.0"
+  domains: ["Commerce", "Experience"]
   minApiVersion: "56.0"
   relatedSkills:
     - "commerce-b2b-store-create"

package/skills/commerce-b2b-open-code-components-replace/SKILL.md

@@ -6,6 +6,7 @@ metadata:
   relatedSkills:
     - "commerce-b2b-open-code-components-integrate"
   version: "1.0"
+  domains: ["Commerce", "Experience"]
 ---
 
 # Replacing OOTB B2B Commerce Components with Open Code

package/skills/commerce-b2b-store-create/SKILL.md

@@ -3,6 +3,7 @@ name: commerce-b2b-store-create
 description: "Interactive workflow to create Commerce B2B Stores and retrieve storefront metadata. Use when users want to: create B2B Commerce stores, build Commerce storefronts, set up B2B stores from Vibes, retrieve Commerce metadata, deploy Commerce experiences, work with DigitalExperienceBundle for Commerce."
 metadata:
   version: "1.0"
+  domains: ["Commerce", "Experience"]
   minApiVersion: "56.0"
   cliTools:
     - tool: ["sf"]

package/skills/data360-activate/SKILL.md

@@ -15,6 +15,7 @@ metadata:
     - "data360-query"
     - "data360-segment"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-activate: Data Cloud Act Phase

package/skills/data360-code-extension-generate/SKILL.md

@@ -3,6 +3,7 @@ name: data360-code-extension-generate
 description: "Develop and deploy Data Cloud Code Extensions using SF CLI plugin. Use this skill when creating custom Python transformations for Data Cloud, deploying code extensions, or testing data transformations. Supports init, run, scan, and deploy operations."
 metadata:
   version: "1.0"
+  domains: ["Data 360", "Developer Experience"]
   relatedSkills:
     - "data360-schema-get"
   cliTools:

package/skills/data360-connect/SKILL.md

@@ -14,6 +14,7 @@ metadata:
     - "data360-prepare"
     - "data360-query"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-connect: Data Cloud Connect Phase

package/skills/data360-harmonize/SKILL.md

@@ -14,6 +14,7 @@ metadata:
     - "data360-query"
     - "data360-segment"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-harmonize: Data Cloud Harmonize Phase

package/skills/data360-orchestrate/SKILL.md

@@ -33,6 +33,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-orchestrate: Salesforce Data Cloud Orchestrator

package/skills/data360-prepare/SKILL.md

@@ -17,6 +17,7 @@ metadata:
     - "data360-orchestrate"
     - "data360-query"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-prepare: Data Cloud Prepare Phase

package/skills/data360-query/SKILL.md

@@ -13,6 +13,7 @@ metadata:
     - "data360-segment"
     - "platform-soql-query"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-query: Data Cloud Retrieve Phase

package/skills/data360-schema-get/SKILL.md

@@ -10,6 +10,7 @@ metadata:
     - tool: ["sf"]
       semver: ">=2.0.0"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-schema-get Skill

package/skills/data360-segment/SKILL.md

@@ -14,6 +14,7 @@ metadata:
     - "data360-orchestrate"
     - "data360-query"
   version: "1.0"
+  domains: ["Data 360"]
 ---
 
 # data360-segment: Data Cloud Segment Phase

package/skills/design-systems-slds-apply/SKILL.md

@@ -3,6 +3,7 @@ name: design-systems-slds-apply
 description: "Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\"."
 metadata:
   version: "1.1"
+  domains: ["Design Systems"]
   relatedSkills:
     - "design-systems-slds-validate"
   cliTools:

package/skills/design-systems-slds-validate/SKILL.md

@@ -3,6 +3,7 @@ name: design-systems-slds-validate
 description: "Audit Lightning Web Components for SLDS design-system compliance and produce a scored quality report. Runs the SLDS linter and analyzes CSS for theming hook usage and pairing, scoring SLDS findings across categories into an overall grade. Use when asked to \"score my component's SLDS\", \"SLDS scorecard\", \"SLDS quality report\", \"audit SLDS compliance\", \"how good is my SLDS\", \"check SLDS quality\", \"rate my SLDS styling\", \"evaluate my component's SLDS\", \"is this component's SLDS ready to ship?\", \"look at my LWC for SLDS issues\", \"audit SLDS before I submit\", \"review my component's SLDS before code review\", or any time a user wants an SLDS quality assessment or SLDS production-readiness check on an LWC. Not for fixing violations (use design-systems-slds2-migrate), building new components (use design-systems-slds-apply), or accessibility/WCAG/ARIA audits (use experience-lwc-accessibility-validate)."
 metadata:
   version: "1.0"
+  domains: ["Design Systems"]
   relatedSkills:
     - "design-systems-slds-apply"
     - "design-systems-slds2-migrate"

package/skills/design-systems-slds2-migrate/SKILL.md

@@ -3,6 +3,7 @@ name: design-systems-slds2-migrate
 description: "Migrate Lightning Web Components from SLDS 1 to SLDS 2 by running the SLDS linter and fixing violations. Use this skill whenever users mention SLDS 2, SLDS uplift, linter violations, LWC token migration, class overrides, hardcoded CSS values that need SLDS hook replacement, or styling hook selection. Covers all styling hook categories — color, spacing, sizing, typography, borders, radius, and shadows. Also use when users mention no-hardcoded-values, no-slds-class-overrides, lwc-to-slds-hooks, no-deprecated-tokens-slds1, or ask about SLDS component migration — even if they don't explicitly say \"uplift\" or \"migration\"."
 metadata:
   version: "1.0"
+  domains: ["Design Systems"]
   cliTools:
     - tool: ["npx"]
       semver: ">=7.0.0"

package/skills/dx-apexguru-scan/SKILL.md

@@ -5,6 +5,7 @@ allowed-tools: Read, Bash(bash), Bash(node), Bash(curl), Bash(zip), Bash(unzip),
 argument-hint: "[project-path] [--org <alias>] [--fast]"
 metadata:
   version: "1.1"
+  domains: ["Developer Experience"]
   relatedSkills:
     - "dx-code-analyzer-run"
   cliTools:

package/skills/dx-app-analytics-query/SKILL.md

@@ -10,6 +10,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "56.0"
 ---
 

package/skills/dx-code-analyzer-configure/SKILL.md

@@ -3,6 +3,7 @@ name: dx-code-analyzer-configure
 description: "Set up, configure, and troubleshoot Salesforce Code Analyzer for any project. Handles installation, prerequisite checks, diagnosing broken setups, creating and editing code-analyzer.yml overrides, engine-specific settings, ignore patterns, severity overrides, and CI/CD pipeline setup. TRIGGER when: user says 'set up code analyzer', 'configure code analyzer', 'install code analyzer', 'code analyzer not working', 'fix my setup', 'scan failing', 'check my setup', 'enable/disable engine', 'exclude files', 'change severity', 'set up GitHub Actions', 'set up CI/CD', 'add to pipeline', 'pipeline fail', 'update my workflow', 'quality gate', 'fail on violations', 'scan changed files only', 'add SARIF', 'code-analyzer.yml', 'ESLint config', 'increase SFGE memory', or reports errors running Code Analyzer. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), fix violations, explain rules, create custom rules (use dx-code-analyzer-custom-rule-create), or suppress violations."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   relatedSkills:
     - "dx-code-analyzer-custom-rule-create"
     - "dx-code-analyzer-run"

package/skills/dx-code-analyzer-custom-rule-create/SKILL.md

@@ -3,6 +3,7 @@ name: dx-code-analyzer-custom-rule-create
 description: "Create custom Code Analyzer rules for Regex (pattern matching), PMD (XPath/AST for Apex and metadata XML), and ESLint (LWC/JavaScript/TypeScript). Use when users want to enforce coding standards, ban patterns, detect hardcoded values, govern metadata, or add rules not in the built-in set. TRIGGER when: user says 'create a rule', 'ban System.debug', 'enforce naming convention', 'detect hardcoded IDs', 'custom rule', 'xpath rule', 'regex rule', 'add a PMD rule', 'enforce a policy', 'create a check for', 'flag this pattern', 'make a rule that catches', 'metadata rule', 'check permissions', 'enforce API version', 'eslint rule', 'lwc rule', 'override rule threshold', 'customize complexity', or describes a pattern to enforce. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), configure engines (use dx-code-analyzer-configure), or explain existing rules (use dx-code-analyzer-run)."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   relatedSkills:
     - "dx-code-analyzer-configure"
     - "dx-code-analyzer-run"

package/skills/dx-code-analyzer-run/SKILL.md

@@ -3,6 +3,7 @@ name: dx-code-analyzer-run
 description: "Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', 'show security violations', 'what is this rule', 'explain ApexCRUDViolation', 'filter results', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). Use this skill for scanning, exploring results, and listing rules. DO NOT TRIGGER when: user asks only about installation/configuration (use dx-code-analyzer-configure), or wants to create a custom rule (use dx-code-analyzer-custom-rule-create)."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   relatedSkills:
     - "dx-code-analyzer-configure"
     - "dx-code-analyzer-custom-rule-create"

package/skills/dx-devops-pipeline-manage/SKILL.md

@@ -3,6 +3,7 @@ name: dx-devops-pipeline-manage
 description: "Use this skill to manage the full lifecycle of a DevOps Center pipeline — list all pipelines, get a single pipeline's details, create a new pipeline linked to a Git repository, add or remove stages, rename a stage, add or remove Salesforce environments on stages, attach or detach projects, and activate or deactivate the pipeline. Invoke when the user wants to set up a release pipeline, wire promotion stages across integration, UAT, staging, and production orgs, connect environments to stages, attach a project, or activate a continuous delivery pipeline. Uses sf devops pipeline and sf devops stage commands with --json output. DO NOT TRIGGER for work-item lifecycle, promotion or deployment execution, conflict detection, or standalone project creation (separate skills)."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "58.0"
   relatedSkills:
     - "dx-devops-work-item-manage"

package/skills/dx-devops-promote/SKILL.md

@@ -3,6 +3,7 @@ name: dx-devops-promote
 description: "Use this skill to drive the full DevOps Center promotion workflow for work items and pipeline stages — validate preconditions, prepare work items, optionally combine work items that share metadata, promote one or more work items or an entire stage to a target pipeline stage, and complete the promotion to finalize the deployment. TRIGGER when the user wants to promote a work item, advance changes to the next environment or stage, combine work items for a single promotion, or move metadata through the release pipeline. The mandatory validate step runs automatically at the start. DO NOT TRIGGER for work item creation or status updates (use dx-devops-work-item-manage), for conflict detection, or for polling an existing promotion's status."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "58.0"
   relatedSkills:
     - "dx-devops-work-item-manage"

package/skills/dx-devops-test-failures-analyze/SKILL.md

@@ -11,6 +11,7 @@ metadata:
     - "platform-apex-generate"
     - "platform-apex-test-generate"
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "67.0"
 ---
 

package/skills/dx-devops-test-pipeline-configure/SKILL.md

@@ -10,6 +10,7 @@ metadata:
     - "dx-devops-test-suite-assignments-configure"
     - "dx-devops-test-suite-run"
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "67.0"
 ---
 

package/skills/dx-devops-test-suite-assignments-configure/SKILL.md

@@ -12,6 +12,7 @@ metadata:
     - "platform-apex-test-generate"
     - "platform-apex-test-run"
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "67.0"
 ---
 

package/skills/dx-devops-test-suite-run/SKILL.md

@@ -11,6 +11,7 @@ metadata:
     - "dx-devops-test-suite-assignments-configure"
     - "platform-apex-test-run"
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "67.0"
 ---
 

package/skills/dx-devops-work-item-manage/SKILL.md

@@ -3,6 +3,7 @@ name: dx-devops-work-item-manage
 description: "Use this skill to manage the full lifecycle of DevOps Center work items — list, create, update, commit changes, perform status transitions, and create pull requests. Update fields like subject, description, and status. Commit and push code changes to work item branches. Create pull requests for work item branches via DevOps Center API. Invoke when the user wants to track, find, create, or update a work item, commit changes to a work item branch, advance a work item's status through the pipeline, or create a pull request for code review. Consolidates sf devops work-item and review operations. DO NOT TRIGGER for promotion or deployment operations, or conflict detection."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   minApiVersion: "58.0"
   cliTools:
     - tool: ["sf"]

package/skills/dx-org-devhub-configure/SKILL.md

@@ -4,6 +4,7 @@ description: "Enable Dev Hub on a Salesforce org and view its scratch org alloca
 allowed-tools: Read, Bash(bash), Bash(sf api request rest), Bash(sf data query), Bash(sf org list), Bash(sf org login web), Bash(sf org login device), Bash(sf project deploy), Bash(sf config get), Bash(sf org display), Bash(sf org open), Bash(jq)
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   # DevHubSettings metadata + the Tooling API DevHubSettings endpoint require
   # API 47.0 or later (see scripts/devhub.sh SETTINGS_API_VERSION).
   minApiVersion: "47.0"

package/skills/dx-org-manage/SKILL.md

@@ -3,6 +3,7 @@ name: dx-org-manage
 description: "INVOKE this skill to execute Salesforce org operations: create scratch orgs, list/display/resume/delete scratch orgs, create org snapshots, open orgs in browser. This skill EXECUTES operations immediately - it does NOT generate scripts or code files. ALWAYS invoke this skill (do not execute SF CLI commands directly) when user requests to: create a scratch org (from edition, definition file (.json), snapshot, or org shape), list/display/resume/delete scratch orgs, create an org snapshot, or open a Salesforce org. Trigger phrases include: 'create a snapshot', 'take a snapshot', 'create scratch org', 'new scratch org', 'spin up an org', 'create 5 scratch orgs', 'create org from snapshot', 'scratch-def.json', 'project-scratch-def.json', 'list scratch orgs', 'display org', 'delete scratch org', 'resume scratch org', 'open my Salesforce org', 'open org in browser'. Do NOT use for switching default org (use dx-org-switch) or deploying metadata (use platform-metadata-deploy)."
 metadata:
   version: "1.2"
+  domains: ["Developer Experience"]
   minApiVersion: "60.0"
   relatedSkills:
     - "dx-org-switch"

package/skills/dx-org-permission-set-assign/SKILL.md

@@ -3,6 +3,7 @@ name: dx-org-permission-set-assign
 description: "ALWAYS USE THIS SKILL to assign permission sets to org users. Assign one or more permission sets to org users using the sf org assign permset command. TRIGGER when the user asks to assign, grant, give, add, or apply permission sets to users, admins, specific orgs, or specific users. Supports granting permissions, giving access, and adding permission sets to default admin or specific users via --on-behalf-of. DO NOT TRIGGER for listing permission sets or checking user permissions."
 metadata:
   version: "1.0"
+  domains: ["Developer Experience"]
   relatedSkills:
     - "platform-permission-set-generate"
   cliTools:

package/skills/dx-org-switch/SKILL.md

@@ -6,6 +6,7 @@ metadata:
     - tool: ["sf"]
       semver: ">=2.0.0"
   version: "1.0"
+  domains: ["Developer Experience"]
 ---
 
 ## Steps

package/skills/dx-org-trial-expiration-check/SKILL.md

@@ -4,6 +4,7 @@ description: "Check when Salesforce orgs expire (or already expired) and what to
 allowed-tools: Read, Bash(bash), Bash(sf data query), Bash(sf org list), Bash(sf config get), Bash(jq), Bash(date)
 metadata:
   version: "2.0"
+  domains: ["Developer Experience"]
   cliTools:
     - tool: ["jq"]
       semver: ">=1.6.0"

package/skills/dx-pkg-post-install-configure/SKILL.md

@@ -3,6 +3,7 @@ name: dx-pkg-post-install-configure
 description: "Use this skill to automate managed package post-install configuration. Package-agnostic — works with any managed package (LMA, FMA, work.com, Certinia, etc.). TRIGGER when: user installs a managed package and needs post-install configuration, mentions LMA/FMA/work.com post-install setup, asks to configure permission sets/FLS/page layouts for an installed package, says 'post-install', 'package setup', 'configure LMA', 'set up FMA', 'post-install steps'. DO NOT TRIGGER for: standalone permission set assignment (use dx-org-permission-set-assign), generating permission set metadata XML (use platform-permission-set-generate), package installation, or org switching."
 metadata:
   version: "2.2"
+  domains: ["Developer Experience"]
   minApiVersion: "67.0"
   cliTools:
     - tool: ["sf"]

package/skills/experience-aura-lwc-migrate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-aura-lwc-migrate
 description: "Use this skill to analyze a Salesforce Aura component bundle (.cmp, .app, .evt, .intf, Controller.js, Helper.js, Renderer.js) and produce a framework-agnostic migration blueprint (PRD.yaml / PRD.md / PRD.json) capturing public API, data requirements, slots, events, states, accessibility, styling, localization, and security posture. This is Phase 1 (analysis + PRD) only — it does NOT author or edit component code, wire adapters, or Jest tests, and does not write .html/.js/.css/.js-meta.xml. TRIGGER when the user says \"analyze this Aura component\", \"migrate Aura\", \"convert .cmp\", \"produce a migration blueprint\", \"generate a PRD for this Aura component\", or mentions aura:attribute, aura:handler, force:recordData, $Label, $Resource, component.get, cmp.find, or an input directory containing .cmp files. DO NOT TRIGGER when there is no Aura source (delegate downstream LWC authoring to experience-lwc-generate), for post-migration scoring, or for refactoring an existing modern component."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - experience-lwc-generate
 ---

package/skills/experience-cms-brand-apply/SKILL.md

@@ -3,6 +3,7 @@ name: experience-cms-brand-apply
 description: "Extracts, retrieves, and applies CMS brand guidelines (voice, tone, style, colors, typography) to generated content. Use this skill ANY TIME a user request involves branding, brand voice, brand tone, brand guidelines, brand identity, brand styling, or applying a brand to content. Triggers for requests like \"apply my brand\", \"use our brand voice\", \"match our brand guidelines\", \"find my brand\", \"search for brand\", \"get brand instructions\", \"apply brand tone\". Handles the full workflow: searching for brands in Salesforce CMS, extracting brand instructions, and applying brand voice/tone/guidelines to generated content. Does not apply to media/image search (use experience-content-media-search skill), logo search, or creating new brand definitions."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
 ---
 
 # Applying CMS Brand

package/skills/experience-content-media-search/SKILL.md

@@ -3,6 +3,7 @@ name: experience-content-media-search
 description: "Searches for and retrieves existing visual media (images, logos, icons, photos, graphics, banners, thumbnails, hero images, backgrounds) from sources such as Salesforce CMS, Data 360 or any other source. Use this skill ANY TIME a user request involves finding, searching, getting, fetching, retrieving, grab, looking up, locating media. NEVER call search_media_cms_channels, search_electronic_media tools directly — always go through this skill first. This skill must be activated before any tool is used for media search or retrieval, without exception.  Takes PRIORITY and activates FIRST when ANY media search/retrieval is mentioned, regardless of what else happens with the media afterward. Triggers for requests like \"search for logo\", \"find hero image\", \"get company logo\", \"locate icons\", \"fetch background image\", \"retrieve product photos\". Handles the search and source selection workflow. Does not apply when the request is about brand search, to generate NEW images with AI, or edit existing images."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-content-media-stock-image-search"
   mcpTools:

package/skills/experience-content-media-stock-image-search/SKILL.md

@@ -3,6 +3,7 @@ name: experience-content-media-stock-image-search
 description: "Searches for and downloads ethically-licensed stock images via the media-management MCP server. Use this skill whenever a user wants an image, photo, or picture — for BOTH requests to find existing imagery (\"find a stock image\", \"search for a photo of X\", \"get a royalty-free image\", \"find an ethical image\", editorial/news photography) AND requests phrased ambiguously as creating or generating one (\"create an image of a sunset\", \"generate a picture of a team meeting\", \"make me a mountain image\") — treat these as stock search requests, since this skill searches a stock photo library, it does not generate images. Do NOT offer alternative search methods or ask the user to pick one. Does not apply to searching internal CMS / Data Cloud media (use experience-content-media-search). Does not apply when the user explicitly asks for AI-generated, synthetic, or computer-generated imagery — this skill only searches licensed stock photography and has no image-generation capability."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-content-media-search"
   cliTools:

package/skills/experience-lds-best-practices-apply/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lds-best-practices-apply
 description: "Use when reviewing or implementing Lightning Data Service best practices in an LWC (.js, .html, .js-meta.xml) — UIAPI vs Apex, refreshApex / notifyRecordUpdateAvailable, @salesforce/schema imports, LDS record-form data patterns. TRIGGER on \"apply LDS best practices to this LWC\", \"review this LWC for LDS best-practice issues\", \"review this component for Lightning Data Service issues\", \"UIAPI or Apex for this data?\", \"fix stale data after record save\", \"sync LDS cache\", \"use @salesforce/schema for field names\", \"choose between getRecord and Apex\". DO NOT TRIGGER when building a new LWC (use experience-lwc-generate), applying SLDS design tokens (use design-systems-slds-apply), picking or wiring a `lightning-*` base component's props/events/slots generically (use experience-lwc-base-components-integrate — this skill covers only the LDS data-layer rationale, even when the fix involves a base record form), or for security / RTL / accessibility reviews (separate passes)."
 metadata:
   version: "1.0"
+  domains: ["Experience", "Platform"]
   relatedSkills:
     - design-systems-slds-apply
     - experience-lwc-base-components-integrate

package/skills/experience-lds-data-requirements-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lds-data-requirements-generate
 description: "Use when a Lightning Web Component data need is described in ambiguous natural language — turn \"get contact info\" or \"show account data\" into a clear, PRD-ready data-requirements spec. TRIGGER when the user says \"define data requirements for this LWC\", \"turn this PRD data section into validated object/field names\", \"recommend GraphQL vs UIAPI for this data need\", \"validate these Salesforce API names\", or \"spec out the LDS adapter for this component\", or references LWC bundle files (`.js`, `.js-meta.xml`) whose data layer is not yet specified. DO NOT TRIGGER when the data layer is already fully specified, when authoring the actual query or adapter code from a known spec, or when implementing an LWC end-to-end (use experience-lwc-generate)."
 metadata:
   version: "1.0"
+  domains: ["Experience", "Platform"]
   relatedSkills:
     - experience-lwc-generate
 ---

package/skills/experience-lds-graphql-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lds-graphql-generate
 description: "Use ALWAYS when a prompt mentions GraphQL, lightning/uiGraphQLApi, @wire(graphql, ...), or gql template tags in an LWC context — even if the surface ask is \"build an LWC\". Owns the ENTIRE flow: introspect the org's LDS GraphQL schema, identify entities/fields, construct the schema-validated gql query or mutation, wire it into the LWC via lightning/uiGraphQLApi, verify against a connected org. REQUIRED whenever a prompt asks to render, list, or edit Salesforce records (Account, Contact, Case, custom objects) via GraphQL — the .html and .js scaffolding IS in scope. DO NOT delegate to experience-lwc-generate: that skill has NO GraphQL schema introspection, NO create_lds_graphql_read_query binding, and defaults to getRecord/getRelatedListRecords wire adapters which will not satisfy a GraphQL prompt. DO NOT TRIGGER only if the prompt forbids GraphQL, chooses UIAPI/Apex (use experience-lds-best-practices-apply), or asks for data requirements (use experience-lds-data-requirements-generate)."
 metadata:
   version: "1.0"
+  domains: ["Experience", "Platform"]
   cliTools:
     - tool: ["python3"]
       semver: ">=3.8"

package/skills/experience-lwc-accessibility-validate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-accessibility-validate
 description: "Use this skill to determine whether a Lightning Web Component (LWC) is accessible and meets WCAG accessibility guidelines. TRIGGER when the user asks \"is my component accessible?\", \"does my LWC meet accessibility guidelines?\", \"is this component WCAG compliant?\", \"find accessibility problems in this LWC\", \"is this LWC keyboard accessible?\", \"does this component work with a screen reader?\", \"does this component have sufficient color contrast?\", \"check ARIA usage in this LWC\", or \"WCAG 2.2 accessibility check\". Also TRIGGER when the user wants to fix or improve accessibility (a11y, WCAG, ARIA) in an LWC's HTML, JS, or CSS — semantic markup, focus, keyboard nav, contrast, screen-reader labels, WCAG 2.2 SC. Produces `a11y-review.md` with WCAG-cited findings. DO NOT TRIGGER for general LWC generation (use `experience-lwc-generate`) or SLDS visual/design review not focused on accessibility (use `design-systems-slds-validate`)."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   cliTools:
     - tool: ["python3"]
       semver: ">=3.8"

package/skills/experience-lwc-base-components-integrate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-base-components-integrate
 description: "Pick the right Lightning Base Component (`lightning-*`) for a given UI task, retrieve its full API (props, methods, events, slots) from the bundled per-component reference, and wire it into an LWC (LWC `.html`, `.js`, and `.css` files) without breaking SLDS. Use this skill when users say \"I need a Lightning modal / datatable / combobox / record form\", ask which `lightning-*` component fits a use case, want a shortlist of LBC candidates, are about to hand-roll a UI that a base component already provides, or are editing an LWC bundle's `.html` / `.js` / `.css` and need to select or wire a base component. Also triggers on \"Lightning base component\", \"LBC\", \"lightning-combobox\", \"lightning-datatable\", \"use `lightning-` tag\". DO NOT TRIGGER for applying SLDS design tokens, blueprints, or styling guidance in general — that is `design-systems-slds-apply`; this skill only selects and wires `lightning-*` base components."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - design-systems-slds-apply
 ---

package/skills/experience-lwc-design-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-design-generate
 description: "Use when you need to create a brand new Lightning Web Component from a Figma design, a Product Requirements Document, or another design artifact — orchestrating the five-phase workflow (gather requirements → generate code → optimize → lint/format/compile → test) and stitching together the specialized skills for SLDS, LDS, base components, optimization, and testing. Use this skill whenever the user mentions building a new LWC from Figma, building an LWC from a PRD, generating an LWC from a design or screenshot, or migrating an Aura component as a fresh LWC build. DO NOT TRIGGER when refactoring an existing LWC (use experience-lwc-generate), for Aura → LWC in-place migration (out of scope for this skill), for standalone SLDS token or styling work (use design-systems-slds-apply), or for standalone data-layer work (use experience-lds-best-practices-apply or experience-lds-data-requirements-generate)."
 metadata:
   version: "1.0"
+  domains: ["Experience", "Design Systems"]
   cliTools:
     - tool: ["eslint"]
       semver: ">=8.0"

package/skills/experience-lwc-generate/SKILL.md

@@ -21,6 +21,7 @@ metadata:
     - "platform-apex-test-run"
     - "platform-metadata-deploy"
   version: "1.1"
+  domains: ["Experience"]
 ---
 
 # experience-lwc-generate: Lightning Web Components Development

package/skills/experience-lwc-rtl-validate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-rtl-validate
 description: "Use this skill to review a Lightning Web Component (.html, .js, .css files) for right-to-left (RTL) internationalization correctness, producing a finding list with code-level fixes covering CSS logical properties, bidirectional text handling, keyboard semantics, and RTL-aware SLDS class usage. TRIGGER when the user says \"review this LWC for RTL\", \"audit i18n compliance\", \"fix bidirectional text rendering\", \"replace left/right CSS with logical properties\", \"check RTL layout issues\", \"verify SLDS RTL classes\", \"review my component for Arabic/Hebrew layout\", \"ensure this LWC works in RTL locales\", or \"check bidi text handling\". DO NOT TRIGGER when the user is building a new LWC (use experience-lwc-generate), refactoring SLDS classes themselves (use design-systems-slds-apply or design-systems-slds2-migrate), or performing accessibility/security review."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - design-systems-slds-apply
     - design-systems-slds2-migrate

package/skills/experience-lwc-runtime-observe/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-runtime-observe
 description: "Use when running Salesforce Lightning Preview for an app or a single LWC component to extract the runtime DOM for inspection. TRIGGER when the user says \"preview an LWC locally\", \"run sf lightning dev\", \"launch Local Dev\", \"inspect a component's shadow DOM at runtime\", \"grab rendered HTML from a live preview\", \"troubleshoot what actually renders versus the template\", \"set up Salesforce Live Preview plugin\", \"lightning preview\", \"local dev server\", or \"extract runtime DOM\". DO NOT TRIGGER when the user is authoring or editing LWC source code (use experience-lwc-generate) or reviewing component code statically without running it."
 metadata:
   version: "1.0"
+  domains: ["Experience", "Developer Experience"]
   cliTools:
     - tool: ["python3"]
       semver: ">=3.0.0"

package/skills/experience-lwc-security-validate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-security-validate
 description: "Use this skill as THE specialized Lightning Web Security (LWS) validator for a Lightning Web Component bundle (`.js`, `.ts`, `.html`, `.css`, `.js-meta.xml`) — the canonical LWS/Product-Security review for LWCs, NOT a generic code-security pass. It produces either a severity-ranked finding list with code-level remediations or a SARIF 2.1.0 JSON score report keyed by the `lws-001`…`lws-023b` rule catalog. TRIGGER when the user asks to review, audit, or check an LWC component for LWS compliance issues and recommend fixes, score a component's LWS/security compliance, find dangerous DOM APIs or blocked sinks (`eval`, `Function`, `document.write`, `innerHTML`, `document.createElement('script')`, global-scope assignment to `window`/`globalThis`, unsafe URL schemes), or emit a SARIF security report. DO NOT TRIGGER for generic non-LWC security review, for building a new LWC (use experience-lwc-generate), accessibility (WCAG 2.2), RTL/i18n, or Apex/Aura/server-side review."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - design-systems-slds-validate
     - dx-code-analyzer-run

package/skills/experience-lwc-typescript-migrate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwc-typescript-migrate
 description: "Use when converting an existing JavaScript Lightning Web Component (.js, .html, .css) to TypeScript with full type annotations and a matching `.d.ts` file that exposes only the component's `@api` surface. TRIGGER when the user says \"convert LWC to TypeScript\", \"migrate LWC to TS\", \"rename .js to .ts for this component\", \"add types to my LWC\", \"generate .d.ts for this LWC\", \"type-annotate @api properties\", or \"produce declare module 'c/componentName' definitions\". DO NOT TRIGGER when the user is authoring a brand-new LWC from scratch (use experience-lwc-generate), generating Jest tests for an existing LWC (use experience-lwc-generate), or migrating an Aura component to LWC."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-lwc-generate"
   cliTools:

package/skills/experience-lwr-site-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-lwr-site-generate
 description: "Creates, modifies, or manages Salesforce Experience Cloud LWR sites via DigitalExperience metadata. Always trigger when the tasks involve LWR sites configurations, e.g. creating/modifying pages/routes/views/theme layouts/branding sets, previewing sites, or creating/modifying guest sharing rule (metadata type sharingGuestRules)/guest user access/sharing records to guest users, or when user provides a guest user ID (15 or 18 characters starting with 005). NEVER trigger for React or any other ui bundle framework. LWR sites ONLY."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   minApiVersion: "56.0"
   cliTools:
     - tool: ["node"]

package/skills/experience-ui-bundle-2gp-deploy/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-2gp-deploy
 description: "MUST activate when the user wants to package, distribute, or install/upgrade/uninstall/promote a UI Bundle as a Salesforce second-generation (2GP) package (project may contain uiBundles/ or sfdx-project.json for packaging tasks; install/upgrade tasks may lack local bundle files). Handles making a bundle packageable, choosing managed/unlocked flavor, creating package/version with sf package, installing/upgrading in another org, and debugging failures. TRIGGER on packaging, 2GP, managed package, unlocked package, AppExchange, package version, sf package, sf package install, sf package upgrade, install a package, upgrade a package, cross-org distribution. DO NOT TRIGGER for plain source deploy to one org (use experience-ui-bundle-deploy) or scaffolding a new bundle (use experience-ui-bundle-project-generate). Apply piecemeal — do ONLY the part asked."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   minApiVersion: "58.0"
   relatedSkills:
     - "experience-ui-bundle-deploy"