@salesforce/afv-skills 1.38.0 → 1.40.0

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

@@ -1,9 +1,9 @@
 ---
 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."
-compatibility: "Requires search_media_cms_channels and/or search_electronic_media MCP tools"
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-content-media-stock-image-search"
   mcpTools:
@@ -51,17 +51,17 @@ When a user requests to find an image:
 
 
 **Example of what NOT to do:**
-- ❌ Calling ANY tool before the user picks a source (MCP tools, file reads, descriptor checks, etc.)
-- ❌ "Checking which MCP tools are available" — do not probe or discover tools via tool calls
-- ❌ Immediately calling `search_electronic_media` or `search_media_cms_channels`
-- ❌ Reading MCP tool descriptors or schemas to see what's available
-- ❌ Deciding which search source to use without asking
+- Calling ANY tool before the user picks a source (MCP tools, file reads, descriptor checks, etc.)
+- "Checking which MCP tools are available" — do not probe or discover tools via tool calls
+- Immediately calling `search_electronic_media` or `search_media_cms_channels`
+- Reading MCP tool descriptors or schemas to see what's available
+- Deciding which search source to use without asking
 
 **Example of what TO do:**
-- ✅ Respond with ONLY text — a numbered list of search sources
-- ✅ Ask: "Which option would you like to use?"
-- ✅ Wait for user to reply with their choice
-- ✅ Then (and only then) call the tool they selected
+- Respond with ONLY text — a numbered list of search sources
+- Ask: "Which option would you like to use?"
+- Wait for user to reply with their choice
+- Then (and only then) call the tool they selected
 
 **Your first response when this skill triggers MUST be a text-only message presenting search sources. No tool calls. No exceptions.**
 
@@ -72,7 +72,7 @@ When a user requests to find an image:
 
 Copy this checklist and track your progress:
 
-```
+```text
 Media Search Progress:
 - [ ] Step 1: Check your own tool list for available search tools (no tool calls — just inspect what's in your context)
 - [ ] Step 2: Present only the available options to the user as a numbered list (plain text, no tool calls)
@@ -101,7 +101,7 @@ Look at the tools already in your context and check for these names:
 
 Include ONLY the sources whose tools you actually have. Number them sequentially.
 
-```
+```text
 I can help you find that image. Where would you like to search?
 
 [NUMBER]. [SEARCH SOURCE NAME] — [Brief description]
@@ -118,7 +118,7 @@ After presenting the list, STOP. Do not call any tool. Do not proceed. Wait for
 ### Examples
 
 **Both tools available:**
-```
+```text
 I can help you find that image. Where would you like to search?
 
 1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs
@@ -129,7 +129,7 @@ Which option would you like to use?
 ```
 
 **Only `search_media_cms_channels` available:**
-```
+```text
 I can help you find that image. Where would you like to search?
 
 1. Search using keywords — Search Salesforce CMS by keywords and taxonomies
@@ -139,7 +139,7 @@ Which option would you like to use?
 ```
 
 **Only `search_electronic_media` available:**
-```
+```text
 I can help you find that image. Where would you like to search?
 
 1. Search using Data 360 hybrid search — Semantic search across Salesforce CMS and connected DAMs
@@ -149,7 +149,7 @@ Which option would you like to use?
 ```
 
 **Neither tool available:**
-```
+```text
 No automated media search sources are currently configured. Please provide a direct URL or asset library path.
 ```
 
@@ -157,7 +157,7 @@ No automated media search sources are currently configured. Please provide a dir
 
 ## Executing the Selected Search Method
 
-**⚠️ ONLY reach this step if the user has explicitly selected an option from your numbered list.**
+**ONLY reach this step if the user has explicitly selected an option from your numbered list.**
 
 If you haven't shown options yet, go back to the "Presenting Search Sources" section first.
 
@@ -291,7 +291,7 @@ Ask the user to provide:
 3. **Receive the user's selection** from the tool response
 4. **Then** apply the selected image
 
-```
+```text
 I found 4 images. Which one would you like to use?
 
 1. Luxury Apartment Exterior

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"

package/skills/experience-ui-bundle-agentforce-client-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-agentforce-client-generate
 description: "Use this skill when the user asks to add, embed, integrate, configure, style, or remove an agent, chatbot, chat widget, conversation client, or AI assistant in a UI Bundle project (React or Angular). TRIGGER when: project contains a uiBundles/*/src/ directory and the task involves adding or modifying a chat widget, chatbot, or conversational AI; files under uiBundles/*/src/ import AgentforceConversationClient in React `.tsx`/`.jsx` files, or use the app-agentforce-conversation-client element in Angular `.html` templates and AgentforceConversationClientComponent in `.component.ts` files; user asks to add any chat or agent functionality to a page. DO NOT TRIGGER when: user wants to create a custom agent, chatbot, or chat widget component from scratch; the project has no uiBundles directory."
 metadata:
   version: "1.2"
+  domains: ["Experience", "Agentforce"]
   cliTools:
     - tool: ["npm"]
       semver: ">=9.0.0"

package/skills/experience-ui-bundle-app-coordinate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-app-coordinate
 description: "MUST activate when the user wants to build, create, or generate a React application, React app, web application, single-page application (SPA), or frontend application — even if no project files exist yet. MUST also activate when the project contains a uiBundles/*/src/ directory or sfdx-project.json and the prompt says create, build, construct, or generate a new app, site, or page from scratch — even if the prompt also describes visual styling. MUST also activate when the task spans more than one ui-bundle skill. Use this skill when building a complete app end-to-end. Do NOT use for Lightning Experience apps with custom objects (use platform-lightning-app-coordinate). Do NOT use for single-concern edits to an existing page (use experience-ui-bundle-frontend-generate)."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-ui-bundle-agentforce-client-generate"
     - "experience-ui-bundle-custom-app-generate"

package/skills/experience-ui-bundle-custom-app-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-custom-app-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring a Custom Application for hosting a UI bundle in Lightning Experience. Use this skill when creating a CustomApplication metadata record to surface the UI bundle in the App Launcher. Activate when files matching applications/*.app-meta.xml exist and need modification, or when the user wants to expose their app via the Lightning App Launcher without a Digital Experience Site. Do NOT use platform-custom-application-generate for this — UI bundle apps do not use tabs, action overrides, or flexipages."
 metadata:
   version: "1.0"
+  domains: ["Experience", "Platform"]
   minApiVersion: "65.0"
   relatedSkills:
     - "platform-custom-application-generate"

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

@@ -3,6 +3,7 @@ name: experience-ui-bundle-deploy
 description: "MUST activate when the project has a uiBundles/*/src/ directory and the task involves deploying to an org or post-deploy org setup. Deploys a UI bundle app and runs ordered setup: org auth, build, metadata deploy, permission-set and role assignment, Experience Cloud self-registration, social login / SSO / IDP linking (Auth Providers + SAML SSO configs on a React site), seed-data import, and GraphQL schema fetch + codegen. Trigger signals: *.network-meta.xml, org-setup.config.json (with a socialLogin block), data-plan.json, sfdx-project.json, or mentions of deploy, org setup, or social login / SSO / IDP linking on an Experience site. DO NOT TRIGGER when: creating a new UI bundle project (use experience-ui-bundle-project-generate); styling pages without deploying (use experience-ui-bundle-frontend-generate); adding a feature such as auth, search, or file upload without deploying (use the matching experience-ui-bundle-*-generate skill); configuring MFA permission sets (use experience-ui-bundle-mfa-configure)."
 metadata:
   version: "1.2"
+  domains: ["Experience", "Developer Experience"]
   relatedSkills:
     - "experience-ui-bundle-frontend-generate"
     - "experience-ui-bundle-mfa-configure"

package/skills/experience-ui-bundle-features-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-features-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the user wants to add a pre-built feature — such as authentication (login, logout, protected routes, session management) or search (global search across pages and content) — instead of building it from scratch. Always run list first to see the current feature catalog, since it can include more than authentication and search. Always use this skill for installing pre-built features rather than hand-building them. DO NOT TRIGGER for Agentforce conversational client or file-upload features — use experience-ui-bundle-agentforce-client-generate and experience-ui-bundle-file-upload-generate respectively."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   relatedSkills: ["experience-ui-bundle-agentforce-client-generate", "experience-ui-bundle-file-upload-generate"]
   cliTools:
     - tool: ["npx"]

package/skills/experience-ui-bundle-file-upload-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-file-upload-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves uploading, attaching, or dropping files. Use this skill when adding file upload functionality to a UI bundle app. Provides progress tracking and Salesforce ContentVersion integration. This feature provides programmatic APIs ONLY — build custom UI using the upload() API. ALWAYS use this instead of building file upload from scratch with FormData or XHR."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-ui-bundle-salesforce-data-access"
   cliTools:

package/skills/experience-ui-bundle-frontend-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-frontend-generate
 description: "MUST activate before editing ANY file under uiBundles/*/src/ (or the bundle's index.html) for visual or UI changes to an EXISTING app — pages, components, sections, layout, styling, colors, fonts, navigation, animations, branding, or any look-and-feel change. Use this skill when modifying pages, components, layout, styling, navigation, or branding in an existing UI bundle app. Activate when the project contains appLayout.tsx, routes.tsx, src/pages/, src/components/, src/styles/global.css, or the bundle's index.html. This skill contains critical project-specific conventions (appLayout.tsx shell, shadcn/ui components, Tailwind CSS, Salesforce base-path routing, module restrictions) that override general knowledge. Without this skill, generated code will use wrong imports, break routing, or ignore project structure. Do NOT use when creating a new app from scratch or the bundle has not been scaffolded yet (use experience-ui-bundle-app-coordinate instead)."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-ui-bundle-app-coordinate"
     - "experience-ui-bundle-features-generate"

package/skills/experience-ui-bundle-localize/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-localize
 description: "MUST activate to localize / internationalize a uiBundles/*/src/ React project: extract hardcoded user-facing strings into Custom Labels, wire i18next over the Platform SDK GraphQL backend, add a language to a localized bundle, or troubleshoot label rendering across locales. Triggers: user-facing string literals in .tsx/.jsx, a CustomLabels.labels-meta.xml, a src/i18n/ directory or label-manifest.ts, t(…) calls, or requests to 'translate / localize / internationalize / support another language.' Scope: authenticated UI Bundles only (B2E CustomApplication-bound, or in-core accessCheck-bound apps). DO NOT TRIGGER when: the bundle is a site (B2C/B2B) app bound to a DigitalExperienceConfig (site localization not yet supported), building app shell/UI or styling, reading/writing/refreshing records (use experience-ui-bundle-salesforce-data-access), generating a new bundle (use experience-ui-bundle-frontend-generate), deploying (use experience-ui-bundle-deploy), or authoring translations in Translation Workbench."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   minApiVersion: "68.0"
   relatedSkills:
     - "experience-ui-bundle-deploy"

package/skills/experience-ui-bundle-metadata-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-metadata-generate
 description: "Use this skill when adding a front-end React UI bundle to an existing project or configuring UI bundle metadata and config files. TRIGGER when: adding or scaffolding a new UI bundle inside a project that already exists; running sf template generate ui-bundle; editing ui-bundle.json routing, headers, or output directory; working with *.uibundle-meta.xml files; or registering CSP Trusted Sites, resolving blocked images or fonts or external API calls, or editing cspTrustedSites/*.cspTrustedSite-meta.xml files. DO NOT TRIGGER when: creating a brand-new Salesforce project from scratch, where the whole SFDX starter project (UI bundle plus Experience Site metadata and toolchain) is generated together (use experience-ui-bundle-project-generate)."
 metadata:
   version: "1.2"
+  domains: ["Experience"]
   minApiVersion: "67.0"
   relatedSkills:
     - "experience-ui-bundle-custom-app-generate"

package/skills/experience-ui-bundle-mfa-configure/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-mfa-configure
 description: "Configure Multi-Factor Authentication (MFA) for Salesforce Experience Site users. TRIGGER when: user wants to enable MFA on a community, enforce two-factor authentication for portal users, add MFA to a React Experience Site / Web App, configure ForceTwoFactor permission, create MFA permission sets for external users, or troubleshoot MFA not appearing on login. Also triggers on: MFA community, two-factor portal, ForceTwoFactor permission set, MFA Experience Cloud, MFA React site, identity verification community, MFA experience site, ForceTwoFactor permissionset-meta.xml, MFA permissionset-meta.xml. DO NOT TRIGGER when: configuring org-wide MFA for internal users (that's Setup > Identity Verification), building custom login UI components (use experience-ui-bundle-frontend-generate), or generating generic permission sets without MFA context (use platform-permission-set-generate)."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   minApiVersion: "47.0"
   cliTools:
     - tool: ["jq"]

package/skills/experience-ui-bundle-project-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-project-generate
 description: "Generates a minimal, ready-to-develop SFDX starter project from template instead of hand-scaffolding files. Use this skill when starting a brand-new Salesforce React UI bundle app and the initial project must be scaffolded — trigger phrases include create, start, or scaffold a new React UI bundle app, generate a starter project, or use a prebuilt/starter template. DO NOT TRIGGER when: editing, styling, or adding pages or components to an EXISTING app (use experience-ui-bundle-frontend-generate); configuring ui-bundle.json or metadata files (use experience-ui-bundle-metadata-generate); deploying to an org (use experience-ui-bundle-deploy); or when the user explicitly says they want to hand-scaffold from scratch."
 metadata:
   version: "1.1"
+  domains: ["Experience"]
   relatedSkills:
     - "experience-ui-bundle-app-coordinate"
     - "experience-ui-bundle-metadata-generate"

package/skills/experience-ui-bundle-salesforce-data-access/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-salesforce-data-access
 description: "MUST activate whenever a uiBundles/*/src/ project reads, writes, or displays Salesforce data — INCLUDING building a page, list, table, card grid, dashboard, or form that shows, filters, counts, or edits records of any object (e.g. Property__c, Account, Case), even when the prompt names only the UI or the object and never says query, GraphQL, or SDK. Records behind such a component come from Salesforce, so use this ALONGSIDE experience-ui-bundle-frontend-generate: that skill styles the component, this one wires its data. Also triggers on @salesforce/platform-sdk imports, sdk.graphql.query / mutate / sdk.fetch calls, *.graphql files, or stale data needing force-refresh. New read/write work uses the current @salesforce/platform-sdk API; migrate only EXISTING old @salesforce/sdk-data callable code. Not for pure styling/layout with no records, app shell, file upload, or auth/search scaffolding. DO NOT TRIGGER for OAuth, object/field schema changes, Bulk/Tooling/Metadata API, or declarative automation."
 metadata:
   version: "2.2"
+  domains: ["Experience", "Platform"]
   minApiVersion: "66.0"
   relatedSkills:
     - "experience-ui-bundle-frontend-generate"

package/skills/experience-ui-bundle-site-generate/SKILL.md

@@ -3,6 +3,7 @@ name: experience-ui-bundle-site-generate
 description: "MUST activate when the project contains a uiBundles/*/src/ directory and the task involves creating or configuring site infrastructure. Use this skill when creating or configuring a Salesforce Digital Experience Site for hosting a UI bundle. Activate when files matching digitalExperiences/, networks/, customSite/, or DigitalExperienceBundle exist and need modification, or when the user wants to publish, host, or configure guest access for their app."
 metadata:
   version: "1.0"
+  domains: ["Experience"]
   cliTools:
     - tool: ["sf"]
       semver: ">=2.0.0"

package/skills/experience-ui-bundle-site-generate/references/configure-metadata-custom-site.md

@@ -4,7 +4,7 @@
 This configuration file creates a **net-new, default** CustomSite metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing CustomSite record. Use this template only when provisioning a brand-new React site.
 
 ## File Location
-```
+```text
 sites/{siteName}.site-meta.xml
 ```
 

package/skills/experience-ui-bundle-site-generate/references/configure-metadata-digital-experience-bundle.md

@@ -4,7 +4,7 @@
 This configuration file creates a **net-new, default** DigitalExperienceBundle metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing DigitalExperienceBundle record. Use this template only when provisioning a brand-new React site.
 
 ## File Location
-```
+```text
 digitalExperiences/site/{siteName}1/{siteName}1.digitalExperience-meta.xml
 ```
 

package/skills/experience-ui-bundle-site-generate/references/configure-metadata-digital-experience-config.md

@@ -4,7 +4,7 @@
 This configuration file creates a **net-new, default** DigitalExperienceConfig metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing DigitalExperienceConfig record. Use this template only when provisioning a brand-new React site.
 
 ## File Location
-```
+```text
 digitalExperienceConfigs/{siteName}1.digitalExperienceConfig-meta.xml
 ```
 

package/skills/experience-ui-bundle-site-generate/references/configure-metadata-digital-experience.md

@@ -8,7 +8,7 @@ The `appContainer: true` field in `content.json` is what makes this a React site
 ## File Location
 The DigitalExperience directory contains only `_meta.json` and `content.json`. Do not create any directories other than `sfdc_cms__site` inside the bundle.
 
-```
+```text
 digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/_meta.json
 digitalExperiences/site/{siteName}1/sfdc_cms__site/{siteName}1/content.json
 ```

package/skills/experience-ui-bundle-site-generate/references/configure-metadata-network.md

@@ -4,7 +4,7 @@
 This configuration file creates a **net-new, default** Network metadata record for a Digital Experience React Site. It is not intended to edit or modify an existing Network record. Use this template only when provisioning a brand-new React site.
 
 ## File Location
-```
+```text
 networks/{siteName}.network-meta.xml
 ```
 

package/skills/experience-ui-bundle-site-generate/references/update-site-urls.md

@@ -80,7 +80,7 @@ Before deploying, confirm:
 
 ## Example URL Configuration
 
-```
+```text
 ChatterNetworkPicasso Site (Primary):
   DigitalExperienceConfig: <urlPathPrefix>bestsupport</urlPathPrefix>
 

package/skills/external-diagram-mermaid-generate/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: external-diagram-mermaid-generate
 description: "Salesforce architecture diagrams using Mermaid with ASCII fallback. Use this skill when generating text-based diagrams for Salesforce architecture, OAuth flows, ERDs, integration sequences, or Agentforce structure. TRIGGER when: user says \"diagram\", \"visualize\", \"ERD\", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user asks about non-Salesforce systems."
-compatibility: "Requires Mermaid-capable renderer for diagram previews"
 metadata:
   cliTools:
     - tool: ["curl"]
@@ -25,6 +24,7 @@ metadata:
     - "platform-data-manage"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["External"]
 ---
 
 # external-diagram-mermaid-generate: Salesforce Diagram Generation

package/skills/integration-connectivity-connected-app-configure/SKILL.md

@@ -4,6 +4,7 @@ description: "Salesforce Connected Apps and External Client Apps OAuth configura
 allowed-tools: Bash Read Write Edit Glob Grep WebFetch AskUserQuestion TodoWrite
 metadata:
   version: "1.1"
+  domains: ["Integration"]
   minApiVersion: "57.0"
   relatedSkills:
     - "integration-connectivity-generate"

package/skills/integration-connectivity-generate/SKILL.md

@@ -20,6 +20,7 @@ metadata:
     - "platform-data-manage"
     - "platform-metadata-deploy"
   version: "1.1"
+  domains: ["Integration"]
 ---
 
 # integration-connectivity-generate: Salesforce Integration Patterns Expert

package/skills/integration-eventing-cdc-configure/SKILL.md

@@ -11,6 +11,7 @@ metadata:
     - "platform-custom-object-generate"
     - "platform-permission-set-generate"
   version: "1.0"
+  domains: ["Integration"]
   minApiVersion: "60.0"
 ---
 

package/skills/integration-eventing-subscription-configure/SKILL.md

@@ -10,6 +10,7 @@ metadata:
     - "platform-custom-object-generate"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["Integration"]
 ---
 
 # Managing ManagedEventSubscription

package/skills/integration-eventing-subscription-configure/references/delete-guide.md

@@ -13,7 +13,7 @@ After deletion, avoid reusing the same DeveloperName immediately — the Pub/Sub
 ### Step 1 — Remove the metadata file
 
 Delete the file from your project:
-```
+```text
 managedEventSubscriptions/<DeveloperName>.managedEventSubscription-meta.xml
 ```
 

package/skills/mobile-apps-create/SKILL.md

@@ -3,6 +3,7 @@ name: mobile-apps-create
 description: "The entry point for building any Salesforce native mobile app on iOS or Android. TRIGGER when the user says: \"build a Salesforce iOS app\", \"add Salesforce login to my Android app\", \"set up Mobile SDK\", \"add MobileSync / SmartStore offline storage\", \"embed an Agentforce agent in my mobile app\", \"add Agentforce chat to iOS/Android\", or otherwise asks to create, extend, or integrate a Salesforce mobile experience in Swift or Kotlin (MSDK, Agentforce SDK, or both). SKIP when the user is building a non-Salesforce mobile app, using React Native / Flutter / Ionic without Salesforce integration, asking about generic mobile UI design, or working on a Salesforce-adjacent web/desktop surface (LWC, Experience Cloud, Mobile Publisher branding-only)."
 metadata:
   version: "1.0"
+  domains: ["Mobile"]
   cliTools:
     - tool: ["npx"]
       semver: ">=9.0.0"

package/skills/mobile-platform-native-capabilities-integrate/SKILL.md

@@ -6,6 +6,7 @@ metadata:
     - "design-systems-slds-apply"
     - "mobile-platform-offline-validate"
   version: "1.0"
+  domains: ["Mobile"]
 ---
 
 # Using Mobile Native Capabilities

package/skills/mobile-platform-offline-validate/SKILL.md

@@ -2,6 +2,10 @@
 name: mobile-platform-offline-validate
 description: "Review a Lightning Web Component for **mobile offline** compatibility — the Komaci offline static analyzer that pre-primes the data graph for Salesforce Mobile App Plus and Field Service Mobile App. Produces a finding list with code-level fixes covering inline GraphQL queries in `@wire` configurations, modern `lwc:if` / `lwc:elseif` / `lwc:else` directives, and Komaci ESLint rule violations (private wire properties, non-local reactive references, getter side-effects). Use when the user asks for a \"mobile offline review\", \"Komaci check\", \"offline priming audit\", \"offline priming failure\", or \"offline data graph error\", or to validate an LWC against the `@salesforce/eslint-plugin-lwc-graph-analyzer` recommended ruleset. Do not use for generic LWC code review (use an appropriate domain review skill) or for building LWCs with native mobile capabilities (use `mobile-platform-native-capabilities-integrate`)."
 metadata:
+  version: "1.0"
+  domains: ["Mobile"]
+  relatedSkills:
+    - "mobile-platform-native-capabilities-integrate"
   cliTools:
     - tool: ["eslint"]
       semver: ">=8.0.0"
@@ -9,9 +13,6 @@ metadata:
       semver: ">=9.0.0"
     - tool: ["npx"]
       semver: ">=9.0.0"
-  relatedSkills:
-    - "mobile-platform-native-capabilities-integrate"
-  version: "1.0"
 ---
 
 # Reviewing LWC Mobile Offline
@@ -113,7 +114,7 @@ environment.
 
 Emit a report in this shape:
 
-```
+```text
 ## Mobile Offline (Komaci priming)
 - <reviewer> — <file>:<startLine>:<startColumn>-<endLine>:<endColumn> — <type>
   Description: <verbatim from the reviewer reference>

package/skills/omnistudio-callable-apex-generate/SKILL.md

@@ -16,6 +16,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
+  domains: ["OmniStudio"]
   minApiVersion: "60.0"
 ---
 

package/skills/omnistudio-datamapper-generate/SKILL.md

@@ -15,6 +15,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
+  domains: ["OmniStudio"]
   minApiVersion: "60.0"
 ---
 

package/skills/omnistudio-datapacks-deploy/SKILL.md

@@ -21,6 +21,7 @@ metadata:
     - "platform-apex-logs-debug"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["OmniStudio"]
 ---
 
 # omnistudio-datapacks-deploy: Vlocity Build DataPack Deployment

package/skills/omnistudio-dependencies-analyze/SKILL.md

@@ -15,6 +15,7 @@ metadata:
     - "platform-custom-object-generate"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["OmniStudio"]
 ---
 
 # omnistudio-dependencies-analyze: OmniStudio Cross-Component Analysis

package/skills/omnistudio-epc-catalog-generate/SKILL.md

@@ -17,6 +17,7 @@ metadata:
     - "platform-metadata-deploy"
     - "platform-soql-query"
   version: "1.0"
+  domains: ["OmniStudio"]
   minApiVersion: "60.0"
 ---
 

package/skills/omnistudio-flexcard-generate/SKILL.md

@@ -13,6 +13,7 @@ metadata:
     - "omnistudio-omniscript-generate"
     - "platform-metadata-deploy"
   version: "1.0"
+  domains: ["OmniStudio"]
   minApiVersion: "60.0"
 ---