@salesforce/afv-skills 1.26.0 → 1.28.0

package/skills/agentforce-architecture-analyze/scripts/tests/test_write_emit_ctx.py

@@ -32,9 +32,9 @@ from . import _bootstrap  # noqa: F401
 
 
 def _tools_dir() -> pathlib.Path:
-    """Absolute path to the skill's tools/ dir — where the scripts live."""
+    """Absolute path to the skill's scripts/ dir — where the emit helpers live."""
     here = pathlib.Path(__file__).resolve()
-    return here.parent.parent.parent / "tools"
+    return here.parent.parent
 
 
 def _run_script(script_name: str, env: dict) -> subprocess.CompletedProcess:
@@ -439,7 +439,7 @@ class EmitResultPositionalSafetyTests(unittest.TestCase):
 
     def test_build_block_happy_path_auto_promotes_without_asserting(self):
         """Sanity: the assertion does NOT fire under normal operation."""
-        # Force import of emit_result from the tools/ dir.
+        # Force import of emit_result from the scripts/ dir.
         import importlib.util
         spec = importlib.util.spec_from_file_location(
             "emit_result_mod", _tools_dir() / "emit_result.py",

package/skills/agentforce-architecture-analyze/{tools → scripts}/write_emit_ctx.py

@@ -83,7 +83,7 @@ import sys
 
 # local, dependency-free token scrub mirroring the patterns in
 # `scripts/rest_client.redact_text`. Keeping the redactor inline preserves
-# the tools/ <-> scripts/ decoupling (tools/ is stdlib-only by policy) and
+# the scripts/ emit helpers (stdlib-only by policy) and
 # avoids adding a sys.path hop on every write_emit_ctx invocation. The two
 # implementations must stay in sync; the shared regex shapes are:
 # * Authorization: Bearer <token>

package/skills/agentforce-observe/references/stdm-queries.md

@@ -24,9 +24,9 @@ Methods:
 mkdir -p <project-root>/force-app/main/default/classes
 
 # Copy from the skill's apex directory
-cp ../apex/AgentforceOptimizeService.cls \
+cp ../assets/apex/AgentforceOptimizeService.cls \
    <project-root>/force-app/main/default/classes/
-cp ../apex/AgentforceOptimizeService.cls-meta.xml \
+cp ../assets/apex/AgentforceOptimizeService.cls-meta.xml \
    <project-root>/force-app/main/default/classes/
 ```
 

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

@@ -189,7 +189,7 @@ When no custom objects needed:
         - `referenceTo`: (Lookup only) The target object API name
 - Include only objects and fields that are relevant to the flow being generated
 
-## 🎯 Mandatory Enhancement Rules
+## Mandatory Enhancement Rules
 - **userPrompt**: REQUIRED.
     - If the user requests a **single flow**: use the user's prompt as-is.
     - If the user requests **multiple flows**: you MUST **split** the request and write a **separate, focused `userPrompt` for each individual flow**. Each `userPrompt` must describe only ONE flow. Do NOT pass the entire multi-flow request as a single `userPrompt`. See the multiple flows section below for examples.

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

@@ -85,7 +85,7 @@ If no LBC exists (or not using LWC), select an SLDS Blueprint. See [references/c
 
 ## Hook Naming Traps
 
-SLDS hook families do NOT all follow the same naming pattern. Agents frequently invent hooks that don't exist by assuming `{prefix}-{number}` works universally. **Always verify a hook exists** via the bundled `search-hooks.cjs` script or `metadata/hooks-index.json` before using it.
+SLDS hook families do NOT all follow the same naming pattern. Agents frequently invent hooks that don't exist by assuming `{prefix}-{number}` works universally. **Always verify a hook exists** via the bundled `search-hooks.cjs` script or `assets/hooks-index.json` before using it.
 
 ### Trap 1: Font size hooks are NOT numbered
 
@@ -130,10 +130,10 @@ Run the appropriate search command **before** emitting any SLDS artifact:
 
 | Artifact | Verification command | Source of truth |
 |----------|---------------------|-----------------|
-| Styling hook (`--slds-g-*`) | `node scripts/search-hooks.cjs --prefix "<hook-name>"` | `metadata/hooks-index.json` |
-| Utility class (`slds-*`) | `node scripts/search-utilities.cjs --search "<class-name>"` | `metadata/utilities-index.json` |
-| Blueprint / CSS class | `node scripts/search-blueprints.cjs --search "<pattern>"` then read the YAML | `metadata/blueprints/components/*.yaml` |
-| Icon | `node scripts/search-icons.cjs --query "<description>"` | `metadata/icon-metadata.json` |
+| Styling hook (`--slds-g-*`) | `node scripts/search-hooks.cjs --prefix "<hook-name>"` | `assets/hooks-index.json` |
+| Utility class (`slds-*`) | `node scripts/search-utilities.cjs --search "<class-name>"` | `assets/utilities-index.json` |
+| Blueprint / CSS class | `node scripts/search-blueprints.cjs --search "<pattern>"` then read the YAML | `assets/blueprints/components/*.yaml` |
+| Icon | `node scripts/search-icons.cjs --query "<description>"` | `assets/icon-metadata.json` |
 
 If the search returns no match: **do not use the artifact.** Find an alternative from the search results or build custom with verified hooks.
 
@@ -187,10 +187,10 @@ This skill bundles comprehensive SLDS knowledge. Read files as needed -- don't r
 
 | Folder | Content | Index |
 |--------|---------|-------|
-| `guidance/overviews/` | Foundational concepts (color, spacing, typography, etc.) | [guidance/README.md](guidance/README.md) |
-| `guidance/styling-hooks/` | Hook categories with detailed usage | [guidance/README.md](guidance/README.md) |
-| `guidance/utilities/` | 27 utility class categories | [guidance/README.md](guidance/README.md) |
-| `guidance/slds-development-guide.md` | Full SLDS development guide | -- |
+| `references/overviews/` | Foundational concepts (color, spacing, typography, etc.) | [references/README.md](references/README.md) |
+| `references/styling-hooks/` | Hook categories with detailed usage | [references/README.md](references/README.md) |
+| `references/utilities/` | 27 utility class categories | [references/README.md](references/README.md) |
+| `references/slds-development-guide.md` | Full SLDS development guide | -- |
 
 ### Raw Metadata (structured data for lookup)
 
@@ -198,10 +198,10 @@ This skill bundles comprehensive SLDS knowledge. Read files as needed -- don't r
 
 | File | Content | Lines |
 |------|---------|-------|
-| `metadata/blueprints/components/*.yaml` | 85 blueprint specs (classes, variants, a11y, HTML) | ~50-200 each |
-| `metadata/hooks-index.json` | 523 hooks with values and CSS properties | ~6,300 |
-| `metadata/icon-metadata.json` | 1,732 icons with synonyms for search | ~38,500 |
-| `metadata/utilities-index.json` | 1,147 utility classes with CSS rules | ~6,900 |
+| `assets/blueprints/components/*.yaml` | 85 blueprint specs (classes, variants, a11y, HTML) | ~50-200 each |
+| `assets/hooks-index.json` | 523 hooks with values and CSS properties | ~6,300 |
+| `assets/icon-metadata.json` | 1,732 icons with synonyms for search | ~38,500 |
+| `assets/utilities-index.json` | 1,147 utility classes with CSS rules | ~6,900 |
 
 ---
 
@@ -219,7 +219,7 @@ Identify:
 
 1. **If LWC**: Check the [Lightning Component Library](https://developer.salesforce.com/docs/component-library/overview/components) for an LBC
 2. **Search blueprints**: `node scripts/search-blueprints.cjs --search "<pattern>"`
-3. **Read the blueprint YAML**: `metadata/blueprints/components/<name>.yaml` for exact classes, modifiers, states, and accessibility requirements
+3. **Read the blueprint YAML**: `assets/blueprints/components/<name>.yaml` for exact classes, modifiers, states, and accessibility requirements
 4. **No match?** Build custom with hooks (see Phase 3)
 
 Details: [references/component-selection.md](references/component-selection.md)
@@ -249,7 +249,7 @@ npx @salesforce-ux/slds-linter@latest lint <component-path>
 
 The linter catches hardcoded values, class overrides, and deprecated tokens. **Fix all violations before proceeding.** Do not rationalize violations as acceptable.
 
-**Step 2: Verify no invented hooks.** Confirm every `--slds-g-*` hook in the output exists in `metadata/hooks-index.json`. Cross-reference against the T051 check in [checklists.md](checklists.md).
+**Step 2: Verify no invented hooks.** Confirm every `--slds-g-*` hook in the output exists in `assets/hooks-index.json`. Cross-reference against the T051 check in [checklists.md](checklists.md).
 
 **Step 3: Run through [checklists.md](checklists.md)** for the checks the linter cannot automate:
 - All `var(--slds-g-*)` have fallback values (T002)

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

@@ -22,7 +22,7 @@ Code produced by this skill should score high on T-series checks.
 | **Shadow hooks** | Shadows use `var(--slds-g-shadow-*)` | T040 |
 | **Border radius hooks** | Border radius uses `var(--slds-g-radius-*)` | T041 |
 | **Color hooks numbered** | Every `--slds-g-color-*` hook ends in a number (no bare `on-surface`, `on-accent`, etc.) | T050 |
-| **No invented hooks** | Every hook referenced actually exists in `metadata/hooks-index.json` | T051 |
+| **No invented hooks** | Every hook referenced actually exists in `assets/hooks-index.json` | T051 |
 | **No hardcoded colors** | No hex, rgb, or named colors (linter also catches this) | linter |
 | **No class overrides** | No `.slds-*` class overrides (linter also catches this) | linter |
 | **No deprecated tokens** | No `--lwc-*` tokens (linter also catches this) | linter |

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

@@ -24,7 +24,7 @@ node scripts/search-blueprints.cjs --search "modal"
 # Found: Modals (category: Overlay, root: slds-modal)
 ```
 
-**Read blueprint YAML** for class details: `metadata/blueprints/components/modals.yaml`
+**Read blueprint YAML** for class details: `assets/blueprints/components/modals.yaml`
 
 Key takeaway: `LightningModal` handles the `slds-modal`, `slds-backdrop`, and ARIA attributes automatically. No need to apply blueprint classes manually in LWC.
 
@@ -99,8 +99,8 @@ node scripts/search-blueprints.cjs --search "badge"
 ```
 
 **Read YAMLs:**
-- `metadata/blueprints/components/cards.yaml` -- classes: `slds-card`, `slds-card__header`, `slds-card__body`, `slds-card__footer`
-- `metadata/blueprints/components/badges.yaml` -- classes: `slds-badge`, modifiers: `slds-badge_lightest`, `slds-badge_inverse`
+- `assets/blueprints/components/cards.yaml` -- classes: `slds-card`, `slds-card__header`, `slds-card__body`, `slds-card__footer`
+- `assets/blueprints/components/badges.yaml` -- classes: `slds-badge`, modifiers: `slds-badge_lightest`, `slds-badge_inverse`
 
 ### Phase 3: Apply Styling
 

package/skills/design-systems-slds-apply/references/component-selection.md

@@ -68,7 +68,7 @@ node scripts/search-blueprints.cjs --name "modals"
 
 ### How to read a blueprint YAML
 
-Each file in `metadata/blueprints/components/{name}.yaml` contains:
+Each file in `assets/blueprints/components/{name}.yaml` contains:
 
 ```yaml
 name: "Modals"
@@ -107,6 +107,6 @@ Rules for custom components:
 
 ## Deep Reference
 
-- Full blueprint details: `guidance/blueprints-index.md`
-- All blueprint YAMLs: `metadata/blueprints/components/`
+- Full blueprint details: `references/blueprints-index.md`
+- All blueprint YAMLs: `assets/blueprints/components/`
 - LBC documentation: [Lightning Component Library](https://developer.salesforce.com/docs/component-library/overview/components)

package/skills/design-systems-slds-apply/references/icons-decision-guide.md

@@ -119,6 +119,6 @@ Key classes:
 
 ## Deep Reference
 
-- Icon implementation guidance: `guidance/icons-guidance.md`
-- Icons overview: `guidance/overviews/icons.md`
-- Full icon metadata (1,732 icons with synonyms): `metadata/icon-metadata.json`
+- Icon implementation guidance: `references/icons-guidance.md`
+- Icons overview: `references/overviews/icons.md`
+- Full icon metadata (1,732 icons with synonyms): `assets/icon-metadata.json`

package/skills/design-systems-slds-apply/{guidance → references}/slds-development-guide.md

@@ -158,13 +158,13 @@ export default class MyModal extends LightningModal {
 
 ## Core Rules
 
-### Do ✅
+### Do
 - Follow hierarchy: LBC → Blueprints → Styling Hooks → Custom CSS
 - Use `var(--slds-g-*)` with fallbacks for all themeable values
 - Create custom classes (e.g., `my-*`) instead of overriding `.slds-*`
 - Verify components/hooks exist before implementing
 
-### Don't ❌
+### Don't
 - Hard-code colors, spacing, or typography
 - Override `.slds-*` classes directly
 - Use deprecated `--lwc-*` tokens as primary values

package/skills/design-systems-slds-apply/references/styling-decision-guide.md

@@ -24,7 +24,7 @@ Component hooks are scoped to specific Lightning Base Components. To find availa
 2. **Browser DevTools**: Render the LBC, inspect the element, and look for `--slds-c-*` properties in the computed styles
 3. **Known patterns**: Component hooks follow `--slds-c-{component}-{property}-{state}` naming, e.g., `--slds-c-button-success-shadow-hover`
 
-There is no centralized metadata file for `--slds-c-*` hooks — they are documented per-component. Some examples exist in `guidance/overviews/shadows.md` and `guidance/styling-hooks/index.md`.
+There is no centralized metadata file for `--slds-c-*` hooks — they are documented per-component. Some examples exist in `references/overviews/shadows.md` and `references/styling-hooks/index.md`.
 
 ---
 
@@ -46,7 +46,7 @@ Always use `var()` with a fallback value:
 
 The fallback in `var(--slds-g-*, fallback)` is used when the hook isn't loaded (e.g., outside Lightning Experience, in static HTML previews, or during SSR). Use the **light-mode default** value:
 
-1. **Look up the value in `metadata/hooks-index.json`** — each hook has a `value` field showing its resolved default
+1. **Look up the value in `assets/hooks-index.json`** — each hook has a `value` field showing its resolved default
 2. **Use the search script**: `node scripts/search-hooks.cjs --prefix "--slds-g-color-surface-"` shows values
 3. **Common defaults**: `#ffffff` for surfaces, `#181818` for text, `1rem` for spacing-4, `0.25rem` for radius-border-2
 
@@ -218,11 +218,11 @@ Some dimension values have no SLDS hook (e.g., `min-width: 7rem` for label align
 
 ## Deep Reference
 
-- Styling hooks index: `guidance/styling-hooks/index.md`
-- Color hooks deep dive: `guidance/styling-hooks/color/`
-- Color overview (85-5-10 rule): `guidance/overviews/color.md`
-- Spacing overview: `guidance/overviews/spacing.md`
-- Typography hooks: `guidance/styling-hooks/typography.md`
-- Borders overview: `guidance/overviews/borders.md`
-- Shadows overview: `guidance/overviews/shadows.md`
-- All 523 hooks searchable: `metadata/hooks-index.json`
+- Styling hooks index: `references/styling-hooks/index.md`
+- Color hooks deep dive: `references/styling-hooks/color/`
+- Color overview (85-5-10 rule): `references/overviews/color.md`
+- Spacing overview: `references/overviews/spacing.md`
+- Typography hooks: `references/styling-hooks/typography.md`
+- Borders overview: `references/overviews/borders.md`
+- Shadows overview: `references/overviews/shadows.md`
+- All 523 hooks searchable: `assets/hooks-index.json`

package/skills/design-systems-slds-apply/{guidance → references}/styling-hooks/index.md

@@ -245,7 +245,7 @@ font-size: var(--slds-g-font-size-base); /* Or use rem values */
 
 ## Critical Rules
 
-### ✅ DO:
+### DO:
 
 - Reference hooks with `var()`: `color: var(--slds-g-color-accent-1);`
 - Use numbered spacing: `spacing-4` not `spacing-medium`
@@ -254,7 +254,7 @@ font-size: var(--slds-g-font-size-base); /* Or use rem values */
 - Pair container colors with on-colors for text/icons
 - Follow the 50-point rule for text contrast, 40-point rule for UI elements
 
-### ❌ DON'T:
+### DON'T:
 
 - Reassign hook values: `--slds-g-color-accent-1: #ff0000;` ❌
 - Use private hooks (`--_slds-*` or `--slds-s-*`)

package/skills/design-systems-slds-apply/references/utilities-quick-ref.md

@@ -120,6 +120,6 @@ node scripts/search-utilities.cjs --pattern "slds-p-around_*"
 
 ## Deep Reference
 
-- Utility index: `guidance/utilities/index.md`
-- Individual category guides: `guidance/utilities/{category}.md`
-- Full metadata (1,147 classes): `metadata/utilities-index.json`
+- Utility index: `references/utilities/index.md`
+- Individual category guides: `references/utilities/{category}.md`
+- Full metadata (1,147 classes): `assets/utilities-index.json`

package/skills/design-systems-slds-apply/scripts/search-blueprints.cjs

@@ -13,7 +13,7 @@
 const fs = require('fs');
 const path = require('path');
 
-const BLUEPRINTS_DIR = path.join(__dirname, '..', 'metadata', 'blueprints', 'components');
+const BLUEPRINTS_DIR = path.join(__dirname, '..', 'assets', 'blueprints', 'components');
 
 function loadBlueprints() {
   const blueprints = [];
@@ -67,7 +67,7 @@ function run() {
     console.log(`Category: ${bp.category}`);
     console.log(`Root class: ${bp.rootClass}`);
     console.log(`Description: ${bp.description}`);
-    console.log(`\nFull YAML: metadata/blueprints/components/${bp.file}.yaml`);
+    console.log(`\nFull YAML: assets/blueprints/components/${bp.file}.yaml`);
     console.log('\nRead the full YAML file for classes, modifiers, states, accessibility, and example HTML.');
     return;
   }

package/skills/design-systems-slds-apply/scripts/search-hooks.cjs

@@ -15,7 +15,7 @@
 const fs = require('fs');
 const path = require('path');
 
-const INDEX_PATH = path.join(__dirname, '..', 'metadata', 'hooks-index.json');
+const INDEX_PATH = path.join(__dirname, '..', 'assets', 'hooks-index.json');
 
 function loadHooks() {
   if (!fs.existsSync(INDEX_PATH)) {

package/skills/design-systems-slds-apply/scripts/search-icons.cjs

@@ -13,7 +13,7 @@
 const fs = require('fs');
 const path = require('path');
 
-const ICONS_PATH = path.join(__dirname, '..', 'metadata', 'icon-metadata.json');
+const ICONS_PATH = path.join(__dirname, '..', 'assets', 'icon-metadata.json');
 
 function loadIcons() {
   if (!fs.existsSync(ICONS_PATH)) {

package/skills/design-systems-slds-apply/scripts/search-utilities.cjs

@@ -13,8 +13,8 @@
 const fs = require('fs');
 const path = require('path');
 
-const INDEX_PATH = path.join(__dirname, '..', 'metadata', 'utilities-index.json');
-const GUIDANCE_DIR = path.join(__dirname, '..', 'guidance', 'utilities');
+const INDEX_PATH = path.join(__dirname, '..', 'assets', 'utilities-index.json');
+const GUIDANCE_DIR = path.join(__dirname, '..', 'references', 'utilities');
 
 function loadUtilities() {
   if (!fs.existsSync(INDEX_PATH)) {
@@ -100,7 +100,7 @@ function run() {
 
     const guidePath = path.join(GUIDANCE_DIR, `${catKey}.md`);
     if (fs.existsSync(guidePath)) {
-      console.log(`\nDetailed guidance: guidance/utilities/${catKey}.md`);
+      console.log(`\nDetailed guidance: references/utilities/${catKey}.md`);
     }
     return;
   }

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

@@ -127,7 +127,7 @@ ls code-analyzer.yml code-analyzer.yaml 2>/dev/null
 
 The CLI auto-discovers `code-analyzer.yml` in the current directory. Since scans run from project root, the file must live there.
 
-### ⚠️ Rule Name Resolution — ALWAYS Before Writing YAML
+### Rule Name Resolution — ALWAYS Before Writing YAML
 
 When a user references rules by partial, descriptive, or approximate names (e.g., "the doc rule", "CRUD violation", "console rule", "hardcoded values"), you MUST resolve to exact rule names using the lookup in **Step 6.1** BEFORE writing any YAML. The `code-analyzer.yml` file silently ignores rule names that don't exactly match — there is no error, the override just won't apply.
 

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

@@ -9,11 +9,11 @@ metadata:
 
 # Running Code Analyzer Skill
 
-## ⚠️ CRITICAL: Mandatory Script Usage
+## CRITICAL: Mandatory Script Usage
 
 Every interaction with Code Analyzer results MUST go through the bundled scripts in `<skill_dir>/scripts/`. No exceptions.
 
-### ❌ WRONG — never do this:
+### WRONG — never do this:
 
 ```bash
 # WRONG: inline Python to parse results
@@ -31,7 +31,7 @@ Read tool → code-analyzer-results-*.json
 
 Also forbidden: `run_code_analyzer` and any `mcp__*` tool — Bash only.
 
-### ✅ RIGHT — always do this:
+### RIGHT — always do this:
 
 ```bash
 # Summarize scan results

package/skills/dx-code-analyzer-run/examples/command-variations.md

@@ -297,7 +297,7 @@ sf code-analyzer run \
 
 ## Anti-Patterns (DO NOT USE)
 
-### ❌ Using `--format` flag
+### Using `--format` flag
 ```bash
 # WRONG - v3 syntax, does not exist in v4+
 sf code-analyzer run --format json
@@ -306,7 +306,7 @@ sf code-analyzer run --format json
 
 ---
 
-### ❌ Using `$TIMESTAMP` variable in command
+### Using `$TIMESTAMP` variable in command
 ```bash
 # WRONG - variable substitution fails in permission prompts
 sf code-analyzer run --output-file "./results-${TIMESTAMP}.json"
@@ -315,7 +315,7 @@ sf code-analyzer run --output-file "./results-${TIMESTAMP}.json"
 
 ---
 
-### ❌ Running in background for long scans
+### Running in background for long scans
 ```bash
 # WRONG - loses output stream
 sf code-analyzer run --rule-selector sfge &
@@ -324,7 +324,7 @@ sf code-analyzer run --rule-selector sfge &
 
 ---
 
-### ❌ Partial rule names
+### Partial rule names
 ```bash
 # WRONG - returns 0 results
 sf code-analyzer run --rule-selector "no-hardcoded-values"

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

@@ -1,6 +1,6 @@
 ---
 name: dx-devops-test-failures-analyze
-description: "Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request. Analysis is pure reasoning; work-item creation is a confirmation-gated write. Use this skill to explain failures or improvement suggestions, translate Code Analyzer violations, or track a fix as a work item. TRIGGER when: a run failed and the user wants root cause; a quality gate failure needs explaining; violations need translating; the user shares a failure payload and asks how to address it; wants to strengthen tests; or wants to create a fix work item, log a remediation, or assign a failure. DO NOT TRIGGER when: the user wants fix code written (use generating-apex) or new test classes authored (use generating-apex-test)."
+description: "Analyzes DevOps Center test failures and Code Analyzer violations in plain language — failure category, offending file/class/method/line, rule violated, fix direction, and prioritized improvement suggestions (test-code vs production-code) — then optionally creates a tracked fix WorkItem on explicit request. Analysis is pure reasoning; work-item creation is a confirmation-gated write. Use this skill to explain failures or improvement suggestions, translate Code Analyzer violations, or track a fix as a work item. TRIGGER when: a run failed and the user wants root cause; a quality gate failure needs explaining; violations need translating; the user shares a failure payload and asks how to address it; wants to strengthen tests; or wants to create a fix work item, log a remediation, or assign a failure. DO NOT TRIGGER when: the user wants fix code written (use platform-apex-generate) or new test classes authored (use platform-apex-test-generate)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"
@@ -86,4 +86,4 @@ If no `DevopsProject` exists in the org, report that the work item cannot be cre
 
 - **`dx-devops-test-suite-run`** — produces the failure payload (via its polling step) that feeds this skill.
 - **`dx-devops-test-suite-assignments-configure`** — assign/strengthen the suites whose tests are failing.
-- **`generating-apex` / `generating-apex-test`** — to actually write fix code or new test classes (out of scope here).
+- **`platform-apex-generate` / `platform-apex-test-generate`** — to actually write fix code or new test classes (out of scope here).

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

@@ -1,6 +1,6 @@
 ---
 name: dx-devops-test-suite-assignments-configure
-description: "Recommends and manages DevOps Center test suite assignments for pipeline stages. Mode A analyzes a commit diff against assigned suite metadata to recommend relevant existing suites and flag coverage gaps (pure reasoning). Modes B-D assign a single suite, bulk-map multiple suites with a mandatory impact preview, or add/remove test classes with governance rules, via the testSuiteStages Connect API. Use this skill to recommend suites for a commit, assign or map suites to stages, or add/remove tests in a suite. TRIGGER when: the user asks which suites to run for a commit/diff or what covers their changes; a suite is unlinked and the user wants it assigned; the user wants to configure suite-to-stage mappings, assign multiple suites, or add/remove/sync tests in a suite. DO NOT TRIGGER when: configuring or syncing a test provider (use dx-devops-test-pipeline-configure), running suites (use dx-devops-test-suite-run), or authoring/running tests directly (use generating-apex-test or running-apex-tests)."
+description: "Recommends and manages DevOps Center test suite assignments for pipeline stages. Mode A analyzes a commit diff against assigned suite metadata to recommend relevant existing suites and flag coverage gaps (pure reasoning). Modes B-D assign a single suite, bulk-map multiple suites with a mandatory impact preview, or add/remove test classes with governance rules, via the testSuiteStages Connect API. Use this skill to recommend suites for a commit, assign or map suites to stages, or add/remove tests in a suite. TRIGGER when: the user asks which suites to run for a commit/diff or what covers their changes; a suite is unlinked and the user wants it assigned; the user wants to configure suite-to-stage mappings, assign multiple suites, or add/remove/sync tests in a suite. DO NOT TRIGGER when: configuring or syncing a test provider (use dx-devops-test-pipeline-configure), running suites (use dx-devops-test-suite-run), or authoring/running tests directly (use platform-apex-test-generate or platform-apex-test-run)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"

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

@@ -1,6 +1,6 @@
 ---
 name: dx-devops-test-suite-run
-description: "Runs DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) end to end: triggers async execution via the Connect API after an explicit confirmation gate, then polls by runId at provider-specific intervals until it completes, fails, or times out, and hands results to failure analysis. Also retriggers a quality gate after fixes, but only once coverage meets the threshold. Use this skill when a user wants to run, kick off, or launch test suites on a stage, re-run a quality gate, or watch an in-progress run to completion. TRIGGER when: the user wants to run/launch suites on a stage, execute tests before or after promotion, re-run a quality gate after fixing failures, unblock a blocked promotion after adding tests, or poll/watch an in-progress run. DO NOT TRIGGER when: running sf apex run test directly (use running-apex-tests), or configuring a NEW gate or threshold (use dx-devops-test-pipeline-configure)."
+description: "Runs DevOps Center test suites on a pipeline stage (Pre-Promote, Post-Promote, or Review event) end to end: triggers async execution via the Connect API after an explicit confirmation gate, then polls by runId at provider-specific intervals until it completes, fails, or times out, and hands results to failure analysis. Also retriggers a quality gate after fixes, but only once coverage meets the threshold. Use this skill when a user wants to run, kick off, or launch test suites on a stage, re-run a quality gate, or watch an in-progress run to completion. TRIGGER when: the user wants to run/launch suites on a stage, execute tests before or after promotion, re-run a quality gate after fixing failures, unblock a blocked promotion after adding tests, or poll/watch an in-progress run. DO NOT TRIGGER when: running sf apex run test directly (use platform-apex-test-run), or configuring a NEW gate or threshold (use dx-devops-test-pipeline-configure)."
 metadata:
   version: "1.0"
   minApiVersion: "67.0"

package/skills/dx-devops-test-suite-run/references/error-handling.md

@@ -28,4 +28,4 @@ If no `DevopsTestExecution` record matches the runId, report it gracefully and d
 
 ## Do NOT use `sf apex run test`
 
-That command is for the `running-apex-tests` skill, not DevOps Center test suites.
+That command is for the `platform-apex-test-run` skill, not DevOps Center test suites.

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

@@ -12,7 +12,7 @@ Assigns one or more permission sets to org users using `sf org assign permset`.
 
 ---
 
-## ⚠️ Tool Restrictions
+## Tool Restrictions
 
 **Use ONLY the Bash tool** to execute `sf org assign permset`. Do NOT use MCP tools like `assign_permission_set` — ignore them completely.
 

package/skills/experience-lwc-generate/references/async-notification-patterns.md

@@ -617,7 +617,7 @@ connectedCallback() {
 
 ## Best Practices
 
-### DO ✅
+### DO
 
 | Practice | Reason |
 |----------|--------|
@@ -627,7 +627,7 @@ connectedCallback() {
 | Use `refreshApex` after events | Keeps wire data in sync |
 | Set reasonable replay ID | `-1` for real-time, `-2` for recovery |
 
-### DON'T ❌
+### DON'T
 
 | Anti-Pattern | Problem |
 |--------------|---------|

package/skills/experience-lwc-generate/references/state-management.md

@@ -511,7 +511,7 @@ export default class ComposedStateComponent extends LightningElement {
 
 ## Anti-Patterns to Avoid
 
-### ❌ BAD: Mutating Objects In Place
+### BAD: Mutating Objects In Place
 
 ```javascript
 // DON'T - won't trigger reactivity
@@ -519,7 +519,7 @@ this.user.name = 'New Name';
 this.items.push(newItem);
 ```
 
-### ✅ GOOD: Create New References
+### GOOD: Create New References
 
 ```javascript
 // DO - triggers reactivity
@@ -527,7 +527,7 @@ this.user = { ...this.user, name: 'New Name' };
 this.items = [...this.items, newItem];
 ```
 
-### ❌ BAD: Heavy Computation in Getters
+### BAD: Heavy Computation in Getters
 
 ```javascript
 // DON'T - runs every render cycle
@@ -539,7 +539,7 @@ get expensiveComputation() {
 }
 ```
 
-### ✅ GOOD: Cache Computed Values
+### GOOD: Cache Computed Values
 
 ```javascript
 _cachedResult;
@@ -558,7 +558,7 @@ get optimizedComputation() {
 }
 ```
 
-### ❌ BAD: Forgetting to Unsubscribe
+### BAD: Forgetting to Unsubscribe
 
 ```javascript
 // DON'T - memory leak
@@ -567,7 +567,7 @@ connectedCallback() {
 }
 ```
 
-### ✅ GOOD: Clean Up Subscriptions
+### GOOD: Clean Up Subscriptions
 
 ```javascript
 // DO - proper cleanup