@salesforce/afv-skills 1.29.0 → 1.31.0

package/skills/omnistudio-flexcard-generate/references/best-practices.md

@@ -8,7 +8,7 @@
 
 Use for displaying summary information about a single record. Group related fields into logical sections.
 
-```
+```text
 ┌──────────────────────────────────┐
 │  Header: Record Name             │
 ├──────────────────────────────────┤
@@ -37,7 +37,7 @@ Use for displaying summary information about a single record. Group related fiel
 
 Use for displaying a collection of related records. Each card in the list renders from one item in the data source array.
 
-```
+```text
 ┌──────────────────────────────────┐
 │  Card 1: Record A                │
 │  Field 1 | Field 2 | [Action]   │
@@ -62,7 +62,7 @@ Use for displaying a collection of related records. Each card in the list render
 
 Use when a single record has multiple contexts worth displaying. Each tab represents a different state with its own data source or field set.
 
-```
+```text
 ┌──────────────────────────────────┐
 │  [Tab 1: Overview] [Tab 2: History] [Tab 3: Related] │
 ├──────────────────────────────────┤
@@ -83,7 +83,7 @@ Use when a single record has multiple contexts worth displaying. Each tab repres
 
 Use for progressive disclosure: show a summary, then expand for details on demand.
 
-```
+```text
 ┌──────────────────────────────────┐
 │  Summary: Key Fields  [▼ More]   │
 └──────────────────────────────────┘
@@ -173,7 +173,7 @@ Use for progressive disclosure: show a summary, then expand for details on deman
 
 ### Color Usage
 
-```
+```yaml
 Correct:  Use SLDS token  →  var(--slds-g-color-brand-base-50)
 Wrong:    Hardcoded hex    →  #0176d3
 Wrong:    Hardcoded rgb    →  rgb(1, 118, 211)
@@ -272,7 +272,7 @@ Wrong:    Hardcoded rgb    →  rgb(1, 118, 211)
 
 ### Data Flow Pattern
 
-```
+```text
 Parent FlexCard
   ├── Data Source: IP_GetAccountSummary
   │     └── Passes {AccountId} to child

package/skills/omnistudio-flexcard-generate/references/data-binding-guide.md

@@ -34,7 +34,7 @@ The most common FlexCard data source is an Integration Procedure. The data sourc
 
 The `ipMethod` value combines the IP's Type and SubType fields:
 
-```
+```text
 IP Type:    "Account"
 IP SubType: "GetSummary"
 ipMethod:   "Account_GetSummary"
@@ -72,7 +72,7 @@ Input parameters pass context from the FlexCard's hosting environment into the I
 
 Map IP response fields to FlexCard display elements using curly-brace merge syntax:
 
-```
+```text
 IP Response JSON:                    FlexCard Merge Field:
 ─────────────────                    ─────────────────────
 { "Name": "Acme Corp" }        →    {Name}
@@ -84,7 +84,7 @@ IP Response JSON:                    FlexCard Merge Field:
 
 Access nested objects in the IP response using dot notation:
 
-```
+```text
 IP Response JSON:                         FlexCard Merge Field:
 ─────────────────                         ─────────────────────
 {                                    →    {Account.Name}
@@ -113,7 +113,7 @@ For card list layouts, set `resultListPath` to the array node. Each card in the
 }
 ```
 
-```
+```text
 IP Response:                              Each Card Renders:
 ────────────                              ──────────────────
 {                                         Card 1: {Name} → "Alice"
@@ -145,7 +145,7 @@ Apply formatting to merge fields for display:
 
 Show or hide individual fields based on a data value:
 
-```
+```yaml
 Condition:  {Status} == "Active"
 Action:     Show the "Renewal Date" field
 
@@ -183,7 +183,7 @@ FlexCards support multiple states. Each state can have visibility conditions:
 
 Apply different styles based on data values:
 
-```
+```text
 If {Status} == "Active"    → Green badge (slds-badge slds-theme_success)
 If {Status} == "Expired"   → Red badge (slds-badge slds-theme_error)
 If {Status} == "Pending"   → Yellow badge (slds-badge slds-theme_warning)
@@ -203,7 +203,7 @@ Use SLDS theme classes rather than inline color styles to maintain dark mode com
 
 ### Configuration Pattern
 
-```
+```yaml
 FlexCard: AccountOverview
 ├── Data Source 1: "Account_GetSummary"
 │     Input: { "recordId": "{recordId}" }
@@ -222,7 +222,7 @@ FlexCard: AccountOverview
 
 When a card has multiple data sources, reference fields using the data source name prefix:
 
-```
+```text
 Single data source:     {Name}
 Multiple data sources:  {ds1.Name}  or  {accountSummary.Name}
 ```
@@ -261,7 +261,7 @@ Multiple data sources:  {ds1.Name}  or  {accountSummary.Name}
 
 Configure an explicit error state rather than letting the card fail silently:
 
-```
+```text
 ┌──────────────────────────────────┐
 │  ⚠ Unable to load account data   │
 │                                  │

package/skills/omnistudio-integration-procedure-generate/SKILL.md

@@ -27,7 +27,7 @@ Expert OmniStudio Integration Procedure (IP) builder with deep knowledge of serv
 
 ## Quick Reference
 
-**Scoring**: 110 points across 6 categories. **Thresholds**: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ <67 (Block - fix required)
+**Scoring**: 110 points across 6 categories. **Thresholds**: [PASS] 90+ (Deploy) | [REVIEW] 67-89 (Review) | [BLOCK] <67 (Block - fix required)
 
 ---
 
@@ -272,3 +272,11 @@ Deliverables produced by this skill:
 | `references/best-practices.md` | Phase 2-5 — Design patterns: element composition, error handling, caching, parallel execution, and security guidance |
 | `references/element-types.md` | Phase 2 — Element selection: read before configuring PropertySetConfig for any element type |
 | `scripts/cli-commands.sh` | Phase 1 & 4 — CLI queries and deploy/retrieve commands; adapt by replacing `<Name>` and `<org>` placeholders |
+
+---
+
+## Pre-Delivery Checklist
+
+- [ ] Data Mappers exist and are deployed before IP references them
+- [ ] `IsIntegrationProcedure = true` set when creating via Data API
+- [ ] IP activated before any OmniScript/FlexCard invokes it

package/skills/omnistudio-integration-procedure-generate/references/element-types.md

@@ -465,12 +465,12 @@ Elements inside a Loop Block execute once per iteration. The current item is acc
 ### Example Pattern: Collect and Bulk Process
 
 Instead of:
-```
+```text
 Loop -> DataRaptor Load (per item)  // BAD: N DML operations
 ```
 
 Use:
-```
+```text
 Loop -> Set Values (collect items into array)
 DataRaptor Load (entire array)  // GOOD: 1 DML operation
 ```
@@ -501,7 +501,7 @@ Set Values elements define key-value mappings:
 
 ### Example: Response Assembly
 
-```
+```text
 Set Values: "BuildResponse"
   out_success = true
   out_accountId = %GetAccount:Id%

package/skills/omnistudio-omniscript-generate/SKILL.md

@@ -11,7 +11,7 @@ Expert OmniStudio OmniScript builder for declarative, step-based guided digital
 
 ## Quick Reference
 
-**Scoring**: 120 points across 6 categories. **Thresholds**: ✅ 90+ (Deploy) | ⚠️ 67-89 (Review) | ❌ <67 (Block - fix required)
+**Scoring**: 120 points across 6 categories. **Thresholds**: [PASS] 90+ (Deploy) | [REVIEW] 67-89 (Review) | [BLOCK] <67 (Block - fix required)
 
 ---
 
@@ -168,7 +168,7 @@ Run `scripts/check-duplicate-omniscript.sh <Type> <SubType> <Language> <org>` to
 - **WARN**: Steps with no elements, input elements without validation, missing error handling on actions, unused data paths, deeply nested elements (>4 levels)
 
 **Validation Report Format** (6-Category Scoring 0-120):
-```
+```yaml
 Score: 102/120 ---- Very Good
 -- Design & Structure: 22/25 (88%)
 -- Data Integration: 18/20 (90%)

package/skills/omnistudio-omniscript-generate/references/best-practices.md

@@ -41,7 +41,7 @@ The default and most common pattern. Each Step represents a phase of the process
 - The final Step should be a review/confirmation screen
 
 **Example structure:**
-```
+```text
 Step 1: "Account Selection"    -> Type Ahead (account search) + DataRaptor Extract (prefill)
 Step 2: "Service Details"      -> Select, Text, Date inputs for the request
 Step 3: "Attachments"          -> File upload + Text Area for notes

package/skills/omnistudio-omniscript-generate/scripts/check-duplicate-omniscript.sh

@@ -8,6 +8,14 @@ SUBTYPE="${2:?}"
 LANGUAGE="${3:?}"
 ORG="${4:?}"
 
+# Validate inputs to prevent SOQL injection
+for var in "$TYPE" "$SUBTYPE" "$LANGUAGE"; do
+  if [[ ! "$var" =~ ^[a-zA-Z0-9_\ ]+$ ]]; then
+    echo "ERROR: Invalid input '$var'. Only alphanumeric, underscores, and spaces allowed." >&2
+    exit 1
+  fi
+done
+
 sf data query \
   -q "SELECT Id,Name,Type,SubType,Language,IsActive,VersionNumber FROM OmniProcess WHERE Type='${TYPE}' AND SubType='${SUBTYPE}' AND Language='${LANGUAGE}' AND OmniProcessType='OmniScript' LIMIT 10" \
   -o "${ORG}"

package/skills/omnistudio-omniscript-generate/scripts/deploy-omniscript.sh

@@ -9,6 +9,14 @@ TYPE="${2:?}"
 SUBTYPE="${3:?}"
 ORG="${4:?}"
 
+# Validate inputs to prevent SOQL injection
+for var in "$TYPE" "$SUBTYPE"; do
+  if [[ ! "$var" =~ ^[a-zA-Z0-9_\ ]+$ ]]; then
+    echo "ERROR: Invalid input '$var'. Only alphanumeric, underscores, and spaces allowed." >&2
+    exit 1
+  fi
+done
+
 echo "Step 1: Verify prerequisites — check org auth"
 sf org display -o "${ORG}" || { echo "ERROR: Org '${ORG}' is not authenticated. Run: sf org login web --alias ${ORG}"; exit 1; }
 

package/skills/platform-apex-logs-debug/README.md

@@ -16,7 +16,7 @@ Salesforce debugging and troubleshooting skill with log analysis, governor limit
 
 ### 1. Invoke the skill
 
-```
+```text
 Skill: platform-apex-logs-debug
 Request: "Analyze debug logs for AccountTrigger performance issues in org dev"
 ```
@@ -58,7 +58,7 @@ sf apex tail log --target-org [alias] --color
 
 | Related Skill | When to Use |
 |---------------|-------------|
-| sf-apex | Fix identified Apex issues |
+| platform-apex-generate | Fix identified Apex issues |
 | platform-soql-query | Optimize slow SOQL queries |
 | platform-apex-test-run | Re-run tests after fixes |
 

package/skills/platform-apex-logs-debug/references/cli-commands.md

@@ -297,7 +297,7 @@ echo "Deleted $COUNT logs"
 Logs over 2MB are truncated. Solutions:
 
 1. **Reduce debug level:**
-   ```
+   ```text
    ApexCode: DEBUG → INFO
    ApexProfiling: FINEST → FINE
    ```
@@ -342,7 +342,7 @@ sf apex list log --target-org my-org --json | \
 ```
 
 The hook will output analysis like:
-```
+```text
 ============================================================
 🔍 DEBUG LOG ANALYSIS
 ============================================================

package/skills/platform-apex-logs-debug/references/debug-log-reference.md

@@ -4,12 +4,12 @@
 ## Log Structure
 
 Debug logs follow a consistent format:
-```
+```text
 TIMESTAMP|EVENT_IDENTIFIER|[PARAMS]|DETAILS
 ```
 
 Example:
-```
+```text
 14:32:54.123 (123456789)|SOQL_EXECUTE_BEGIN|[45]|SELECT Id FROM Account
 ```
 
@@ -34,7 +34,7 @@ Example:
 | `SOQL_EXECUTE_END` | Query ends | Rows returned |
 
 **Analysis Pattern:**
-```
+```text
 |SOQL_EXECUTE_BEGIN|[45]|SELECT Id, Name FROM Account WHERE...
 |SOQL_EXECUTE_END|[3 rows]
 ```
@@ -54,7 +54,7 @@ Example:
 | `DML_END` | DML ends | Rows affected |
 
 **Analysis Pattern:**
-```
+```text
 |DML_BEGIN|[78]|Op:Insert|Type:Contact|
 |DML_END|[200 rows]
 ```
@@ -74,7 +74,7 @@ Example:
 | `CUMULATIVE_LIMIT_USAGE` | End of transaction | Summary of all limits |
 
 **Example:**
-```
+```text
 |LIMIT_USAGE|SOQL_QUERIES|25|100
 |LIMIT_USAGE|DML_STATEMENTS|45|150
 |LIMIT_USAGE|CPU_TIME|3500|10000
@@ -89,7 +89,7 @@ Example:
 | `FATAL_ERROR` | Unhandled exception | Full stack trace |
 
 **Analysis Pattern:**
-```
+```text
 |EXCEPTION_THROWN|[67]|System.NullPointerException|Attempt to de-reference a null object
 |FATAL_ERROR|System.NullPointerException: Attempt to de-reference a null object
   Class.ContactService.processContacts: line 67, column 1
@@ -116,7 +116,7 @@ Example:
 | `ITERATION_END` | Iteration ends | |
 
 **Detection Pattern for SOQL in Loop:**
-```
+```text
 |LOOP_BEGIN|
   |ITERATION_BEGIN|
     |SOQL_EXECUTE_BEGIN|[45]|SELECT...
@@ -137,7 +137,7 @@ Example:
 | `CALLOUT_EXTERNAL_EXIT` | HTTP callout ends | Status code, Duration |
 
 **Example:**
-```
+```text
 |CALLOUT_EXTERNAL_ENTRY|[89]|https://api.example.com/endpoint
 |CALLOUT_EXTERNAL_EXIT|[200]|[1500ms]
 ```
@@ -182,7 +182,7 @@ Example:
 ### Recommended Debug Level Settings
 
 **For Performance Issues:**
-```
+```text
 Apex Code: FINE
 Apex Profiling: FINEST
 Database: FINE
@@ -190,7 +190,7 @@ System: DEBUG
 ```
 
 **For Exception Debugging:**
-```
+```text
 Apex Code: DEBUG
 Apex Profiling: FINE
 Database: INFO
@@ -198,7 +198,7 @@ System: DEBUG
 ```
 
 **For Callout Issues:**
-```
+```text
 Apex Code: DEBUG
 Callout: FINEST
 System: DEBUG
@@ -243,7 +243,7 @@ System: DEBUG
 
 ### Pattern 1: SOQL in Loop
 
-```
+```text
 |LOOP_BEGIN|
 |ITERATION_BEGIN|
 |SOQL_EXECUTE_BEGIN|[45]|SELECT Id FROM Contact WHERE AccountId = '001xxx'
@@ -260,7 +260,7 @@ System: DEBUG
 
 ### Pattern 2: DML in Loop
 
-```
+```text
 |LOOP_BEGIN|
 |ITERATION_BEGIN|
 |DML_BEGIN|[78]|Op:Insert|Type:Contact|
@@ -273,21 +273,21 @@ System: DEBUG
 
 ### Pattern 3: Non-Selective Query
 
-```
+```text
 |SOQL_EXECUTE_BEGIN|[23]|SELECT Id FROM Lead WHERE Status = 'Open'
 |SOQL_EXECUTE_END|[250000 rows]  ← Large result set!
 ```
 
 ### Pattern 4: CPU Limit Approaching
 
-```
+```text
 |CUMULATIVE_LIMIT_USAGE|
 |CPU_TIME|9500|10000  ← 95% used!
 ```
 
 ### Pattern 5: Null Pointer Exception
 
-```
+```text
 |SOQL_EXECUTE_BEGIN|[45]|SELECT Id FROM Account WHERE Id = '001xxx'
 |SOQL_EXECUTE_END|[0 rows]  ← No results!
 |METHOD_EXIT|getAccount|

package/skills/platform-apex-logs-debug/references/log-analysis-tools.md

@@ -11,7 +11,7 @@ The **Apex Log Analyzer** is a free VS Code extension that provides visual analy
 
 ### Installation
 
-```
+```text
 1. Open VS Code
 2. Go to Extensions (Ctrl+Shift+X / Cmd+Shift+X)
 3. Search "Apex Log Analyzer"
@@ -53,7 +53,7 @@ code --install-extension FinancialForce.lana
 
 ### Reading Flame Charts
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │ FLAME CHART INTERPRETATION                                   │
 ├─────────────────────────────────────────────────────────────┤

package/skills/platform-apex-test-run/README.md

@@ -15,7 +15,7 @@ Comprehensive Salesforce testing skill with test execution, code coverage analys
 
 ### 1. Invoke the skill
 
-```
+```yaml
 Skill: platform-apex-test-run
 Request: "Run all tests and show coverage report for org dev"
 ```

package/skills/platform-apex-test-run/references/test-fix-loop.md

@@ -16,7 +16,7 @@ When the agentic loop is enabled, platform-apex-test-run will:
 
 ## Example Agentic Flow
 
-```
+```yaml
 User: "Run tests for AccountService with auto-fix enabled"
 
 Claude:
@@ -44,6 +44,6 @@ Claude:
 
 ## Auto-Fix Command
 
-```
+```text
 Skill(skill="sf-apex", args="Fix failing test [TestClassName].[methodName] - Error: [error message]")
 ```

package/skills/platform-apex-test-run/references/testing-best-practices.md

@@ -7,7 +7,7 @@ This guide covers best practices for writing effective, maintainable Apex tests
 
 ## The Testing Pyramid
 
-```
+```text
                     ╱╲
                    ╱  ╲
                   ╱ E2E╲        Few end-to-end tests
@@ -423,7 +423,7 @@ Fast tests enable continuous integration. Slow tests become barriers to frequent
 
 ### Speed Strategy
 
-```
+```text
 ┌─────────────────────────────────────────────────────────────┐
 │  INTEGRATION TESTS (Few)                                    │
 │  - Real DML, real triggers                                  │
@@ -499,7 +499,7 @@ sf apex get test --test-run-id [id] --code-coverage --result-format json | jq '.
 
 ### Fast Test Checklist
 
-```
+```text
 □ Is there a pure logic portion that can be unit tested?
 □ Can database operations be mocked for edge cases?
 □ Is @TestSetup reused across multiple test methods?

package/skills/platform-custom-field-generate/SKILL.md

@@ -4,6 +4,7 @@ description: "Use this skill when users need to create, generate, or validate Sa
 metadata:
   version: "1.0"
   minApiVersion: "51.0"
+  relatedSkills: ["platform-value-set-generate", "platform-validation-rule-generate"]
 ---
 
 # Salesforce Custom Field Generator and Validator
@@ -20,7 +21,7 @@ Every generated field must include these tags:
 
 | Attribute | Requirement | Notes |
 |-----------|-------------|-------|
-| `<fullName>` | Required | **Field** name only: derive from `<label>` — capitalize each word, replace spaces with `_`, append `__c`. Must start with a letter. E.g., label `Total Contract Value` → `Total_Contract_Value__c`. ⚠️ This rule is for the FIELD name. **Picklist VALUE `<fullName>` is different — keep it exactly as the user spelled it, spaces and all, no `__c`** (e.g. `Closed Won`, NOT `Closed_Won`). See [`references/advanced-picklists.md`](references/advanced-picklists.md) (ref §3). |
+| `<fullName>` | Required | **Field** name only: derive from `<label>` — capitalize each word, replace spaces with `_`, append `__c`. Must start with a letter. E.g., label `Total Contract Value` → `Total_Contract_Value__c`. This rule is for the FIELD name. **Picklist VALUE `<fullName>` is different — keep it exactly as the user spelled it, spaces and all, no `__c`** (e.g. `Closed Won`, NOT `Closed_Won`). See [`references/advanced-picklists.md`](references/advanced-picklists.md) (ref §3). |
 | `<label>` | Required | The UI name (Title Case) |
 | `<description>` | Always include | Explain the business reason *why* this field exists. |
 | `<inlineHelpText>` | Always include | Actionable end-user guidance that adds value beyond the label (e.g., "Enter the value in USD including tax", not "The amount"). |
@@ -49,7 +50,7 @@ To ensure deployment success, follow these mathematical constraints:
 
 ### The "Fixed 255" Rule
 
-**TextArea: always include `<length>255</length>` exactly** — this literal value is required by the Metadata API and **omitting it fails deployment**, even though the UI exposes no length control. Unlike every other type where `length` is a value you calculate, TextArea's is a fixed constant.
+**TextArea: do NOT include `<length>`** — the Metadata API fixes the length at 255 implicitly and **rejects an explicit `<length>` value** with "Can not specify 'length' for a CustomField of type TextArea". Omit `<length>` entirely; the field only needs `<fullName>`, `<label>`, and `<type>TextArea</type>`.
 
 ### Visible Lines
 
@@ -76,7 +77,7 @@ Mandatory for Long/Rich text and Multi-select picklists to control UI height.
 | Phone | `Phone` | Standardizes phone number formatting |
 | Picklist | `Picklist` | `valueSet` containing EITHER `valueSetDefinition` (inline) OR `valueSetName` (reference); `restricted` (see "Picklist `restricted` default" below; advanced cases in §3.4) |
 | Text | `Text` | `length` (Max 255) |
-| Text Area | `TextArea` | `<length>255</length>` |
+| Text Area | `TextArea` | None — do NOT include `<length>`; the API fixes length at 255 implicitly |
 | Text (Long) | `LongTextArea` | `length`, `visibleLines` (default 3) |
 | Text (Rich) | `Html` | `length`, `visibleLines` (default 25) |
 | Time | `Time` | Stores time only (no date) |
@@ -112,7 +113,7 @@ Mandatory for Long/Rich text and Multi-select picklists to control UI height.
 
 ### 3.4 Advanced Picklists
 
-The inline `<valueSetDefinition>` above is the simple case. Full rules and worked ✅/❌
+The inline `<valueSetDefinition>` above is the simple case. Full rules and worked correct/incorrect
 examples for everything below are in
 [`references/advanced-picklists.md`](references/advanced-picklists.md) — load it for any
 non-trivial picklist. Section numbers in parentheses below (e.g. "ref §1") point to that
@@ -166,12 +167,12 @@ Master-Detail fields have **strict attribute restrictions** that differ from Loo
 
 | Attribute | Master-Detail | Lookup |
 |-----------|---------------|--------|
-| `<required>` | ❌ FORBIDDEN | ✅ Optional |
-| `<deleteConstraint>` | ❌ FORBIDDEN (always CASCADE) | ✅ Required (`SetNull`, `Restrict`, `Cascade`) |
-| `<lookupFilter>` | ❌ FORBIDDEN | ✅ Optional |
-| `<relationshipOrder>` | ✅ Required (0 or 1) | ❌ Not applicable |
-| `<reparentableMasterDetail>` | ✅ Optional | ❌ Not applicable |
-| `<writeRequiresMasterRead>` | ✅ Optional | ❌ Not applicable |
+| `<required>` | FORBIDDEN | Optional |
+| `<deleteConstraint>` | FORBIDDEN (always CASCADE) | Required (`SetNull`, `Restrict`, `Cascade`) |
+| `<lookupFilter>` | FORBIDDEN | Optional |
+| `<relationshipOrder>` | Required (0 or 1) | Not applicable |
+| `<reparentableMasterDetail>` | Optional | Not applicable |
+| `<writeRequiresMasterRead>` | Optional | Not applicable |
 
 ### INCORRECT — Master-Detail with forbidden attributes:
 
@@ -451,7 +452,7 @@ Before generating CustomField XML, verify:
 - [ ] Is `precision ≤ 18`?
 
 ### Text Area Checks
-- [ ] For TextArea: Is `<length>255</length>` explicitly included?
+- [ ] For TextArea: Is `<length>` **omitted**? (The API rejects an explicit `<length>` value on TextArea fields.)
 - [ ] For LongTextArea/Html: Is `<visibleLines>` set?
 
 ### Relationship Limit Checks