@salesforce/afv-skills 1.38.0 → 1.40.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.38.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/README.md

@@ -50,7 +50,7 @@ See `SKILL.md` for the full TRIGGER conditions, flag table, and the "DC-only bli
 
 Three stages, each independently runnable:
 
-```
+```text
 fetch_dc.py     →  24 dc.<name>.json + dc._session_manifest.json   (DC Query REST waterfall)
 assemble_dc.py  →  dc._session_tree.json                           (in-memory hierarchical join)
 render_dc.py    →  dc._session_summary.md                          (markdown rendering)
@@ -87,7 +87,7 @@ For design-time architecture questions (topic/action tree, flow inventory, Apex
 
 ## Layout
 
-```
+```text
 agentforce-d360-analyze/
 ├── SKILL.md                               ← runtime-parsed entry point (TRIGGER / DO NOT TRIGGER, flags, prompts)
 ├── README.md                              ← this file

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

@@ -2,15 +2,16 @@
 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"
   cliTools:
     - tool: ["python3"]
       semver: ">=3.10.0"
     - tool: ["sf"]
       semver: ">=2.0.0"
-  relatedSkills:
-    - "agentforce-architecture-analyze"
-  version: "1.0"
-  minApiVersion: "66.0"
 ---
 
 # agentforce-d360-analyze — Data Cloud 360° session view
@@ -72,7 +73,7 @@ python3 "$prefix/discover_sessions.py" --org <alias> [filters...]
 
 ## Pipeline — three stages
 
-```
+```text
 fetch_dc.py     →  24 dc.<name>.json + dc._session_manifest.json     (DC Query REST waterfall, 5 waves)
 assemble_dc.py  →  dc._session_tree.json                             (pure in-memory hierarchical join)
 render_dc.py    →  dc._session_summary.md                            (human summary, multi-section)
@@ -92,7 +93,7 @@ Flags: `--verbose` for per-DMO row counts; `--no-assemble` / `--no-render` to st
 
 Everything lands under `~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<session_id>/` (default; override with `--data-dir <path>`):
 
-```
+```text
 dc.sessions.json              dc.steps.json                dc.gateway_requests.json
 dc.interactions.json          dc.messages.json             dc.gateway_responses.json
 dc.participants.json          dc.generations.json          dc.gateway_request_llm.json

package/skills/agentforce-d360-analyze/references/artifacts.md

@@ -5,7 +5,7 @@ Every successful trace lands artifacts under
 Re-running the same `(org, sid)` overwrites in place. Listed below in
 the order they're produced.
 
-```
+```text
 ~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<sid>/
 ├── dc._session_manifest.json ← per-query counts + session_shape + empties
 ├── dc._session_tree.json ← hierarchical join (primary artifact)

package/skills/agentforce-d360-analyze/references/dc_dmo_fields.md

@@ -59,7 +59,7 @@ Per-run row counts, empty reasons, and join paths are recorded in
 Legend: ★ = session-FK direct (one hop) ▸ = polymorphic `parent__c`
  ⚠ = requires feature provisioning
 
-```
+```text
 Session (ssot__AIAgentSession__dlm, PK ssot__Id__c)
  │
  ├── ★ Participant (ssot__AiAgentSessionId__c)
@@ -135,7 +135,7 @@ All 24 entries below are in the `scripts/fetch_dc.py` waterfall — the
 join expressions are exactly what the script runs, and each one has a
 `.sql` template under `assets/dc/`.
 
-```
+```text
  1. sessions WHERE ssot__Id__c = {sid}
  2. interactions WHERE ssot__AiAgentSessionId__c = {sid}
  3. messages WHERE ssot__AiAgentSessionId__c = {sid}
@@ -370,7 +370,7 @@ schemas are documented in the per-DMO sections below.
 `turnId__c` column (verified via live `describe`; 11 fields total,
 none reference session/trace/turn). The canonical join path is:
 
-```
+```text
 Session → Interaction → Step (.ssot__GenerationId__c) → Generation (.generationId__c)
 ```
 
@@ -432,7 +432,7 @@ Richer than `GenAIGeneration` — carries prompt text, tokens, model, and
 session/user/bot identifiers. **Forward entry point for the entire audit
 chain**, reached from Session via `sessionId__c`:
 
-```
+```text
 Session.ssot__Id__c → GatewayRequest.sessionId__c LIKE '%<sid>%'
 ```
 

package/skills/agentforce-d360-analyze/references/dc_pipeline_contract.md

@@ -3,7 +3,7 @@
 The DC pipeline for a single Agentforce session runs as three stages in
 sequence:
 
-```
+```text
 fetch_dc.py → 24 dc.<name>.json artifacts + dc._session_manifest.json
 assemble_dc.py → dc._session_tree.json (pure in-memory join)
 render_dc.py → dc._session_summary.md (pure tree reader)
@@ -71,7 +71,7 @@ Per-field schema for every DMO lives in
 The "normal" path that nests a `GatewayRequest` under its owning
 `LLM_STEP` in the tree. Every edge is a platform-sanctioned forward FK:
 
-```
+```text
 Step.ssot__GenerationId__c → Generation.generationId__c
 Generation.generationResponseId__c → GatewayResponse.generationResponseId__c
 GatewayResponse.generationRequestId__c → GatewayRequest.gatewayRequestId__c

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

@@ -3,15 +3,16 @@ name: commerce-b2b-open-code-components-integrate
 description: "Integrate Salesforce B2B Commerce open source components from GitHub into B2B Commerce stores. Use when users mention \"integrate open code components\", \"open source B2B commerce\", \"add open code components\", \"forcedotcom/b2b-commerce-open-source-components\", or want to add open source commerce components to their store. Copies all components and labels so they become available in Experience Builder."
 allowed-tools: Bash(git clone:*) Bash(cp:*) Read
 metadata:
+  version: "1.0"
+  domains: ["Commerce", "Experience"]
+  minApiVersion: "56.0"
+  relatedSkills:
+    - "commerce-b2b-store-create"
   cliTools:
     - tool: ["git"]
       semver: ">=2.0.0"
     - tool: ["sf"]
       semver: ">=2.0.0"
-  relatedSkills:
-    - "commerce-b2b-store-create"
-  version: "1.0"
-  minApiVersion: "56.0"
 ---
 
 ## When to Use This Skill
@@ -98,8 +99,8 @@ Copy all components and labels from cloned repo to site directory:
 5. Report: "Copied X components and Y label sets"
 
 **Output:**
-```
-✅ Integration Complete!
+```text
+Integration Complete!
 
 Copied: X components and Y label sets to <store-name>
 
@@ -125,7 +126,7 @@ Next Steps:
 **User:** "1"
 
 **Agent:** "I'm checking if your project already has B2B store metadata locally..."
-- ✓ Found store metadata for My_B2B_Store1
+- [done] Found store metadata for My_B2B_Store1
 
 **Agent:** "I'm checking if open code components already exist in your store's site metadata..."
 
@@ -138,10 +139,10 @@ Next Steps:
 
 **Agent:** "I'm now copying all open code LWC components from the cloned repository into your store's site metadata directory..."
 **Agent:** "I'm copying the associated label files that these components need..."
-- ✓ Copied 45 components and 38 label sets
+- [done] Copied 45 components and 38 label sets
 
-```
-✅ Integration Complete!
+```text
+Integration Complete!
 
 Copied: 45 components and 38 label sets to My_B2B_Store1
 

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

@@ -1,9 +1,9 @@
 ---
 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."
-compatibility: "Requires Commerce licenses, Experience Cloud, Salesforce CLI"
 metadata:
   version: "1.0"
+  domains: ["Commerce", "Experience"]
   minApiVersion: "56.0"
   cliTools:
     - tool: ["sf"]
@@ -101,7 +101,7 @@ sf org list metadata --metadata-type DigitalExperienceConfig --json
 - Explain naming (underscores, number suffixes)
 
 **Example output:**
-```
+```text
 Available Digital Experience sites:
 1. My_B2B_Store1
 2. Partner_Portal
@@ -134,7 +134,7 @@ sf project retrieve start -m DigitalExperienceBundle:site/<selected-store-name>
 - List retrieved directory structure
 
 **Expected output:**
-```
+```text
 Retrieved: force-app/main/default/digitalExperiences/site/My_B2B_Store1/
 ├── My_B2B_Store1.digitalExperience-meta.xml
 ├── sfdc_cms__view/ (home, current_cart, detail_*, list_*, etc.)
@@ -149,7 +149,7 @@ Retrieved: force-app/main/default/digitalExperiences/site/My_B2B_Store1/
 
 **Agent provides:**
 
-✅ **Metadata retrieved successfully!**
+**Metadata retrieved successfully!**
 
 **Next steps:**
 - Customize with custom LWCs or branding changes

package/skills/commerce-b2b-store-create/references/store-vs-storefront.md

@@ -121,7 +121,7 @@ Understanding the distinction between Commerce Store and Storefront is critical
 
 ### Step 1: Create Commerce Store (Must Be First)
 
-```
+```text
 User Interface (Commerce App)
      ↓
 WebStore Record Created
@@ -144,7 +144,7 @@ Commerce Components Configured
 
 ### Step 2: Retrieve Storefront Metadata
 
-```
+```sh
 sf org list metadata --metadata-type DigitalExperienceConfig
      ↓
 Select Store from List

package/skills/data360-activate/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: data360-activate
 description: "Salesforce Data Cloud Act phase. Use this skill when the user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. TRIGGER when: user manages activations, activation targets, data actions, or downstream delivery of Data Cloud audiences and data. DO NOT TRIGGER when: the task is segment creation (use data360-segment), data retrieval/search work (use data360-query), or STDM/session tracing (use agentforce-observe)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["node"]
@@ -16,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

@@ -1,7 +1,6 @@
 ---
 name: data360-connect
 description: "Salesforce Data Cloud Connect phase. Use this skill when the user manages Data Cloud connections, connectors, or sets up a new source system. TRIGGER when: user manages Data Cloud connections, connectors, connector metadata, tests a connection, browses source objects or databases, or sets up a new source system. DO NOT TRIGGER when: the task is about data streams or DLOs (use data360-prepare), DMOs or identity resolution (use data360-harmonize), retrieval/search (use data360-query), or STDM telemetry (use agentforce-observe)."
-compatibility: "Requires the sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["node"]
@@ -15,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

@@ -1,7 +1,6 @@
 ---
 name: data360-harmonize
 description: "Salesforce Data Cloud Harmonize phase. Use this skill when the user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. TRIGGER when: user works with DMOs, mappings, relationships, identity resolution, unified profiles, data graphs, or universal IDs. DO NOT TRIGGER when: the task is only about streams/DLOs (use data360-prepare), segments/insights (use data360-segment), retrieval/search (use data360-query), or STDM/session tracing (use agentforce-observe)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["node"]
@@ -15,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

@@ -1,7 +1,6 @@
 ---
 name: data360-orchestrate
 description: "Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use agentforce-observe), standard CRM SOQL (use platform-soql-query), or Apex implementation (use platform-apex-generate)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["curl"]
@@ -34,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

@@ -1,7 +1,6 @@
 ---
 name: data360-prepare
 description: "Salesforce Data Cloud Prepare phase. Use this skill when the user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations. TRIGGER when: user creates or manages Data Cloud data streams, DLOs, transforms, or Document AI configurations, or asks about ingestion into Data Cloud. DO NOT TRIGGER when: the task is connection setup only (use data360-connect), DMOs and identity resolution (use data360-harmonize), or query/search work (use data360-query)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["node"]
@@ -18,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

@@ -1,7 +1,6 @@
 ---
 name: data360-query
 description: "Salesforce Data Cloud Retrieve phase. Use this skill when the user runs Data Cloud SQL, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. TRIGGER when: user runs Data Cloud SQL, describe, async queries, vector search, search-index workflows, or metadata introspection for Data Cloud objects. DO NOT TRIGGER when: the task is standard CRM SOQL (use platform-soql-query), segment creation or calculated insight design (use data360-segment), or STDM/session tracing/parquet analysis (use agentforce-observe)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["node"]
@@ -14,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

@@ -1,7 +1,6 @@
 ---
 name: data360-segment
 description: "Salesforce Data Cloud Segment phase. Use this skill when the user creates or publishes segments, manages calculated insights, or troubleshoots audience SQL in Data Cloud. TRIGGER when: user creates or publishes segments, manages calculated insights, inspects segment counts or membership, or troubleshoots audience SQL in Data Cloud. DO NOT TRIGGER when: the task is DMO/mapping/identity-resolution work (use data360-harmonize), activation work (use data360-activate), query/search-index work (use data360-query), or Standard Data Model (STDM)/session tracing (use agentforce-observe)."
-compatibility: "Requires an external community sf data360 CLI plugin and a Data Cloud-enabled org"
 metadata:
   cliTools:
     - tool: ["node"]
@@ -15,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-slds-validate/references/quality-checks.md

@@ -260,7 +260,7 @@ const NATIVE_SELECT = /<select\s/gi;
 
 The script outputs individual category scores. It does **not** produce a combined overall grade — the agent computes that using the formula in SKILL.md Step 4:
 
-```
+```text
 Overall = (Linter × 0.30) + (Theming × 0.20) + (Accessibility × 0.20)
         + (CodeQuality × 0.15) + (ComponentUsage × 0.15)
 ```
@@ -273,7 +273,7 @@ The script automates **17 of 53** checks listed above (marked **Script** in the
 
 ### Theming
 
-```
+```text
 Score = 100 - (critical issues in category × 10)
               - (warnings in category × 3)
               - (info in category × 1)
@@ -282,7 +282,7 @@ Min: 0
 
 ### Accessibility
 
-```
+```text
 Score = 100 - (critical issues in category × 10)
               - (warnings in category × 3)
               - (info in category × 1)
@@ -291,7 +291,7 @@ Min: 0
 
 ### Code Quality
 
-```
+```text
 Score = 100 - (critical issues in category × 10)
               - (warnings in category × 3)
               - (info in category × 1)
@@ -300,7 +300,7 @@ Min: 0
 
 ### Component Usage
 
-```
+```text
 Score = 100 - (critical issues in category × 10)
               - (warnings in category × 3)
               - (info in category × 1)

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

@@ -2,10 +2,11 @@
 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"
-  version: "1.0"
 ---
 
 # Goal
@@ -36,7 +37,7 @@ Color hooks require the most judgment (context-dependent selection). Non-color h
 
 # Workflow
 
-```
+```text
 1. **REQUIRED — ALWAYS run first:** npx @salesforce-ux/slds-linter@latest lint --fix . — NEVER skip this step. This handles simple violations automatically.
 2. Review linter output -> Identify remaining manual fixes needed
 3. Fix by violation type -> Use per-rule reference guides
@@ -57,7 +58,7 @@ The linter analyzes all CSS and markup files (`.html` for LWC, `.cmp` for Aura),
 
 The linter reports violations in this format:
 
-```
+```text
 componentName.css
   15:3  warning  Overriding slds-button isn't supported. To differentiate SLDS and
                  custom classes, create a CSS class in your namespace.
@@ -126,7 +127,7 @@ See [rule-no-slds-class-overrides.md](references/rule-no-slds-class-overrides.md
 
 **Linter feedback loop — repeat until zero errors:**
 
-```
+```text
 1. npx @salesforce-ux/slds-linter@latest lint .
 2. Review errors -> fix by type (Step 3)
 3. Re-run linter

package/skills/design-systems-slds2-migrate/references/color-hooks-decision-guide.md

@@ -24,7 +24,7 @@ This guide helps you choose the correct SLDS 2 color hook. Use it when replacing
 
 **Always try semantic hooks first.** ~85-90% of color decisions should use semantic hooks. System and palette hooks are last resorts, not alternatives.
 
-```
+```text
 1. SEMANTIC HOOKS (try first, ~85-90% of decisions)
    surface-*, accent-*, error/warning/success/info/disabled-*
    • Accessibility built-in  • Theme-aware  • Dark mode ready

package/skills/design-systems-slds2-migrate/references/examples.md

@@ -19,7 +19,7 @@ Before/after examples organized by violation type.
 ## Class Override Example
 
 **Violation:**
-```
+```text
 dataTable.css
   5:1   warning  Overriding slds-table isn't supported. To differentiate SLDS and
                  custom classes, create a CSS class in your namespace.
@@ -68,7 +68,7 @@ dataTable.css
 ## LWC Token Example
 
 **Violation:**
-```
+```text
 panelHeader.css
   3:3  error  The '--lwc-colorBackgroundAlt' design token is deprecated. Replace it with
               the SLDS 2 styling hook and set the fallback to '--lwc-colorBackgroundAlt'.
@@ -106,7 +106,7 @@ panelHeader.css
 ### Tile with Border and Spacing
 
 **Violation:**
-```
+```text
 tile.css
   2:20  warning  Consider replacing the #ffffff static value with an SLDS 2 styling hook
                  that has a similar value:

package/skills/design-systems-slds2-migrate/references/rule-lwc-token-to-slds-hook.md

@@ -10,7 +10,7 @@
 
 The linter detects deprecated `--lwc-*` tokens and reports them as **errors**. When there is only one suggestion, `--fix` auto-applies it. When there are multiple suggestions, manual selection is required. Here's real linter output for a multiple-suggestion case:
 
-```
+```text
   2:14  error  The '--lwc-colorBackground' design token is deprecated. Replace it with
                the SLDS 2 styling hook and set the fallback to '--lwc-colorBackground'.
                1. --slds-g-color-surface-2

package/skills/design-systems-slds2-migrate/references/rule-no-deprecated-tokens-slds1.md

@@ -13,13 +13,13 @@ The linter detects `t()` and `token()` function calls in CSS, `.cmp`, and `.html
 Two message types:
 
 **When a replacement exists:**
-```
+```text
 Consider removing t(colorTextDefault) or replacing it with --slds-g-color-on-surface-3.
 Set the fallback to t(colorTextDefault).
 ```
 
 **When no replacement exists:**
-```
+```text
 Update outdated design tokens to SLDS 2 styling hooks with similar values.
 ```