@salesforce/afv-skills 1.38.0 → 1.39.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@salesforce/afv-skills",
-  "version": "1.38.0",
+  "version": "1.39.0",
   "description": "Salesforce skills for Agentforce Vibes",
   "license": "CC-BY-NC-4.0",
   "files": [

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,15 @@
 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"
+  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 +72,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 +92,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/commerce-b2b-open-code-components-integrate/SKILL.md

@@ -3,15 +3,15 @@ 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"
+  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 +98,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 +125,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 +138,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-store-create/SKILL.md

@@ -1,7 +1,6 @@
 ---
 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"
   minApiVersion: "56.0"
@@ -101,7 +100,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 +133,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 +148,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"]

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"]

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"]

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"]

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"]

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"]

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"]

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,10 @@
 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"
   cliTools:
     - tool: ["npx"]
       semver: ">=7.0.0"
-  version: "1.0"
 ---
 
 # Goal
@@ -36,7 +36,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 +57,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 +126,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.
 ```
 

package/skills/design-systems-slds2-migrate/references/rule-no-hardcoded-values.md

@@ -10,7 +10,7 @@
 
 The linter detects hardcoded values and reports them as warnings. Here's real output for an icon component:
 
-```
+```text
   3:10  warning  Consider replacing the 32px static value with an SLDS 2 styling hook
                  that has a similar value: --slds-g-sizing-9.                              slds/no-hardcoded-values-slds2
 
@@ -72,7 +72,7 @@ The fallback must be the **exact original value** from the source CSS (e.g., `#0
 
 When examining a hardcoded value or deprecated token, follow this decision tree:
 
-```
+```text
 1. SLDS utility class available?
    └─ Yes → Remove CSS, add utility class to HTML
    └─ No  ↓

package/skills/design-systems-slds2-migrate/references/rule-no-slds-class-overrides.md

@@ -10,7 +10,7 @@
 
 The linter detects CSS classes that directly override SLDS classes and reports them as **warnings**. It does **not** auto-fix — all changes require manual work in both CSS and HTML.
 
-```
+```text
   1:1  warning  Overriding slds-button isn't supported. To differentiate SLDS and
                custom classes, create a CSS class in your namespace.
                Examples: myapp-input, myapp-button.                  slds/no-slds-class-overrides

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

@@ -4,9 +4,11 @@ description: "Set up, configure, and troubleshoot Salesforce Code Analyzer for a
 metadata:
   version: "1.0"
   relatedSkills:
-    - "dx-code-analyzer-run"
     - "dx-code-analyzer-custom-rule-create"
+    - "dx-code-analyzer-run"
   cliTools:
+    - tool: ["sf"]
+      semver: ">=2.0.0"
     - tool: ["curl"]
       semver: ">=7.0.0"
     - tool: ["java"]
@@ -17,8 +19,6 @@ metadata:
       semver: ">=9.0.0"
     - tool: ["python3"]
       semver: ">=3.10.0"
-    - tool: ["sf"]
-      semver: ">=2.0.0"
 ---
 
 # Configuring Code Analyzer Skill
@@ -51,7 +51,7 @@ This skill manages the `code-analyzer.yml` configuration file — the single sou
 
 ## Tool Usage Rules
 
-**Allowed:** Bash (sf, java, node, python3, git, npm), Read, Write, Edit
+**Allowed:** Bash (sf, java, node, python3, npm), Read, Write, Edit
 **Forbidden:** MCP tools, Agent tool, Web tools, other skills, `which`, `find`, `locate`, searching for binaries
 
 ---
@@ -359,7 +359,7 @@ rules:
 
 ### 6.1 Rule Name Resolution (Fuzzy Matching)
 
-**⚠️ CRITICAL:** A misspelled or partial rule name in `code-analyzer.yml` is SILENTLY IGNORED — no error, the override just won't apply.
+**CRITICAL:** A misspelled or partial rule name in `code-analyzer.yml` is SILENTLY IGNORED — no error, the override just won't apply.
 
 **When users reference rules by approximate names** (e.g., "the doc rule", "CRUD violation", "hardcoded values"), resolve to exact names BEFORE writing YAML:
 

package/skills/dx-code-analyzer-configure/references/ci-cd-templates.md

@@ -316,7 +316,7 @@ For monorepos where Salesforce code lives in a subdirectory, use `--target` to s
 ```
 
 For multiple packages:
-```
+```text
 --target packages/app-a/force-app --target packages/app-b/force-app
 ```
 
@@ -601,7 +601,7 @@ Build the `run-arguments` string by combining these independent flags as needed:
 
 ### Decision Tree for Template Selection
 
-```
+```text
 User wants CI/CD for Code Analyzer
 ├── Platform?
 │   ├── GitHub Actions → Use forcedotcom/run-code-analyzer@v2

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

@@ -4,8 +4,8 @@ description: "Create custom Code Analyzer rules for Regex (pattern matching), PM
 metadata:
   version: "1.0"
   relatedSkills:
-    - "dx-code-analyzer-run"
     - "dx-code-analyzer-configure"
+    - "dx-code-analyzer-run"
   cliTools:
     - tool: ["git"]
       semver: ">=2.0.0"
@@ -102,7 +102,7 @@ These are non-negotiable rules. Violating any of them is a skill failure regardl
 
 \* **For ESLint:** ALWAYS check Tier 1 (built-in rules) and Tier 2 (configurable rules) BEFORE creating a custom plugin. See `references/eslint-rules-discovery.md`.
 
-⚠️ **"Both could work → Regex first" NEVER applies to JavaScript/LWC/TypeScript files.** JS/LWC/TS patterns MUST use ESLint — Regex cannot distinguish code from comments/strings in JS and produces false positives. Do NOT rationalize Regex for JS files based on "simplicity" or "no npm dependencies."
+**"Both could work → Regex first" NEVER applies to JavaScript/LWC/TypeScript files.** JS/LWC/TS patterns MUST use ESLint — Regex cannot distinguish code from comments/strings in JS and produces false positives. Do NOT rationalize Regex for JS files based on "simplicity" or "no npm dependencies."
 
 Tell the user which engine you chose and why. Respect their preference if they disagree.
 
@@ -116,7 +116,7 @@ When a rule should NOT apply to test classes, the approach differs by engine:
 | **Regex** | Use `ignores.files` in `code-analyzer.yml` with globs like `**/*Test.cls` | `regex_ignore` is per-LINE, not per-FILE — it CANNOT exclude entire test classes. Only use `regex_ignore` for per-line patterns like `// NOPMD` |
 | **ESLint** | Use `ignores` array in `eslint.config.js` | Standard ESLint file-level ignores |
 
-⚠️ **`regex_ignore` is NOT file-level exclusion.** It only skips matches on lines that ALSO match the ignore pattern. Example: `regex_ignore: "/@isTest/i"` only suppresses violations on lines containing `@isTest` — a SOQL query on line 50 of a test class still flags because line 50 doesn't contain `@isTest`. To exclude test files from regex rules entirely, use:
+**`regex_ignore` is NOT file-level exclusion.** It only skips matches on lines that ALSO match the ignore pattern. Example: `regex_ignore: "/@isTest/i"` only suppresses violations on lines containing `@isTest` — a SOQL query on line 50 of a test class still flags because line 50 doesn't contain `@isTest`. To exclude test files from regex rules entirely, use:
 ```yaml
 ignores:
   files:
@@ -124,7 +124,7 @@ ignores:
     - "**/*_Test.cls"
 ```
 
-⚠️ **`ignores.files` is GLOBAL** — it affects ALL engines and ALL rules. If you need test-class exclusion for some rules but not others (e.g., exclude tests from SOQL rules but still scan tests for @AuraEnabled), use **PMD with XPath** for the rules that need selective exclusion. PMD's XPath can structurally check `@Test = true()` per-method or per-class — Regex cannot.
+**`ignores.files` is GLOBAL** — it affects ALL engines and ALL rules. If you need test-class exclusion for some rules but not others (e.g., exclude tests from SOQL rules but still scan tests for @AuraEnabled), use **PMD with XPath** for the rules that need selective exclusion. PMD's XPath can structurally check `@Test = true()` per-method or per-class — Regex cannot.
 
 **Decision guide for Apex rules that should skip test classes:**
 - If the pattern is structural (method calls, annotations, nesting) → use PMD. XPath handles test-class exclusion natively.
@@ -180,7 +180,7 @@ When the user highlights a code block in their editor and asks to "catch this",
      --name "<RuleName>" --regex "<pattern>" --description "<desc>" \
      --severity <1-5> --file-extensions ".cls,.trigger"
    ```
-   ⚠️ **ALWAYS use the script.** Do NOT manually write regex patterns into `code-analyzer.yml` — regex characters (quotes, backslashes, braces) inside YAML cause parsing failures. The script handles serialization correctly.
+   **ALWAYS use the script.** Do NOT manually write regex patterns into `code-analyzer.yml` — regex characters (quotes, backslashes, braces) inside YAML cause parsing failures. The script handles serialization correctly.
 4. **Validate** — `sf code-analyzer rules --rule-selector regex:<RuleName>`
 5. **Test positive** — `sf code-analyzer run --rule-selector regex:<RuleName> --target <violation-sample>` — must find violations
 6. **Test negative** — `sf code-analyzer run --rule-selector regex:<RuleName> --target <clean-sample>` — must find 0 violations. If it flags clean code, your regex is too broad — go back and tighten the pattern.
@@ -190,10 +190,10 @@ When the user highlights a code block in their editor and asks to "catch this",
 ### For PMD/XPath Rules (Apex)
 
 1. **Write a minimal sample** (5-10 lines) demonstrating the violation. Write sample files inside the project workspace (e.g., a temporary `samples/` directory at the project root) so Code Analyzer can target them. **After both positive and negative tests pass, delete ALL sample files you created** — both the original samples and any copies made during testing. Do not leave temporary test fixtures in the user's project. For loop-based rules, the positive sample MUST include all 3 Apex loop types (`for-each`, traditional `for`, and `while`) — omitting any loop type means the XPath won't be validated against it and may silently miss violations.
-2. **⚠️ MANDATORY: Dump the AST** — `sf code-analyzer ast-dump --file <sample.cls> --output-file <ast.xml>` — this step is NOT optional. Do NOT skip it even if you "already know" the node names. Run it, read the output, confirm the exact node names and attributes.
+2. **MANDATORY: Dump the AST** — `sf code-analyzer ast-dump --file <sample.cls> --output-file <ast.xml>` — this step is NOT optional. Do NOT skip it even if you "already know" the node names. Run it, read the output, confirm the exact node names and attributes.
 3. **Read the AST output** — identify the target node and its attributes from the ACTUAL ast-dump output (not from memory). Use `references/apex-ast-reference.md` and `references/xpath-patterns.md` as supplementary context only.
 4. **Write XPath** — target the smallest stable node with discriminating attributes. Every node name in your XPath MUST appear verbatim in the ast-dump output you just read. Use `/Child` (direct child) vs `//Descendant` deliberately — check the ast-dump to understand which nodes are siblings vs nested.
-5. **⚠️ BEFORE creating the rule: Write a SEPARATE negative sample file** (5-10 lines) showing code that is CORRECT and must NOT be flagged. This MUST be a distinct file from the positive sample — do NOT combine positive and negative cases into one file. For loop-based rules, include `for (x : [SELECT...])` idiom. Run `sf code-analyzer ast-dump` on this negative sample file too. Read the output and trace your XPath against it — confirm it does NOT match any node in the negative AST. If it would match, go back to step 4 and tighten the XPath BEFORE proceeding. Do NOT skip this step or defer it until after rule creation. The negative file will be used again in step 9 for an explicit zero-violation confirmation.
+5. **BEFORE creating the rule: Write a SEPARATE negative sample file** (5-10 lines) showing code that is CORRECT and must NOT be flagged. This MUST be a distinct file from the positive sample — do NOT combine positive and negative cases into one file. For loop-based rules, include `for (x : [SELECT...])` idiom. Run `sf code-analyzer ast-dump` on this negative sample file too. Read the output and trace your XPath against it — confirm it does NOT match any node in the negative AST. If it would match, go back to step 4 and tighten the XPath BEFORE proceeding. Do NOT skip this step or defer it until after rule creation. The negative file will be used again in step 9 for an explicit zero-violation confirmation.
 6. **Create the rule** — run the script:
    ```bash
    node "<skill_dir>/scripts/create-pmd-rule.js" \
@@ -224,7 +224,7 @@ When the user highlights a code block in their editor and asks to "catch this",
        file_extensions:
          xml: [".xml"]
    ```
-   ⚠️ Do NOT add compound extensions like `.permissionset-meta.xml` — Code Analyzer's validator rejects them (`/^[.][a-zA-Z0-9]+$/` pattern). Just `.xml` covers all Salesforce metadata files automatically.
+   Do NOT add compound extensions like `.permissionset-meta.xml` — Code Analyzer's validator rejects them (`/^[.][a-zA-Z0-9]+$/` pattern). Just `.xml` covers all Salesforce metadata files automatically.
 6. **Write a SEPARATE negative sample file** — same as Apex rules: create a metadata file that is correct and must NOT be flagged. Verify the XPath does not match it BEFORE creating the rule. Both positive and negative samples should be `.xml` extension files in the workspace so PMD can scan them directly.
 7. **Create the rule** — run the script:
    ```bash
@@ -265,7 +265,7 @@ ESLint has 200+ built-in rules plus thousands more from plugins. DO NOT attempt
 
 ---
 
-0. **⚠️ MANDATORY: Run the ESLint discovery workflow FIRST.** 90% of ESLint requests are solved by built-in rules (Tier 1) or configurable rules like `no-restricted-syntax` (Tier 2). Creating a custom plugin (Tier 3) is a LAST RESORT. Before proceeding:
+0. **MANDATORY: Run the ESLint discovery workflow FIRST.** 90% of ESLint requests are solved by built-in rules (Tier 1) or configurable rules like `no-restricted-syntax` (Tier 2). Creating a custom plugin (Tier 3) is a LAST RESORT. Before proceeding:
    
    a) **Run:** `sf code-analyzer rules --rule-selector eslint`
    b) **Search** the output for keywords from the user's request (e.g., "console", "equal", "unused")
@@ -276,9 +276,9 @@ ESLint has 200+ built-in rules plus thousands more from plugins. DO NOT attempt
    
    **Validation:** After configuration, run `sf code-analyzer rules --rule-selector eslint:<ruleName>` to confirm it appears. If it doesn't, the config is wrong.
    
-   ⚠️ **Skipping this discovery workflow and creating a custom plugin when a built-in rule exists is a skill failure**, regardless of whether the custom plugin works.
+   **Skipping this discovery workflow and creating a custom plugin when a built-in rule exists is a skill failure**, regardless of whether the custom plugin works.
 
-⚠️ **Built-in ESLint rules vs. configurable ESLint rules:** Code Analyzer bundles a SUBSET of ESLint rules in its base config. Rules like `no-restricted-globals`, `no-restricted-syntax`, and `no-restricted-properties` are core ESLint rules but are NOT active until you enable them in an `eslint.config.js`. They WILL appear in `sf code-analyzer rules` output ONLY after you configure them. **Always validate** (step 4) to confirm the rule actually loaded — do NOT assume a rule exists just because it's a core ESLint rule.
+**Built-in ESLint rules vs. configurable ESLint rules:** Code Analyzer bundles a SUBSET of ESLint rules in its base config. Rules like `no-restricted-globals`, `no-restricted-syntax`, and `no-restricted-properties` are core ESLint rules but are NOT active until you enable them in an `eslint.config.js`. They WILL appear in `sf code-analyzer rules` output ONLY after you configure them. **Always validate** (step 4) to confirm the rule actually loaded — do NOT assume a rule exists just because it's a core ESLint rule.
 
 1. **Install the ESLint plugin** (skip if using a built-in/core ESLint rule) — `npm install --save-dev eslint-plugin-<name>`
 2. **Create/update `eslint.config.js`** — add plugin and rule configuration (or just enable the built-in rule with `"error"` severity). **The file MUST exist** before configuring `engines.eslint.eslint_config_file` in `code-analyzer.yml` — Code Analyzer validates the path and fails if the file is missing.
@@ -300,26 +300,26 @@ For `no-restricted-globals`, `no-restricted-syntax`, and `no-restricted-properti
 - User: "Ban console.log in LWC"
 - Discovery: `sf code-analyzer rules --rule-selector eslint | grep console` → finds `no-console`
 - Action: Enable `no-console` in eslint.config.js
-- Result: ✅ Done in 2 minutes (no custom plugin needed)
+- Result: Done in 2 minutes (no custom plugin needed)
 
 **Example 2: Configurable rule (Tier 2)**
 - User: "Ban setTimeout in LWC"
 - Discovery: No built-in `no-setTimeout` rule
 - Action: Use `no-restricted-globals` with custom message
-- Result: ✅ Done in 5 minutes (no custom plugin needed)
+- Result: Done in 5 minutes (no custom plugin needed)
 
 **Example 3: LWC plugin rule (Tier 1)**
 - User: "Ban innerHTML for XSS prevention"
 - Discovery: `@lwc/lwc/no-inner-html` already exists
 - Action: Enable `@lwc/lwc/no-inner-html` in config
-- Result: ✅ Done in 2 minutes (no custom plugin needed)
+- Result: Done in 2 minutes (no custom plugin needed)
 
 **Example 4: Custom plugin justified (Tier 3)**
 - User: "Flag imperative Apex calls without error handling"
 - Discovery: No built-in rule for this pattern
 - Analysis: Pattern requires checking `import` + `.then()` without `.catch()` — multi-node traversal
 - Action: Create custom plugin with visitor pattern
-- Result: ✅ Custom plugin is justified (20+ minutes effort)
+- Result: Custom plugin is justified (20+ minutes effort)
 
 See `references/eslint-rules-discovery.md` for complete discovery workflow.
 
@@ -375,11 +375,11 @@ When creating multiple PMD rules, use the `create-pmd-rule.js` script for the fi
 
 ### What NOT to do
 
-- ❌ Do NOT rewrite the entire `code-analyzer.yml` to reorganize it
-- ❌ Do NOT create all rules in parallel then validate all at once
-- ❌ Do NOT create a PMD rule with an unverified XPath from the reference docs — ast-dump each pattern
-- ❌ Do NOT mix engine types in one creation step (e.g., creating regex + PMD rules simultaneously)
-- ❌ Do NOT add `engines.eslint.eslint_config_file` to `code-analyzer.yml` before the file exists
+- Do NOT rewrite the entire `code-analyzer.yml` to reorganize it
+- Do NOT create all rules in parallel then validate all at once
+- Do NOT create a PMD rule with an unverified XPath from the reference docs — ast-dump each pattern
+- Do NOT mix engine types in one creation step (e.g., creating regex + PMD rules simultaneously)
+- Do NOT add `engines.eslint.eslint_config_file` to `code-analyzer.yml` before the file exists
 
 ---
 
@@ -393,7 +393,7 @@ When creating multiple PMD rules, use the `create-pmd-rule.js` script for the fi
 | Always validate after creation | `sf code-analyzer rules --rule-selector <engine>:<name>` catches config errors |
 | Always test against sample code | Catches XPath/regex mismatches before full scan |
 | Use `@FullMethodName` for method calls in XPath | More reliable than `@Image` or `@MethodName` alone |
-| **⚠️ NEVER skip `ast-dump`** | Run `ast-dump`, read output, THEN write XPath. No exceptions — even for "obvious" patterns. Using node names from memory without ast-dump verification is a skill failure. |
+| **NEVER skip `ast-dump`** | Run `ast-dump`, read output, THEN write XPath. No exceptions — even for "obvious" patterns. Using node names from memory without ast-dump verification is a skill failure. |
 | **PMD 7 boolean attributes: use `= false()` XPath function** | In PMD 7, boolean attributes like `@WithSharing`, `@Abstract`, `@Final` are ALWAYS present on the node (never absent). Compare with `= false()` (XPath boolean function), NOT string `'false'`. `@WithSharing = false()` works. `@WithSharing='false'` (string) does NOT. `not(@WithSharing)` does NOT (attribute is always present). |
 | `code-analyzer.yml` at project root | Auto-discovered by CLI — placing it elsewhere causes silent failures for rule authors |
 | **XML rules MUST use `local-name()`** | Salesforce metadata namespace breaks bare element names |
@@ -451,11 +451,11 @@ node "<skill_dir>/scripts/create-regex-rule.js" \
   --name "RuleName" --regex "/pattern/flags" ...
 ```
 
-⚠️ **DO NOT:**
-- ❌ Invent or generate script code yourself
-- ❌ Use bare relative paths like `node scripts/create-regex-rule.js` (won't resolve from user's CWD)
-- ❌ Use heredocs or inline script content
-- ❌ Skip resolving `<skill_dir>` — find the absolute path first
+**DO NOT:**
+- Invent or generate script code yourself
+- Use bare relative paths like `node scripts/create-regex-rule.js` (won't resolve from user's CWD)
+- Use heredocs or inline script content
+- Skip resolving `<skill_dir>` — find the absolute path first
 
 ---
 

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

@@ -160,7 +160,7 @@ security/OWASP → `Security` · performance → `Performance` · best practices
 ### 1.4 SPECIFIC RULE
 If the user names a rule (e.g., "ApexCRUDViolation", "no-unused-vars"): `--rule-selector <engine>:<ruleName>`, or just `<ruleName>` if engine is ambiguous.
 
-⚠️ **Partial names:** `--rule-selector` requires the **exact full** rule name (e.g., `@salesforce-ux/slds/no-hardcoded-values-slds2`, not `no-hardcoded-values`). No wildcards. If you are not 100% certain, look it up first — **do not guess**:
+**Partial names:** `--rule-selector` requires the **exact full** rule name (e.g., `@salesforce-ux/slds/no-hardcoded-values-slds2`, not `no-hardcoded-values`). No wildcards. If you are not 100% certain, look it up first — **do not guess**:
 ```bash
 sf code-analyzer rules --rule-selector all 2>&1 | grep -i "USER_KEYWORD"
 ```
@@ -246,12 +246,12 @@ Run the parse script straight after the scan — do not pause to ask:
 node "<skill_dir>/scripts/parse-results.js" "./code-analyzer-results-TIMESTAMP.json"
 ```
 
-⚠️ **DO NOT:**
-- ❌ Invent or generate script code yourself
-- ❌ Use bare relative paths like `node scripts/parse-results.js` (won't resolve from user's CWD)
-- ❌ Use heredocs or inline script content
-- ❌ Use `jq` as a substitute for the parse script (shell quoting will break)
-- ❌ Read the JSON file directly
+**DO NOT:**
+- Invent or generate script code yourself
+- Use bare relative paths like `node scripts/parse-results.js` (won't resolve from user's CWD)
+- Use heredocs or inline script content
+- Use `jq` as a substitute for the parse script (shell quoting will break)
+- Read the JSON file directly
 
 ### Presentation template
 
@@ -328,7 +328,7 @@ These are safe, deterministic fixes generated by the engines (not AI-generated).
 Would you like me to apply these fixes? (yes / no / select specific rules)
 ```
 
-⚠️ **Stop and wait for the user's reply, even if they originally said "scan and fix everything".** Apply only on a fresh "yes" / "apply" / "go ahead" in the next turn.
+**Stop and wait for the user's reply, even if they originally said "scan and fix everything".** Apply only on a fresh "yes" / "apply" / "go ahead" in the next turn.
 
 ### 6.4 Apply
 
@@ -346,7 +346,7 @@ node "<skill_dir>/scripts/summarize-fixes.js" "./code-analyzer-results-TIMESTAMP
 Then present:
 
 ```text
-### Engine-Provided Fixes Applied Successfully ✓
+### Engine-Provided Fixes Applied Successfully
 **Applied X auto-fixes across Y files.**
 
 | Severity | Fixes Applied |

package/skills/dx-code-analyzer-run/references/post-scan-workflows.md

@@ -82,7 +82,7 @@ When `--summary` is used, the `violations` array is omitted.
 
 Present query results using the same format as Step 5, but with a header indicating the active filter:
 
-```
+```text
 ## Filtered Results: [description of filter]
 
 **X matches** out of Y total violations.
@@ -192,7 +192,7 @@ node "<skill_dir>/scripts/describe-rule.js" "OperationWithLimitsInLoop"
 
 **For a successful lookup**, present:
 
-```
+```text
 ## Rule: ApexCRUDViolation
 
 | Property | Value |
@@ -219,7 +219,7 @@ Want me to show all violations of this rule in your scan results?
 
 **For multiple matches**, present:
 
-```
+```text
 I found multiple rules matching "CRUD":
 
 | # | Rule | Engine | Severity |
@@ -232,7 +232,7 @@ Which rule would you like details on?
 
 **For not found**, present:
 
-```
+```text
 I couldn't find a rule named "FakeRule". Would you like me to:
 - Search for similar rules? (I'll grep the full rule list)
 - List all rules for a specific engine or category?
@@ -253,7 +253,7 @@ Offer next steps:
 
 Present available rules in this format:
 
-```
+```text
 ## Available Rules: Security
 
 **Found X rules** across Y engines.

package/skills/dx-code-analyzer-run/references/vendor-file-handling.md

@@ -123,7 +123,7 @@ UMD/AMD/CommonJS wrapper       → 70% vendor
 
 ### Final Score
 
-```
+```text
 Weighted Score = (PathScore × 0.3) + (NameScore × 0.3) + (ContentScore × 0.4)
 
 > 70% = Vendor file
@@ -133,7 +133,7 @@ Weighted Score = (PathScore × 0.3) + (NameScore × 0.3) + (ContentScore × 0.4)
 
 ## Example Output
 
-```
+```text
 === INTELLIGENT VENDOR FILE DETECTION ===
 
 Original violations: 9714

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

@@ -1,7 +1,6 @@
 ---
 name: dx-org-switch
 description: "Switches the active Salesforce org (default target-org) using the Salesforce CLI. Use whenever someone wants to change which org CLI commands run against — whether they say \"switch org\", \"change default org\", \"set my org to\", \"use alias\", \"point to\", or describe wanting to work against a specific org, scratch org, sandbox, or production."
-compatibility: Salesforce CLI (sf) v2+
 metadata:
   cliTools:
     - tool: ["sf"]

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

@@ -1,7 +1,6 @@
 ---
 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."
-compatibility: "Requires get_brand_instructions and/or search_media_cms_channels MCP tools"
 metadata:
   version: "1.0"
 ---

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

@@ -1,7 +1,6 @@
 ---
 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"
   relatedSkills:
@@ -51,17 +50,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 +71,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 +100,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 +117,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 +128,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 +138,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 +148,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 +156,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 +290,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-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"]

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-platform-offline-validate/SKILL.md

@@ -2,6 +2,9 @@
 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"
+  relatedSkills:
+    - "mobile-platform-native-capabilities-integrate"
   cliTools:
     - tool: ["eslint"]
       semver: ">=8.0.0"
@@ -9,9 +12,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 +113,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/platform-lightning-app-coordinate/SKILL.md

@@ -84,7 +84,7 @@ This table shows which metadata types are commonly needed for Lightning Experien
 
 ### Phase 1: Data Model (Foundation)
 
-```
+```text
 Custom Objects (no dependencies)
     ↓
 Custom Fields (depends on: Objects exist)
@@ -99,7 +99,7 @@ Relationships (depends on: Both parent and child objects + fields exist)
 
 ### Phase 2: Business Logic (Optional - only if requested)
 
-```
+```text
 Validation Rules (depends on: Fields exist)
     ↓
 Flows (depends on: Objects, Fields exist)
@@ -112,7 +112,7 @@ Flows (depends on: Objects, Fields exist)
 
 ### Phase 3: User Interface
 
-```
+```text
 List Views (depends on: Objects, Fields exist)
     ↓
 Custom Tabs (depends on: Objects exist)
@@ -128,7 +128,7 @@ FlexiPages (depends on: Objects, Tabs exist)
 
 ### Phase 4: Application Assembly
 
-```
+```text
 Custom Application (depends on: Tabs exist)
 ```
 
@@ -138,7 +138,7 @@ Custom Application (depends on: Tabs exist)
 
 ### Phase 5: Security & Access
 
-```
+```text
 Permission Sets (depends on: Objects, Fields, Tabs, App exist)
 ```
 
@@ -170,7 +170,7 @@ Permission Sets (depends on: Objects, Fields, Tabs, App exist)
 
 Generate a structured plan listing:
 
-```
+```text
 Lightning App Build Plan: [App Name]
 
 DATA MODEL:
@@ -299,7 +299,7 @@ The completed build produces:
    - Organized by standard SFDX structure: `force-app/main/default/`
 2. **Metadata Files** - One file per component, organized by type:
 
-   ```
+   ```text
    force-app/main/default/
    ├── objects/              # Custom Objects (.object-meta.xml)
    ├── fields/               # Custom Fields (.field-meta.xml)
@@ -324,7 +324,7 @@ The completed build produces:
 
 **Example Summary Structure:**
 
-```
+```text
 Lightning App Build Complete: Project Management App
 
 METADATA GENERATED:
@@ -400,7 +400,7 @@ Log warning and continue if:
 
 **Warning Pattern:**
 
-```
+```yaml
 Warning: [Component Type] generation encountered issue
     Component: [Name]
     Issue: [Description]

package/skills/platform-metadata-retrieve/SKILL.md

@@ -1,7 +1,6 @@
 ---
 name: platform-metadata-retrieve
 description: "ALWAYS USE THIS SKILL to retrieve metadata from an org to your local project using the sf project retrieve start command. Supports multiple retrieval modes: retrieve all remote changes, retrieve by source directory, retrieve by metadata type with wildcards, retrieve by manifest (package.xml), or retrieve by package name. Use when the user asks to retrieve, pull, sync, or download metadata, Apex classes, custom objects, or org changes. Supports source format (default) or metadata format (ZIP). DO NOT TRIGGER for deploying metadata (use platform-metadata-deploy skill), listing metadata, or generating package.xml. NEVER use MCP tools - always use this skill and the Bash tool with sf project retrieve start."
-compatibility: Salesforce CLI (sf) v2+
 metadata:
   version: "1.0"
   relatedSkills: