@salesforce/afv-skills 1.28.0 → 1.30.0

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

package/skills/external-diagram-mermaid-generate/assets/architecture/system-landscape.md

@@ -268,7 +268,7 @@ flowchart TB
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │                              SYSTEM LANDSCAPE                               │
 └─────────────────────────────────────────────────────────────────────────────┘

package/skills/external-diagram-mermaid-generate/assets/datamodel/b2b-commerce-erd.md

@@ -107,7 +107,7 @@ flowchart LR
 ## Key Concepts
 
 ### B2B Commerce Flow
-```
+```text
 WebStore → ProductCatalog → Product2
     ↓           ↓
 BuyerAccount → WebCart → CartItem → Order
@@ -123,7 +123,7 @@ BuyerGroup → Entitlements (What they can see/buy)
 | BuyerGroup | Pricing/entitlement grouping |
 
 ### Entitlement Model
-```
+```text
 CommerceEntitlementPolicy
     ├── CommerceEntitlementProduct (What products)
     └── CommerceEntitlementBuyerGroup (Who can see)
@@ -223,7 +223,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  B2B COMMERCE DATA MODEL (L→R)                                               │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/campaigns-erd.md

@@ -130,7 +130,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  CAMPAIGNS DATA MODEL (L→R)                                                  │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/consent-erd.md

@@ -114,7 +114,7 @@ flowchart LR
 Each contact point links to an Individual.
 
 ### Consent Model
-```
+```text
 DataUsePurpose  →  ContactPointConsent  ←  ContactPoint
 (e.g., Marketing)        (Opt-In/Out)        (Email/Phone)
 ```
@@ -179,7 +179,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  CONSENT DATA MODEL (GDPR/PRIVACY) (L→R)                                     │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/files-erd.md

@@ -86,7 +86,7 @@ flowchart LR
 ## Key Concepts
 
 ### Content Architecture
-```
+```text
 ContentDocument (Container)
     ├── ContentVersion (Current + History)
     ├── ContentDocumentLink (Sharing to Records)
@@ -177,7 +177,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  SALESFORCE FILES DATA MODEL (L→R)                                           │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/forecasting-erd.md

@@ -114,7 +114,7 @@ flowchart LR
 | Omitted | Excluded from forecast |
 
 ### Forecast Rollup Hierarchy
-```
+```text
 CEO
  └── VP Sales
       ├── Regional Manager 1
@@ -182,7 +182,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  COLLABORATIVE FORECASTS DATA MODEL (L→R)                                    │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/fsl-erd.md

@@ -127,7 +127,7 @@ flowchart LR
 ## Key Concepts
 
 ### FSL Object Hierarchy
-```
+```text
 Case/Asset → WorkOrder → WorkOrderLineItem → ServiceAppointment
                    ↓              ↓                    ↓
               ProductRequired  ProductConsumed   AssignedResource
@@ -245,7 +245,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  FIELD SERVICE LIGHTNING DATA MODEL (L→R)                                    │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/party-model-erd.md

@@ -157,7 +157,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  PARTY MODEL (INDUSTRY CLOUD) DATA MODEL (L→R)                              │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/quote-order-erd.md

@@ -102,7 +102,7 @@ flowchart LR
 ## Key Concepts
 
 ### Quote-to-Cash Flow
-```
+```text
 Opportunity → Quote → Order → Invoice → Payment
       ↓          ↓        ↓
     OLI        QLI   OrderItem
@@ -121,7 +121,7 @@ Opportunity → Quote → Order → Invoice → Payment
 | Reduction Orders | Negative quantity adjustments |
 
 ### Pricebook Structure
-```
+```text
 Pricebook2 (Standard + Custom)
     ↓
 PricebookEntry (Product + Price per Pricebook)
@@ -176,7 +176,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  QUOTE & ORDER DATA MODEL (L→R)                                              │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/revenue-cloud-erd.md

@@ -109,7 +109,7 @@ flowchart LR
 | **Dynamic Revenue Orchestration** | Guided selling |
 
 ### Product Hierarchy
-```
+```text
 ProductCatalog
     └── ProductCategory (Hierarchy)
             └── Product2
@@ -244,7 +244,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  REVENUE CLOUD DATA MODEL (L→R)                                              │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/sales-cloud-erd.md

@@ -116,7 +116,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  SALES CLOUD DATA MODEL (L→R)                                               │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>), -.-> = converts       │

package/skills/external-diagram-mermaid-generate/assets/datamodel/salesforce-erd.md

@@ -94,7 +94,7 @@ flowchart LR
 
 ## ASCII Fallback Template
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  DATA MODEL (L→R)                                                           │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/scheduler-erd.md

@@ -112,7 +112,7 @@ flowchart LR
 ## Key Concepts
 
 ### Scheduling Flow
-```
+```text
 Customer (Contact) → WorkType → ServiceAppointment ← ServiceResource
                                         ↓
                                ServiceTerritory
@@ -184,7 +184,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  SALESFORCE SCHEDULER DATA MODEL (L→R)                                       │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │

package/skills/external-diagram-mermaid-generate/assets/datamodel/service-cloud-erd.md

@@ -120,7 +120,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  SERVICE CLOUD DATA MODEL (L→R)                                             │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │
@@ -173,14 +173,14 @@ flowchart LR
 ## Service Cloud Patterns
 
 ### Case Flow
-```
+```text
 Customer → Contact → Case → CaseComment
               ↓
          Entitlement (SLA)
 ```
 
 ### Entitlement Coverage
-```
+```text
 Account → ServiceContract → Entitlement → Case
     └─────────────────────────────────────┘
                   (direct)

package/skills/external-diagram-mermaid-generate/assets/datamodel/territory-management-erd.md

@@ -162,7 +162,7 @@ flowchart LR
 
 ## ASCII Fallback
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────────────────────┐
 │  ENTERPRISE TERRITORY MANAGEMENT DATA MODEL (L→R)                           │
 │  Legend: LK = Lookup (-->), MD = Master-Detail (==>)                        │