@salesforce/afv-skills 1.29.0 → 1.30.0

package/README.md

@@ -4,6 +4,8 @@ This repository provides a curated collection of Salesforce agent skills for bui
 
 The skills are contributed by Salesforce and the broader community. It’s optimized for Agentforce Vibes and can be used with any AI tool that supports skills.
 
+> ⚠️ **Expect frequent changes.** The Salesforce skills library is evolving rapidly as we refine patterns and incorporate feedback. Skills may be renamed, restructured, or removed between releases — they do not follow the same stability guarantees as GA platform APIs. If you’ve forked or synced the repository, be prepared for upstream changes that may conflict with local modifications. This repository is always the source of truth.
+
 ## 🗂️ Structure
 
 ```

package/package.json

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

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

@@ -44,7 +44,7 @@ See `SKILL.md` for the full flag table and sample prompts.
 
 ## Directory layout
 
-```
+```text
 agentforce-architecture-analyze/
 ├── SKILL.md                       Skill contract (inputs, outputs, pipeline, invariants)
 ├── README.md                      This file
@@ -86,7 +86,7 @@ agentforce-architecture-analyze/
 
 ### Channel strategy — SOQL-first
 
-```
+```text
 Seed query: planner_definition_by_agent_chain (chain-LIKE lookup → planner id)
 
 6 parallel Tooling SOQL channels (keyed on the resolved planner id):
@@ -147,9 +147,3 @@ Per-branch ancestor-path cycle detection is the primary termination primitive: t
 | `INVALID_FIELD` from a SOQL asset | Salesforce renamed / removed the field in a quarterly release. Run with `--reprobe` to refresh the 7-day channel cache and pick up the new schema |
 | `STATUS=PROBE_FAILED` on first run | Channel probe saw a mandatory field missing. Check `channels.json` under the probe cache dir for which sObject / field — may require org-side feature enablement |
 | Tree for classic ReAct agent shows `_unresolved` entries for NGA plugins | Expected — the NGA external-plugin retrieve is skipped when the planner shape is classic. Those entries can be ignored |
-
----
-
-## Author
-
-Raghul Jayagopal (RJ), Salesforce ANZ FDE.

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

@@ -157,14 +157,14 @@ exit "$_rc"
 
 All artifacts under `~/.vibe/data/agentforce-architecture-analyze/<org_id15>/<agent_api_name>__<agent_version>/` (default; override with `--data-dir <path>`):
 
-```
+```xml
 <agent>_<ver>_metadata_tree.json   primary artifact — normalized planner/topic/action/flow/apex/prompt/plugin tree
 <agent>_<ver>_architecture.md      human-readable section-by-section rendering (H1 + 7 numbered sections, plus a conditional Dependency graph appendix). Mermaid diagrams are embedded inside the relevant sections (Action tree, Data flow, and Dependency graph)
 ```
 
 ## Pipeline — inline, no subagent
 
-```
+```text
 resolve_bot.py        → BotDefinition + BotVersion + planner name lookup
 retrieve_planner.py   → Metadata API zip retrieve for GenAiPlannerBundle (+ NGA plugins if present)
 parallel_retrieve.py  → 6 parallel Tooling SOQL channels fan out from the planner id

package/skills/agentforce-architecture-analyze/references/contract.json

@@ -1,5 +1,5 @@
 {
-  "_doc": "retired-name references replaced with plugin-scoped layout. Machine-readable I/O contract for investigating-agentforce-architecture. Orchestrator code reads this file (not SKILL.md prose) to discover the input schema, output keys, STATUS enum, and error-contract rules. The architecture skill runs inline (no subagent).",
+  "_doc": "retired-name references replaced with plugin-scoped layout. Machine-readable I/O contract for agentforce-architecture-analyze. Orchestrator code reads this file (not SKILL.md prose) to discover the input schema, output keys, STATUS enum, and error-contract rules. The architecture skill runs inline (no subagent).",
   "_schema_version": "3.1",
   "_schema_notes": "3.1 (2026-05-05) canonicalizes `invocation_type` on STANDARD_ACTION / UNKNOWN nodes in the metadata tree. Prior versions split this across `raw_invocation_type` (bundle-sourced nodes) and `raw_action_type` (flow-actionCall-sourced nodes). Both legacy keys are still tolerated by readers for one release.",
   "input": {
@@ -35,15 +35,15 @@
       },
       "work_dir": {
         "type": "absolute_path",
-        "description": "Ephemeral scratch. Default: /tmp/investigating-agentforce-architecture-<epoch>-<rand>."
+        "description": "Ephemeral scratch. Default: /tmp/agentforce-architecture-analyze-<epoch>-<rand>."
       },
       "cache_root": {
         "type": "absolute_path",
-        "description": "Internal rebuildable cache root. Default: ~/.vibe/cache/investigating-agentforce-architecture. Override with --cache-dir <path>."
+        "description": "Internal rebuildable cache root. Default: ~/.vibe/cache/agentforce-architecture-analyze. Override with --cache-dir <path>."
       },
       "data_root": {
         "type": "absolute_path",
-        "description": "Durable user-facing output root. Default: ~/.vibe/data/investigating-agentforce-architecture. Override with --data-dir <path>."
+        "description": "Durable user-facing output root. Default: ~/.vibe/data/agentforce-architecture-analyze. Override with --data-dir <path>."
       },
       "force_refresh": {
         "type": "boolean",

package/skills/agentforce-architecture-analyze/references/soql_fields.md

@@ -64,7 +64,7 @@ Every edge is strictly **forward** from the entry query
 (`GenAiPlannerDefinition WHERE DeveloperName = :planner_name`). No
 backward lookups.
 
-```
+```text
 BotDefinition (Data API, PK Id, matched by DeveloperName)
  └── BotVersion (Data API, FK BotDefinitionId)
  │ [resolved to planner name via Bot metadata retrieve]

package/skills/data360-activate/README.md

@@ -36,4 +36,3 @@ sf data360 data-action-target list -o myorg 2>/dev/null
 - [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
 - [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
 - [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
-- [CREDITS.md](CREDITS.md)

package/skills/data360-activate/SKILL.md

@@ -107,11 +107,9 @@ Next step: <destination validation or downstream testing>
 
 ## References
 
-- [README.md](README.md)
 - [../data360-orchestrate/assets/definitions/activation-target.template.json](../data360-orchestrate/assets/definitions/activation-target.template.json)
 - [../data360-orchestrate/assets/definitions/activation.template.json](../data360-orchestrate/assets/definitions/activation.template.json)
 - [../data360-orchestrate/assets/definitions/data-action-target.template.json](../data360-orchestrate/assets/definitions/data-action-target.template.json)
 - [../data360-orchestrate/assets/definitions/data-action.template.json](../data360-orchestrate/assets/definitions/data-action.template.json)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)
 - [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
 - [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)

package/skills/data360-connect/README.md

@@ -55,5 +55,3 @@ sf data360 connection schema-upsert -o myorg --name <connector-id> -f examples/c
 
 - [SKILL.md](SKILL.md)
 - [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)
-- [CREDITS.md](CREDITS.md)

package/skills/data360-connect/SKILL.md

@@ -142,7 +142,6 @@ Next step: <prepare phase or connector follow-up>
 
 ## References
 
-- [README.md](README.md)
 - [examples/connections/heroku-postgres.json](examples/connections/heroku-postgres.json)
 - [examples/connections/redshift.json](examples/connections/redshift.json)
 - [examples/connections/sharepoint-unstructured.json](examples/connections/sharepoint-unstructured.json)
@@ -151,4 +150,3 @@ Next step: <prepare phase or connector follow-up>
 - [examples/connections/ingest-api-schema.json](examples/connections/ingest-api-schema.json)
 - [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)
 - [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

package/skills/data360-harmonize/SKILL.md

@@ -107,7 +107,6 @@ Next step: <segment / retrieve / follow-up>
 
 ## References
 
-- [README.md](README.md)
 - [../data360-orchestrate/assets/definitions/dmo.template.json](../data360-orchestrate/assets/definitions/dmo.template.json)
 - [../data360-orchestrate/assets/definitions/mapping.template.json](../data360-orchestrate/assets/definitions/mapping.template.json)
 - [../data360-orchestrate/assets/definitions/relationship.template.json](../data360-orchestrate/assets/definitions/relationship.template.json)

package/skills/data360-orchestrate/README.md

@@ -47,7 +47,6 @@ See [references/plugin-setup.md](references/plugin-setup.md).
 | [scripts/diagnose-org.mjs](scripts/diagnose-org.mjs) | Classify org readiness by phase before mutating Data Cloud assets |
 | [references/feature-readiness.md](references/feature-readiness.md) | Map high-signal errors and feature gates to concrete next steps |
 | [assets/definitions/](assets/definitions/) | Generic JSON templates for repeatable Data Cloud definition files |
-| [UPSTREAM.md](UPSTREAM.md) | Upstream mapping for future distillation and maintenance |
 
 ## Generic templates
 
@@ -119,9 +118,3 @@ sf data360 activation platforms -o myorg 2>/dev/null
 - [SKILL.md](SKILL.md) - Orchestrator guidance
 - [references/plugin-setup.md](references/plugin-setup.md) - Plugin install and verification
 - [references/feature-readiness.md](references/feature-readiness.md) - Readiness classification and setup guidance
-- [UPSTREAM.md](UPSTREAM.md) - Upstream tracking and distillation policy
-- [CREDITS.md](CREDITS.md) - Contributor and source attribution
-
-## Primary contributor
-
-**Gnanasekaran Thoppae** — primary contributor for the data360-orchestrate family.

package/skills/data360-orchestrate/SKILL.md

@@ -215,10 +215,8 @@ Next step: <next phase, setup guidance, or cross-skill handoff>
 ## Reference Map
 
 ### Start here
-- [README.md](README.md)
 - [references/plugin-setup.md](references/plugin-setup.md)
 - [references/feature-readiness.md](references/feature-readiness.md)
-- [UPSTREAM.md](UPSTREAM.md)
 
 ### Phase skills
 - [data360-connect](../data360-connect/SKILL.md)

package/skills/data360-prepare/README.md

@@ -48,4 +48,3 @@ sf data360 connection run-existing -o myorg --name <connection-id> 2>/dev/null
 - [SKILL.md](SKILL.md)
 - [examples/ingestion-api/README.md](examples/ingestion-api/README.md)
 - [../data360-orchestrate/assets/definitions/data-stream.template.json](../data360-orchestrate/assets/definitions/data-stream.template.json)
-- [CREDITS.md](CREDITS.md)

package/skills/data360-prepare/SKILL.md

@@ -183,7 +183,6 @@ Next step: <harmonize or retrieve>
 
 ## References
 
-- [README.md](README.md)
 - [examples/ingestion-api/README.md](examples/ingestion-api/README.md)
 - [../data360-orchestrate/assets/definitions/data-stream.template.json](../data360-orchestrate/assets/definitions/data-stream.template.json)
 - [../data360-orchestrate/references/plugin-setup.md](../data360-orchestrate/references/plugin-setup.md)

package/skills/data360-query/README.md

@@ -41,4 +41,3 @@ sf data360 query hybrid -o myorg --index Knowledge_Index --query "reset password
 
 - [SKILL.md](SKILL.md)
 - [../data360-orchestrate/assets/definitions/search-index.template.json](../data360-orchestrate/assets/definitions/search-index.template.json)
-- [CREDITS.md](CREDITS.md)

package/skills/data360-query/SKILL.md

@@ -111,7 +111,6 @@ Next step: <segment / harmonize / follow-up>
 
 ## References
 
-- [README.md](README.md)
 - [examples/search-indexes/vector-knowledge.json](examples/search-indexes/vector-knowledge.json)
 - [examples/search-indexes/hybrid-structured.json](examples/search-indexes/hybrid-structured.json)
 - [../data360-orchestrate/assets/definitions/search-index.template.json](../data360-orchestrate/assets/definitions/search-index.template.json)

package/skills/data360-segment/README.md

@@ -33,4 +33,3 @@ sf data360 calculated-insight list -o myorg 2>/dev/null
 - [SKILL.md](SKILL.md)
 - [../data360-orchestrate/assets/definitions/calculated-insight.template.json](../data360-orchestrate/assets/definitions/calculated-insight.template.json)
 - [../data360-orchestrate/assets/definitions/segment.template.json](../data360-orchestrate/assets/definitions/segment.template.json)
-- [CREDITS.md](CREDITS.md)

package/skills/data360-segment/SKILL.md

@@ -107,8 +107,6 @@ Next step: <act / retrieve / follow-up>
 
 ## References
 
-- [README.md](README.md)
 - [../data360-orchestrate/assets/definitions/calculated-insight.template.json](../data360-orchestrate/assets/definitions/calculated-insight.template.json)
 - [../data360-orchestrate/assets/definitions/segment.template.json](../data360-orchestrate/assets/definitions/segment.template.json)
 - [../data360-orchestrate/references/feature-readiness.md](../data360-orchestrate/references/feature-readiness.md)
-- [../data360-orchestrate/UPSTREAM.md](../data360-orchestrate/UPSTREAM.md)

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

@@ -1,7 +1,7 @@
 ---
 name: experience-cms-brand-apply
 description: "Extracts, retrieves, and applies CMS brand guidelines (voice, tone, style, colors, typography) to generated content. Use this skill ANY TIME a user request involves branding, brand voice, brand tone, brand guidelines, brand identity, brand styling, or applying a brand to content. Triggers for requests like \"apply my brand\", \"use our brand voice\", \"match our brand guidelines\", \"find my brand\", \"search for brand\", \"get brand instructions\", \"apply brand tone\". Handles the full workflow: searching for brands in Salesforce CMS, extracting brand instructions, and applying brand voice/tone/guidelines to generated content. Does not apply to media/image search (use experience-content-media-search skill), logo search, or creating new brand definitions."
-compatibility: "Requires get_brand_instructions and/or search_brands MCP tools"
+compatibility: "Requires get_brand_instructions and/or search_media_cms_channels MCP tools"
 metadata:
   version: "1.0"
 ---
@@ -44,7 +44,7 @@ When a user requests branded content:
 
 Copy this checklist and track your progress:
 
-```
+```text
 CMS Branding Progress:
 - [ ] Step 1: Determine if brand is already identified or needs search
 - [ ] Step 2: Search for brands (if needed) and present options to user
@@ -63,35 +63,63 @@ Check if the user has already specified which brand to use:
 
 ## Step 2: Search for Brands
 
-**Tool:** `search_brands`
+**Tool:** `search_media_cms_channels`
+
+Brands are stored as CMS content of type `sfdc_cms__brand`. Search for them by
+querying the CMS channels with the brand content type.
+
+> **Note:** Brand content search (`contentTypeFqn=sfdc_cms__brand`) is explicitly
+> excluded from the `experience-content-media-search` skill's scope. Calling
+> `search_media_cms_channels` directly here is correct and intentional — do not
+> route brand search through `experience-content-media-search`.
 
 **Process:**
 
-1. **Determine search query** — Use the user's description, company name, or a general keyword
-2. **Build the request:**
+1. **Determine search query** — Use the user's keyword. Brand search matches on
+   brand title and description.
+2. **Build the request** with the fixed brand-search input contract:
 
 ```json
 {
   "inputs": [{
-    "searchQuery": "keyword or brand name"
+    "searchKeyword": "keyword",
+    "searchLanguage": "<detected_language>",
+    "channelType": "PublicUnauthenticated",
+    "contentTypeFqn": "sfdc_cms__brand",
+    "pageOffset": 0,
+    "searchLimit": 25
   }]
 }
 ```
 
-3. **Call `search_brands`** with the query
-4. **Parse the response** — Extract brand results:
+   Field rules:
+   - `searchKeyword` — the user's keyword input
+   - `searchLanguage` — auto-detect from the user's input; if unsure, use `en_US`
+   - `channelType` — always `PublicUnauthenticated` (brand content is delivered
+     via the public CMS channel; authenticated-channel brand search is not
+     supported by this tool)
+   - `contentTypeFqn` — always `sfdc_cms__brand`
+   - `pageOffset` — `0`
+   - `searchLimit` — `25`
+
+3. **Call `search_media_cms_channels`** with the request
+4. **Parse the response** — A brand result has an ID starting with **`9Ps`**. Extract:
    - `managedContentId` — Unique ID (use this for extraction in Step 3)
    - `managedContentKey` — Content key identifier
    - `title` — Brand display name
-   - `contentUrl` — URL to the brand content
-   - `totalResults` — Number of brands found
+   - `contentUrl` — URL to the brand content, found under
+     `managedContentChannelDeliveryDetails[0].contentUrl`
+   - `pageNumber`, `pageSize`, `totalResults` — pagination summary
 
 ### Presenting Brand Results
 
-**If multiple brands found**, use `ask_followup_question` to present options:
+**If brands found**, first show a summary line, then use `ask_followup_question`
+to present options:
 
-```
-I found [N] brands in your CMS. Which one should I apply?
+```text
+Showing [N] of [totalResults] total results (page [pageNumber], page size [pageSize]).
+
+Which brand should I apply?
 
 1. [Brand Title 1]
 2. [Brand Title 2]
@@ -100,15 +128,18 @@ I found [N] brands in your CMS. Which one should I apply?
 Which brand would you like to use?
 ```
 
+When the user replies with their selection, do NOT perform another search —
+proceed immediately to Step 3.
+
 **If one brand found**, confirm with the user:
 
-```
+```text
 I found the brand "[Brand Title]". Should I apply this brand's guidelines to the content?
 ```
 
 **If no brands found:**
 
-```
+```text
 No brands found in Salesforce CMS. To use branding:
 1. Create a brand in Salesforce CMS (Content Type: sfdc_cms__brand)
 2. Provide brand guidelines directly in this conversation
@@ -152,7 +183,7 @@ The extracted brand instructions typically include:
 
 | Error | Response |
 |---|---|
-| `search_brands` unavailable | "Brand search is unavailable. Please provide your brand name or guidelines directly." |
+| `search_media_cms_channels` unavailable | "Brand search is unavailable. Please provide your brand name or guidelines directly." |
 | `get_brand_instructions` unavailable | "Cannot retrieve brand instructions. Please share your brand guidelines in this conversation and I'll apply them manually." |
 | Org lacks Vibes branding | "CMS branding is not enabled for this org. Contact your admin to enable the Agentforce Vibes branding feature." |
 | Permission denied | "You don't have permission to access CMS brands. Ensure you have Managed Content Authoring permission." |

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

@@ -15,7 +15,7 @@ Lightning Web Components development skill with PICKLES architecture methodology
 
 ### 1. Invoke the skill
 
-```
+```yaml
 Skill: experience-lwc-generate
 Request: "Create a data table component for Account records"
 ```
@@ -39,7 +39,7 @@ The skill generates:
 
 ## PICKLES Framework
 
-```
+```text
 P → Prototype    │ Validate ideas with wireframes & mock data
 I → Integrate    │ Choose data source (LDS, Apex, GraphQL, API)
 C → Composition  │ Structure component hierarchy & communication
@@ -80,6 +80,7 @@ S → Security     │ Enforce permissions, FLS, and data protection
 | generating-metadata | Create Lightning Message Channels |
 | platform-metadata-deploy | Deploy component to org |
 
+
 ## Spring '26 Features (API 66.0)
 
 - **lwc:on directive**: Dynamic event binding from JavaScript

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

@@ -7,7 +7,7 @@ This guide covers real-time notification patterns for Lightning Web Components u
 
 ## Overview
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────┐
 │                    ASYNC NOTIFICATION ARCHITECTURE                       │
 ├─────────────────────────────────────────────────────────────────────────┤

package/skills/experience-lwc-generate/references/component-patterns.md

@@ -154,7 +154,7 @@ LWC can interact with Apex in two ways: **@wire** (reactive/declarative) and **i
 
 #### Quick Comparison
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────────────┐
 │                    WIRE vs IMPERATIVE APEX CALLS                                     │
 ├──────────────────┬──────────────────────────────┬────────────────────────────────────┤
@@ -254,7 +254,7 @@ export default class ImperativeExample extends LightningElement {
 
 #### Decision Tree
 
-```
+```text
                     ┌─────────────────────────────┐
                     │   Need to modify data?      │
                     │   (Insert/Update/Delete)    │
@@ -955,7 +955,7 @@ export default class AccountList extends LightningElement {
 
 When two child components need to communicate but share the same parent, use the **parent as middleware**. This is the recommended pattern for master-detail UIs.
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────┐
 │                    SIBLING COMMUNICATION FLOW                       │
 ├─────────────────────────────────────────────────────────────────────┤

package/skills/experience-lwc-generate/references/flow-integration-guide.md

@@ -7,7 +7,7 @@ This guide covers building Lightning Web Components for use in Salesforce Flow S
 
 ## Overview
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────┐
 │                     FLOW ↔ LWC COMMUNICATION                        │
 ├─────────────────────────────────────────────────────────────────────┤

package/skills/experience-lwc-generate/references/lwc-best-practices.md

@@ -9,7 +9,7 @@ This guide provides comprehensive best practices for building production-ready L
 
 The PICKLES Framework provides a structured approach to LWC architecture. Use it as a checklist during component design and implementation.
 
-```
+```text
 🥒 P - Prototype    → Validate ideas with wireframes & mock data
 🥒 I - Integrate    → Choose data source (LDS, Apex, GraphQL)
 🥒 C - Composition  → Structure component hierarchy & communication
@@ -29,7 +29,7 @@ The PICKLES Framework provides a structured approach to LWC architecture. Use it
 
 Each component should do one thing well.
 
-```
+```text
 ✅ GOOD: accountCard, accountList, accountForm (separate components)
 ❌ BAD: accountManager (does display, list, and form in one)
 ```
@@ -52,7 +52,7 @@ Build complex UIs by composing simple components.
 
 Data flows down (props), events bubble up.
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────┐
 │                    DATA FLOW PATTERN                             │
 ├─────────────────────────────────────────────────────────────────┤
@@ -268,7 +268,7 @@ this.dispatchEvent(new CustomEvent('change', {
 
 ### Event Naming Conventions
 
-```
+```text
 ✅ GOOD                    ❌ BAD
 ────────────────────────   ────────────────────────
 onselect                   onSelectItem

package/skills/experience-lwc-generate/references/scoring-and-testing.md

@@ -16,7 +16,7 @@
 | **PICKLES Compliance** | 25 | Architecture methodology adherence (optional) |
 
 **Scoring Thresholds**:
-```
+```text
 ⭐⭐⭐⭐⭐ 150-165 pts → Production-ready, full SLDS 2 + Dark Mode
 ⭐⭐⭐⭐   125-149 pts → Good component, minor styling issues
 ⭐⭐⭐     100-124 pts → Functional, needs SLDS cleanup

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

@@ -11,7 +11,7 @@
 
 LWC state management has evolved beyond simple reactive properties. This guide covers modern patterns for managing complex state across components, including the `@lwc/state` library and Salesforce Platform State Managers.
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │                    STATE MANAGEMENT SPECTRUM                                 │
 ├─────────────────────────────────────────────────────────────────────────────┤
@@ -588,7 +588,7 @@ disconnectedCallback() {
 
 ## Best Practices Summary
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │                    STATE MANAGEMENT BEST PRACTICES                           │
 ├─────────────────────────────────────────────────────────────────────────────┤

package/skills/experience-lwc-generate/references/triangle-pattern.md

@@ -7,7 +7,7 @@ The **Triangle Architecture** is a foundational Salesforce pattern where Flow, L
 
 ## Architecture Overview
 
-```
+```text
                          ┌─────────────────────────────────────┐
                          │              FLOW                   │
                          │         (Orchestrator)              │
@@ -54,7 +54,7 @@ The **Triangle Architecture** is a foundational Salesforce pattern where Flow, L
 
 **Use Case**: Custom UI component for user selection within a guided Flow.
 
-```
+```text
 ┌─────────┐     @api (in)      ┌─────────┐
 │  FLOW   │ ────────────────▶  │   LWC   │
 │ Screen  │                    │  Screen │
@@ -320,7 +320,7 @@ describe('c-record-selector', () => {
 
 When deploying integrated triangle solutions:
 
-```
+```text
 1. APEX CLASSES
    └── @AuraEnabled controllers (LWC depends on these)
 

package/skills/experience-lwc-generate/scripts/post-tool-validate.py

@@ -1,6 +1,6 @@
 #!/usr/bin/env python3
 """
-Post-Tool Validation Hook for generating-lwc-components plugin.
+Post-Tool Validation Hook for experience-lwc-generate plugin.
 
 This hook runs AFTER Write or Edit tool completes and provides SLDS 2
 validation feedback for LWC files (*.html, *.css, *.js).
@@ -38,7 +38,7 @@ for _ca_path in _CODE_ANALYZER_CANDIDATES:
         break
 
 # Also add shared dir for other shared modules
-PLUGIN_ROOT = os.path.dirname(os.path.dirname(SCRIPT_DIR))  # generating-lwc-components/
+PLUGIN_ROOT = os.path.dirname(os.path.dirname(SCRIPT_DIR))  # experience-lwc-generate/
 SKILLS_ROOT = os.path.dirname(PLUGIN_ROOT)
 SHARED_DIR = os.path.join(SKILLS_ROOT, "shared")
 if os.path.isdir(SHARED_DIR):

package/skills/experience-lwc-generate/scripts/template_validator.py

@@ -282,7 +282,7 @@ def format_output(results: Dict) -> str:
         output_parts.append(f"   ... and {remaining} more issues")
 
     output_parts.append("─" * 50)
-    output_parts.append("📚 See: generating-lwc-components/references/template-anti-patterns.md")
+    output_parts.append("📚 See: experience-lwc-generate/references/template-anti-patterns.md")
 
     return "\n".join(output_parts)
 

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

@@ -19,7 +19,7 @@
 
 ## Quick Start
 
-```
+```text
 # Generate an OAuth diagram
 "Create a JWT Bearer OAuth flow diagram"
 
@@ -85,7 +85,7 @@ sequenceDiagram
 ```
 
 ### ASCII Fallback
-```
+```text
 ┌───────────────┐     ┌───────────────┐
 │    Server     │     │   Salesforce  │
 └───────┬───────┘     └───────┬───────┘

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

@@ -1,6 +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 wants PNG/SVG image output (use external-diagram-visual-generate), or asks about non-Salesforce systems."
+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:
   version: "1.0"
@@ -20,7 +20,6 @@ Use `external-diagram-mermaid-generate` when the user wants:
 - diagrams that can live directly in docs, READMEs, or issues
 
 ### Out of Scope — Delegate elsewhere when the user wants:
-- rendered PNG/SVG images or polished mockups → [external-diagram-visual-generate](../external-diagram-visual-generate/SKILL.md)
 - non-Salesforce systems only → use a more general diagramming skill
 - object discovery before an ERD → [platform-custom-object-generate](../platform-custom-object-generate/SKILL.md) or [platform-custom-field-generate](../platform-custom-field-generate/SKILL.md)
 
@@ -125,7 +124,6 @@ Call out the key relationships, flow direction, and any assumptions.
 | Need | Delegate to | Reason |
 |---|---|---|
 | real object / field definitions | [platform-custom-object-generate](../platform-custom-object-generate/SKILL.md) / [platform-custom-field-generate](../platform-custom-field-generate/SKILL.md) | grounded ERD generation |
-| rendered diagram / image output | [external-diagram-visual-generate](../external-diagram-visual-generate/SKILL.md) | visual polish beyond Mermaid |
 | connected-app auth setup context | [integration-connectivity-connected-app-configure](../integration-connectivity-connected-app-configure/SKILL.md) | accurate OAuth flows |
 | Agentforce logic visualization | [agentforce-generate](../agentforce-generate/SKILL.md) | source-of-truth behavior details |
 | Flow behavior diagrams | [automation-flow-generate](../automation-flow-generate/SKILL.md) | actual Flow logic grounding |

package/skills/external-diagram-mermaid-generate/assets/agentforce/agent-flow.md

@@ -202,7 +202,7 @@ flowchart TD
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │                        🤖 SERVICE AGENT STRUCTURE                           │
 └─────────────────────────────────────────────────────────────────────────────┘
@@ -283,17 +283,17 @@ flowchart TD
 ## Conversation Flow Patterns
 
 ### 1. Linear Flow
-```
+```text
 Start → Topic → Action → Response → End
 ```
 
 ### 2. Branching Flow
-```
+```text
 Start → Classify → [Topic A | Topic B | Escalate]
 ```
 
 ### 3. Loop Back
-```
+```text
 Start → Topic → Action → Validate → [Success | Retry]
 ```