@salesforce/afv-skills 1.48.0 → 1.50.0

package/skills/field-service-data-capture-reference-configure/examples/Repeater_with_prepopulation.flow-meta.xml

@@ -0,0 +1,231 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Flow xmlns="http://soap.sforce.com/2006/04/metadata">
+    <areMetricsLoggedToDataCloud>false</areMetricsLoggedToDataCloud>
+    <customProperties>
+        <name>IsLlmTargetable</name>
+        <value>
+            <stringValue>{&quot;value&quot;:&quot;false&quot;}</stringValue>
+        </value>
+    </customProperties>
+    <environments>Offline</environments>
+    <interviewLabel>Repeater with prepopulation (joost) {!$Flow.CurrentDateTime}</interviewLabel>
+    <label>Repeater with prepopulation (joost)</label>
+    <loops>
+        <name>Loop_Through_Repeater</name>
+        <label>Loop Through Repeater</label>
+        <locationX>0</locationX>
+        <locationY>0</locationY>
+        <collectionReference>accountRepeater.AllItems</collectionReference>
+        <iterationOrder>Asc</iterationOrder>
+        <nextValueConnector>
+            <targetReference>Repeater_Output_Screen</targetReference>
+        </nextValueConnector>
+    </loops>
+    <processMetadataValues>
+        <name>BuilderType</name>
+        <value>
+            <stringValue>LightningFlowBuilder</stringValue>
+        </value>
+    </processMetadataValues>
+    <processMetadataValues>
+        <name>CanvasMode</name>
+        <value>
+            <stringValue>AUTO_LAYOUT_CANVAS</stringValue>
+        </value>
+    </processMetadataValues>
+    <processMetadataValues>
+        <name>OriginBuilderType</name>
+        <value>
+            <stringValue>LightningFlowBuilder</stringValue>
+        </value>
+    </processMetadataValues>
+    <processType>DataCaptureFlow</processType>
+    <recordLookups>
+        <name>Get_3_ServiceResources</name>
+        <label>Get 3 Service Resources</label>
+        <locationX>0</locationX>
+        <locationY>0</locationY>
+        <assignNullValuesIfNoRecordsFound>false</assignNullValuesIfNoRecordsFound>
+        <connector>
+            <targetReference>Screen_Repeater</targetReference>
+        </connector>
+        <getFirstRecordOnly>false</getFirstRecordOnly>
+        <limit>
+            <numberValue>3.0</numberValue>
+        </limit>
+        <object>ServiceResource</object>
+        <storeOutputAutomatically>true</storeOutputAutomatically>
+    </recordLookups>
+    <screens>
+        <name>Repeater_Output_Screen</name>
+        <label>Repeater Output Screen</label>
+        <locationX>0</locationX>
+        <locationY>0</locationY>
+        <allowBack>true</allowBack>
+        <allowFinish>true</allowFinish>
+        <allowPause>true</allowPause>
+        <connector>
+            <targetReference>Loop_Through_Repeater</targetReference>
+        </connector>
+        <fields>
+            <name>display_info_2</name>
+            <fieldText>&lt;p&gt;ServiceResource Id:{!Loop_Through_Repeater.UniqueField__Id}&lt;/p&gt;&lt;p&gt;&lt;span style=&quot;background-color: rgb(255, 255, 255);&quot;&gt;Resource Type: {!Loop_Through_Repeater.description.value}&lt;/span&gt;&lt;/p&gt;&lt;p&gt;Name: {!Loop_Through_Repeater.name.value}&lt;/p&gt;</fieldText>
+            <fieldType>DisplayText</fieldType>
+            <styleProperties>
+                <verticalAlignment>
+                    <stringValue>top</stringValue>
+                </verticalAlignment>
+                <width>
+                    <stringValue>12</stringValue>
+                </width>
+            </styleProperties>
+        </fields>
+        <showFooter>true</showFooter>
+        <showHeader>true</showHeader>
+    </screens>
+    <screens>
+        <name>Screen_Repeater</name>
+        <label>Screen Repeater</label>
+        <locationX>0</locationX>
+        <locationY>0</locationY>
+        <allowBack>true</allowBack>
+        <allowFinish>true</allowFinish>
+        <allowPause>true</allowPause>
+        <connector>
+            <targetReference>Loop_Through_Repeater</targetReference>
+        </connector>
+        <fields>
+            <name>accountRepeater</name>
+            <fieldType>Repeater</fieldType>
+            <fields>
+                <name>account_info</name>
+                <fieldText>&lt;p&gt;Id: {!Get_3_ServiceResources[$EachItem].Id}&lt;/p&gt;</fieldText>
+                <fieldType>DisplayText</fieldType>
+                <styleProperties>
+                    <verticalAlignment>
+                        <stringValue>top</stringValue>
+                    </verticalAlignment>
+                    <width>
+                        <stringValue>12</stringValue>
+                    </width>
+                </styleProperties>
+            </fields>
+            <fields>
+                <name>name</name>
+                <extensionName>runtime_service_fieldservice:dcTextInput</extensionName>
+                <fieldType>ComponentInstance</fieldType>
+                <inputParameters>
+                    <name>label</name>
+                    <value>
+                        <stringValue>Name</stringValue>
+                    </value>
+                </inputParameters>
+                <inputParameters>
+                    <name>required</name>
+                    <value>
+                        <booleanValue>false</booleanValue>
+                    </value>
+                </inputParameters>
+                <inputParameters>
+                    <name>value</name>
+                    <value>
+                        <elementReference>Get_3_ServiceResources[$EachItem].Name</elementReference>
+                    </value>
+                </inputParameters>
+                <inputsOnNextNavToAssocScrn>UseStoredValues</inputsOnNextNavToAssocScrn>
+                <isRequired>true</isRequired>
+                <storeOutputAutomatically>true</storeOutputAutomatically>
+                <styleProperties>
+                    <verticalAlignment>
+                        <stringValue>top</stringValue>
+                    </verticalAlignment>
+                    <width>
+                        <stringValue>12</stringValue>
+                    </width>
+                </styleProperties>
+            </fields>
+            <fields>
+                <name>description</name>
+                <extensionName>runtime_service_fieldservice:dcLongText</extensionName>
+                <fieldType>ComponentInstance</fieldType>
+                <inputParameters>
+                    <name>label</name>
+                    <value>
+                        <stringValue>Resource Type</stringValue>
+                    </value>
+                </inputParameters>
+                <inputParameters>
+                    <name>value</name>
+                    <value>
+                        <elementReference>Get_3_ServiceResources[$EachItem].ResourceType</elementReference>
+                    </value>
+                </inputParameters>
+                <inputsOnNextNavToAssocScrn>UseStoredValues</inputsOnNextNavToAssocScrn>
+                <isRequired>true</isRequired>
+                <storeOutputAutomatically>true</storeOutputAutomatically>
+                <styleProperties>
+                    <verticalAlignment>
+                        <stringValue>top</stringValue>
+                    </verticalAlignment>
+                    <width>
+                        <stringValue>12</stringValue>
+                    </width>
+                </styleProperties>
+            </fields>
+            <inputParameters>
+                <name>collection</name>
+                <value>
+                    <elementReference>Get_3_ServiceResources</elementReference>
+                </value>
+            </inputParameters>
+            <isRequired>false</isRequired>
+            <styleProperties>
+                <verticalAlignment>
+                    <stringValue>top</stringValue>
+                </verticalAlignment>
+                <width>
+                    <stringValue>12</stringValue>
+                </width>
+            </styleProperties>
+        </fields>
+        <showFooter>true</showFooter>
+        <showHeader>true</showHeader>
+    </screens>
+    <start>
+        <locationX>0</locationX>
+        <locationY>0</locationY>
+        <connector>
+            <targetReference>Get_3_ServiceResources</targetReference>
+        </connector>
+    </start>
+    <status>Draft</status>
+    <variables>
+        <name>accountRecords</name>
+        <dataType>SObject</dataType>
+        <isCollection>true</isCollection>
+        <isInput>false</isInput>
+        <isOutput>false</isOutput>
+        <objectType>Account</objectType>
+    </variables>
+    <variables>
+        <name>parentObjectType</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>true</isInput>
+        <isOutput>false</isOutput>
+    </variables>
+    <variables>
+        <name>parentRecordId</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>true</isInput>
+        <isOutput>false</isOutput>
+    </variables>
+    <variables>
+        <name>recordId</name>
+        <dataType>String</dataType>
+        <isCollection>false</isCollection>
+        <isInput>true</isInput>
+        <isOutput>false</isOutput>
+    </variables>
+</Flow>

package/skills/field-service-foundation-setup-designer-get/SKILL.md

@@ -0,0 +1,135 @@
+---
+name: field-service-foundation-setup-designer-get
+description: "Creates Field Service foundation data — Work Types, Skills, Service Territories, and Operating Hours. Accepts existing data in any format or designs from scratch, and confirms the design with the user. Use this skill when a user wants to create, design, or set up Field Service foundation data."
+user-invocable: false
+metadata:
+  version: "1.0"
+  domains: ["Field Service"]
+---
+
+# Field Service Foundation Setup Designer
+
+**Design or refine Field Service foundation data — Work Types, Skills, Service Territories, Operating Hours, and other associated Field Service objects — through structured interviews. Starting from scratch or from existing recommendations.**
+
+This skill runs a design conversation — it does not call Salesforce APIs directly. It collects the design through a structured conversation, whether starting from scratch or working from existing data, and confirms the final design with the user. This skill covers two design workflows in sequence (or independently):
+
+1. **Work Types & Skills** — 6-question interview
+2. **Service Territories & Operating Hours** — 3-question interview
+
+## Entry point
+
+- **Starting from scratch** → run the full interview phases below to build the design.
+- **Have existing data** — this includes scraped/read source output, JSON or text provided by the user, or any other external source brought into context. Show a plain-English summary of the proposed configuration as a starting reference, then immediately ask: "Would you like to go through a guided design interview to refine this, or proceed directly with this configuration?" Wait for the answer before doing anything else.
+- **Ready to create** → show a plain-English summary of the records to be created (not raw JSON or skill names), ask for explicit confirmation, then proceed only after the user confirms.
+
+Never expose internal skill names, SOR IDs, or tool references to the user.
+
+## When to use
+
+- Starting Field Service setup from scratch — no existing Work Types or Territories yet
+- When initial recommendations need adjustment for either work types or territories (or both)
+- To explore different granularity levels (Work Types) or territory models (Territories)
+- When customer provides additional context about their business or coverage areas
+- During discovery sessions to design or iterate on the foundation data model
+
+## Design principles
+
+1. **Structured questions with consistent intent**
+   - Questions based on Work Type Implementation Guide and Service Territory Design Guide
+   - Adapt examples to customer's business context
+   - Intent stays consistent, wording adapts intelligently
+
+2. **Brief answers must work**
+   - "No", "Yes", "No we don't" are complete answers
+   - Progress to next question immediately
+   - No explanations required
+
+3. **Smart question adaptation**
+   - Check if topic already covered
+   - If covered: brief confirmatory question
+   - If not covered + business context: customize examples
+   - If not covered + no context: exact structured question
+
+4. **Question format** (three or four parts):
+   ```markdown
+   **Recommendation:** [Only include when context is sufficient. Lead with the best-fit option given what's known, then briefly note alternatives with the condition under which they'd apply instead — not a flat menu of equal choices, but a ranked steer. Omit entirely when confidence is low.]
+
+   **Question:** [The actual question — or a lighter "does this fit?" when a Recommendation is present]
+
+   **Why I'm asking:** [1-2 sentences: why this matters]
+
+   **Impact:** [1-2 sentences: how their answer affects the design]
+   ```
+
+## How it works
+
+### Pre-phase: Source ingestion (if provided)
+
+If no source has been provided, creatively ask the user whether they have a website or document that describes their business or Field Service operation — framing it as something that would help build a more accurate and tailored starting recommendation rather than a generic one.
+
+If the user provides a URL, fetch it. Extract Field Service-relevant signals: industry, service types, geographic coverage, team and skill structure. Use these to generate an initial recommendation covering Work Types, Skills, Service Territories, and Operating Hours — which feeds into the refinement interview rather than starting from nothing.
+
+### Phase 1: Work Types & Skills
+
+1. **Accept input**: Takes existing data in any format (JSON, CSV, free-form text), or starts fresh if nothing is provided.
+2. **Interview**: Cover these topics — service line granularity, equipment size/type variations, brand/model specificity, service tiers and site types, parts tracking, duration accuracy.
+3. **Output**: Designed Work Types and Skills as JSON + change log.
+
+### Phase 2: Service Territories & Operating Hours
+
+1. **Accept input**: Same as Phase 1.
+2. **Interview**: Cover these topics — territory structure (geographic/functional/hybrid), geographic boundaries (if applicable), functional team geographic constraints (if applicable).
+3. **Output**: Designed Service Territories and Operating Hours as JSON + change log.
+
+
+## Inputs
+
+- **Source material** (optional): A URL the agent will fetch to extract business context and generate an initial recommendation. Takes precedence over manually pasted data when both are provided.
+- **Existing data** (optional): Work Types/Skills and/or Service Territories/Operating Hours in any format — JSON, CSV, free-form text, or pasted output from a prior session. If nothing is provided, recommendations are built entirely through the interview.
+- **Business context** (optional): Additional context to tailor interview questions to the customer's industry or service model.
+
+## Outputs
+
+- Designed or refined Work Types with metadata
+- Skills inventory organized by category
+- Designed or refined Service Territories with structure
+- Operating Hours organized by timezone
+- Combined JSON export (Salesforce API-ready, for deployment via `sfs-sobject-create`)
+- Markdown summary with change log
+- Before/after comparison (when refining existing data)
+
+## Granularity Levels Reference (Work Types)
+
+From Work Type Implementation Guide:
+
+| Level | When to Use | Example |
+|-------|-------------|---------|
+| **High-Level** | Simple service models, quick setup | "Installation", "Repair", "Maintenance" |
+| **Mid-Level** | Equipment-specific service | "HVAC Installation", "HVAC Repair" |
+| **Detailed** | Brand-specific service needs | "HVAC Installation (Carrier)", "HVAC Installation (Trane)" |
+| **Hyper-Specific** | SLA/site variations | "HVAC Repair (Carrier) - Hospital" |
+
+**Best practice:** Start with simplest model possible, increase granularity only when necessary.
+
+## Territory Models Reference (Service Territories)
+
+From Service Territory Design Guide:
+
+| Model | When to Use | Example |
+|-------|-------------|---------|
+| **Geographic** | Location-based coverage, reduce travel time | "Northern California", "Southwest Region" |
+| **Functional** | Specialized service types, skill-based assignment | "Fire Safety Team", "Commercial HVAC Team" |
+| **Hybrid** | Combined benefits, specialized teams with regional boundaries | "Northern CA - Fire Safety", "Southwest - Commercial HVAC" |
+
+**Best practice:** Start with simplest model possible, increase complexity only when necessary.
+
+---
+
+## Output format
+
+Generate the output JSON payload from interview answers using this mapping:
+
+- `WorkType` → `SkillRequirement` (junction → `Skill`)
+- `WorkType` → `ProductRequired` (junction → `Product2`)
+- `OperatingHours` → `TimeSlot` (parent-child)
+- `ServiceTerritory` → `OperatingHours` (lookup)

package/skills/field-service-mobile-branding-configure/SKILL.md

@@ -0,0 +1,133 @@
+---
+name: field-service-mobile-branding-configure
+description: "Derive a Field Service mobile app color scheme from a brand source (URL, hex codes, brand-guide paste, or color description), validate WCAG AA contrast in both light and dark mode, and apply the 14-field scheme to the org-default FieldServiceMobileSettings record. Trigger phrases include 'brand the mobile app', 'apply branding to Field Service mobile', 'update the mobile app colors', 'use this brand guide for the app', 'set the color scheme for the mobile app'. Do NOT use this skill for Dispatcher console / Gantt branding, Experience Cloud BrandingSet records, or scheduling policy colors — out of scope."
+user-invocable: false
+metadata:
+  version: "1.0"
+  domains: ["Field Service"]
+---
+
+# Field Service Mobile Branding
+
+This skill ingests a brand source and produces a 14-field color scheme that gets applied to the org-default `FieldServiceMobileSettings` record (`DeveloperName='Field_Service_Mobile_Settings'`, `IsDefault=true`). Confirmation with the user happens between derivation and apply — never apply without approval.
+
+> **Source:** This skill was authored by Chad Barbour and is mirrored from an
+> upstream Field Service assets repository.
+> Methodology, color tables, and contrast checks are unchanged from upstream — refresh from upstream when content changes there.
+
+> **Runtime contract:** every org interaction in this skill is a single REST
+> call dispatched through the Codey runtime (`execute_api` locally / the hosted
+> Headless 360 MCP in shared surfaces). This skill has **no dependency on the
+> execution environment** — no `sf` CLI, no shell scripts, no local Python, no
+> temp files. Colors are derived and validated by the agent inline, then
+> written with one sObject PATCH. Do not shell out.
+
+## Input contract
+
+One of:
+
+- A website URL — fetch with `WebFetch`, extract dominant brand colors.
+- A brand-guide paste or document — parse for hex codes and named colors.
+- Direct hex codes — accept as-is.
+- A color description (e.g. "we're a red and white company") — ask for at least one specific hex code or URL before proceeding.
+
+See [reference/derivation-methodology.md](reference/derivation-methodology.md) for the four ingestion cases (A–D) in detail.
+
+## Output
+
+A 14-field color scheme written to the org-default `FieldServiceMobileSettings` record via a single sObject PATCH (`PATCH /services/data/vXX.0/sobjects/FieldServiceMobileSettings/{id}`). Color changes appear on devices after the metadata cache refreshes (default: 7 days, force-refreshable from app Settings).
+
+## Workflow
+
+### 1. Confirm the target org
+
+**Before fetching the brand source**, confirm the org is reachable with a cheap auth probe — dispatch `SELECT Id FROM Organization LIMIT 1` (`GET /services/data/vXX.0/query`):
+
+- 2xx with `totalSize=1` → the session token is live; continue.
+- 401/403 → the org needs re-authentication. Surface that to the user and **stop**; do not proceed to apply.
+
+Then ask: "Which org should I apply this to?" and wait for explicit confirmation before proceeding. Do not assume a default — even if the user mentioned an org name in their request, confirm it explicitly so there are no surprises. (The Codey runtime resolves the connected org; this skill does not manage org aliases.)
+
+### 2. Ingest the brand source
+
+Follow the cases (A–D) in [reference/derivation-methodology.md](reference/derivation-methodology.md). At the end of this step you should have two anchors:
+
+- **Primary brand color** — for non-interactive surfaces and the navbar.
+- **Secondary/interactive color** — for buttons, links, FAB.
+
+### 3. Derive the full 14-field scheme
+
+Apply the derivation rules in [reference/derivation-methodology.md](reference/derivation-methodology.md) and the field semantics in [reference/color-fields.md](reference/color-fields.md).
+
+Hold the scheme in memory as a flat object whose keys match the 14 `FieldServiceMobileSettings` color fields. Use [examples/salesforce-default-scheme.json](examples/salesforce-default-scheme.json) as a template. Before continuing, self-check that all 14 fields are present and every value matches `^#[0-9A-Fa-f]{6}$` (6-digit hex, `#` prefix — 3-digit shorthand and missing `#` are invalid); fix any that don't before proposing.
+
+### 4. Validate contrast (light + dark mode)
+
+Compute the WCAG AA contrast ratio for each pair in [reference/contrast-validation.md](reference/contrast-validation.md) **inline** — this is deterministic arithmetic on the hex values you already hold, not an external tool. For each `#RRGGBB` pair:
+
+1. Normalize each channel: `r = R/255, g = G/255, b = B/255`.
+2. Linearize each channel: `c ≤ 0.03928 → c/12.92`, else `((c+0.055)/1.055)^2.4`.
+3. Relative luminance: `L = 0.2126·r + 0.7152·g + 0.0722·b`.
+4. Contrast ratio: `(L_lighter + 0.05) / (L_darker + 0.05)`.
+
+Evaluate all 5 light-mode pairs and all 5 dark-mode pairs from [reference/contrast-validation.md](reference/contrast-validation.md); a pair PASSES at `≥ 4.5:1` (WCAG AA, normal text). Surface any FAIL pairs to the user with a suggested fix in step 5. Note that brand colors are fixed across both modes, so a passing light-mode scheme can still fail dark-mode pairs.
+
+### 5. Present proposal & confirm
+
+Show the user:
+
+- A `Brand & Navigation` / `Contrast Scale` / `Feedback Colors` table of all 14 fields with their hex values and roles.
+- The light-mode and dark-mode contrast results from step 4, with FAIL pairs flagged.
+- The target org alias.
+
+Ask the user to confirm before applying. Use the suggested fixes in [reference/contrast-validation.md](reference/contrast-validation.md) when proposing alternatives for failing pairs.
+
+### 6. Apply to org
+
+Apply only after the user has approved the proposal in step 5. Three REST calls:
+
+1. **Confirm FLS (optional but recommended).** `GET /services/data/vXX.0/sobjects/FieldServiceMobileSettings/describe` and confirm each of the 14 color fields has `updateable: true`. A field with `updateable: false` (or a filtered describe) is the earliest signal the running user lacks edit access — surface that before attempting the PATCH.
+
+2. **Resolve the org-default record.** `GET /services/data/vXX.0/query` with `SELECT Id FROM FieldServiceMobileSettings WHERE DeveloperName = 'Field_Service_Mobile_Settings' AND IsDefault = true LIMIT 1`. `totalSize = 0` means Field Service Mobile is not provisioned — surface the error and stop (see step 7). Otherwise take `records[0].Id`.
+
+3. **Write the scheme.** `PATCH /services/data/vXX.0/sobjects/FieldServiceMobileSettings/{id}` with a flat JSON body of the 14 color fields. Merge semantics — only fields in the body are written. Do **not** send `IsDefault` (not updateable). A 204 (no body) is success; then GET the record back to confirm the values landed.
+
+### 7. Report back
+
+On success, print:
+
+- `FieldServiceMobileSettings` record id.
+- Timestamp of the update.
+- Reminder that the metadata cache is 7 days by default — devices won't show the new scheme until the cache refreshes or a tech force-refreshes from app Settings.
+
+If the apply fails because no `Field_Service_Mobile_Settings` record exists, surface the error and stop — Field Service Mobile may not be set up in the org. Direct the user to Setup → Field Service Mobile Settings to bootstrap the default record, then retry.
+
+## Scope
+
+**Generated automatically:**
+
+- The full 14-field color scheme derived from one or two brand anchors plus optional brand neutrals and semantic colors.
+- Light-mode and dark-mode WCAG AA contrast validation across 5 light-mode + 5 dark-mode pairs, computed inline by the agent.
+- Apply via a single sObject PATCH against the org-default `FieldServiceMobileSettings` record.
+
+**Out of scope:**
+
+- Splash screen, profile tab background image, push notification icon — Setup-only uploads.
+- Per-profile `FieldServiceMobileSettings` records (multi-config orgs) — this skill targets the single `IsDefault=true` record. If the org has multiple records, query first and confirm which `DeveloperName` to update.
+- Dispatcher console / Gantt colors (`FSLQA__GanttPalette__c`).
+- `BrandingSet` metadata (Experience Cloud / Lightning App branding — does not theme the FS mobile app).
+
+## Files in this skill
+
+- `reference/color-fields.md` — the 14 fields, descriptions, defaults, JSON schema.
+- `reference/contrast-validation.md` — light + dark mode pair definitions, formulas, common fixes.
+- `reference/derivation-methodology.md` — translating brand sources into a full scheme, edge cases.
+- `examples/salesforce-default-scheme.json` — the out-of-the-box Salesforce purple/blue scheme.
+- `examples/dark-blue-scheme.json` — Salesforce-themed dark blue scheme (also serves as a contrast-warnings example).
+
+Contrast validation and scheme derivation are performed by the agent inline (see steps 3–4); there are no executable scripts in this skill. Org writes are single REST calls dispatched through the Codey runtime.
+
+## Related skills
+
+- `configure-field-service-mobile` — page layouts, permissions, and `FieldServiceSettings` toggles. This skill defers branding to here, and this skill defers structural mobile config to it.
+- `fs-data-capture-form-deployer` — generates and deploys Data Capture Flow metadata.

package/skills/field-service-mobile-branding-configure/examples/dark-blue-scheme.json

@@ -0,0 +1,16 @@
+{
+  "NavbarBackgroundColor": "#0F4C81",
+  "NavbarInvertedColor": "#FFFFFF",
+  "PrimaryBrandColor": "#0F4C81",
+  "SecondaryBrandColor": "#1589EE",
+  "BrandInvertedColor": "#FFFFFF",
+  "ContrastPrimaryColor": "#16325C",
+  "ContrastSecondaryColor": "#54698D",
+  "ContrastTertiaryColor": "#9FAAB5",
+  "ContrastQuaternaryColor": "#DDDBDA",
+  "ContrastQuinaryColor": "#F4F6F9",
+  "ContrastInvertedColor": "#FFFFFF",
+  "FeedbackPrimaryColor": "#C23934",
+  "FeedbackSecondaryColor": "#04844B",
+  "FeedbackSelectedColor": "#FFFFFF"
+}

package/skills/field-service-mobile-branding-configure/examples/salesforce-default-scheme.json

@@ -0,0 +1,16 @@
+{
+  "NavbarBackgroundColor": "#803ABE",
+  "NavbarInvertedColor": "#FFFFFF",
+  "PrimaryBrandColor": "#803ABE",
+  "SecondaryBrandColor": "#2A7AB0",
+  "BrandInvertedColor": "#FFFFFF",
+  "ContrastPrimaryColor": "#000000",
+  "ContrastSecondaryColor": "#444444",
+  "ContrastTertiaryColor": "#9FAAB5",
+  "ContrastQuaternaryColor": "#E6E6EB",
+  "ContrastQuinaryColor": "#EEEEEE",
+  "ContrastInvertedColor": "#FFFFFF",
+  "FeedbackPrimaryColor": "#C23934",
+  "FeedbackSecondaryColor": "#13C4A3",
+  "FeedbackSelectedColor": "#FFFFFF"
+}

package/skills/field-service-mobile-branding-configure/references/color-fields.md

@@ -0,0 +1,66 @@
+# Color Fields
+
+The `FieldServiceMobileSettings` sObject has **14 color fields**, all hex strings (`#RRGGBB`). The org-default record has `IsDefault = true` and `DeveloperName = 'Field_Service_Mobile_Settings'`. There is one default record per org.
+
+Color values are **light-mode** values. Dark mode inverts the contrast scale automatically — see [contrast-validation.md](contrast-validation.md).
+
+## Brand & Navigation
+
+| Field | Description | Salesforce default |
+|---|---|---|
+| `NavbarBackgroundColor` | The color of the top bar in the app | `#803ABE` |
+| `NavbarInvertedColor` | The secondary color of the top bar in the app | `#FFFFFF` |
+| `PrimaryBrandColor` | The color of **non-interactive** areas in the app | `#803ABE` |
+| `SecondaryBrandColor` | The color of **interactive** areas in the app | `#2A7AB0` |
+| `BrandInvertedColor` | The color of toasts and the contrast color for the floating action button | `#FFFFFF` |
+
+## Contrast Scale
+
+| Field | Description | Salesforce default |
+|---|---|---|
+| `ContrastPrimaryColor` | The color of primary text | `#000000` |
+| `ContrastSecondaryColor` | The color of secondary text | `#444444` |
+| `ContrastTertiaryColor` | The color of icons on the settings screen and primary lines delineating UI areas | `#9FAAB5` |
+| `ContrastQuaternaryColor` | The color of some graphics and secondary lines delineating UI areas | `#E6E6EB` |
+| `ContrastQuinaryColor` | The color of the background behind cards in the UI | `#EEEEEE` |
+| `ContrastInvertedColor` | The color of card backgrounds in the UI | `#FFFFFF` |
+
+## Feedback / Status Colors
+
+| Field | Description | Salesforce default |
+|---|---|---|
+| `FeedbackPrimaryColor` | The color of error messages | `#C23934` |
+| `FeedbackSecondaryColor` | The color of success messages or progress icons | `#13C4A3` |
+| `FeedbackSelectedColor` | The color indicating the user's current selection | `#FFFFFF` |
+
+## Key distinctions
+
+- `PrimaryBrandColor` = non-interactive colored areas (schedule icon dot, section labels, decorative elements).
+- `SecondaryBrandColor` = interactive elements (buttons, links, GET DIRECTIONS, floating action button background).
+- `NavbarBackgroundColor` and `PrimaryBrandColor` are typically the same color.
+- `ContrastInvertedColor` = card backgrounds (usually white), not just inverted text.
+
+## JSON spec shape
+
+The skill consumes a flat JSON object whose keys match the 14 field names exactly:
+
+```json
+{
+  "NavbarBackgroundColor": "#0070D2",
+  "NavbarInvertedColor": "#FFFFFF",
+  "PrimaryBrandColor": "#0070D2",
+  "SecondaryBrandColor": "#1589EE",
+  "BrandInvertedColor": "#FFFFFF",
+  "ContrastPrimaryColor": "#000000",
+  "ContrastSecondaryColor": "#444444",
+  "ContrastTertiaryColor": "#9FAAB5",
+  "ContrastQuaternaryColor": "#E6E6EB",
+  "ContrastQuinaryColor": "#EEEEEE",
+  "ContrastInvertedColor": "#FFFFFF",
+  "FeedbackPrimaryColor": "#C23934",
+  "FeedbackSecondaryColor": "#13C4A3",
+  "FeedbackSelectedColor": "#FFFFFF"
+}
+```
+
+Hex must be 6 digits with the `#` prefix. 3-digit shorthand and missing `#` are invalid — the agent rejects them during the step-3 self-check before proposing or applying.

package/skills/field-service-mobile-branding-configure/references/contrast-validation.md

@@ -0,0 +1,55 @@
+# Contrast Validation
+
+The Field Service mobile app supports both light and dark mode. The `FieldServiceMobileSettings` color fields apply to **light mode**. Dark mode inverts the contrast scale automatically — but brand and feedback colors remain fixed. A scheme that passes in light mode can fail in dark mode if the brand colors clash with dark backgrounds.
+
+The agent computes contrast ratios for the pairs below inline (the formulas are at the bottom of this file) and reports pass/fail against WCAG AA (`4.5:1` for normal text). Surface any failures to the user before applying.
+
+## Light mode pairs
+
+| Pair | Foreground | Background |
+|---|---|---|
+| Navbar text on navbar bg | `NavbarInvertedColor` | `NavbarBackgroundColor` |
+| Toast/FAB text on brand bg | `BrandInvertedColor` | `PrimaryBrandColor` |
+| Selected indicator on interactive | `FeedbackSelectedColor` | `SecondaryBrandColor` |
+| Primary text on card bg | `ContrastPrimaryColor` | `ContrastInvertedColor` |
+| Secondary text on card bg | `ContrastSecondaryColor` | `ContrastInvertedColor` |
+
+## Dark mode pairs
+
+In dark mode, the app inverts the contrast scale: card backgrounds become dark (`ContrastPrimaryColor`), and text becomes light (`ContrastInvertedColor`). Brand and feedback colors do **not** change.
+
+| Pair | Effective foreground | Effective background |
+|---|---|---|
+| Primary text on dark card bg | `ContrastInvertedColor` | `ContrastPrimaryColor` |
+| Secondary brand (interactive) on dark bg | `SecondaryBrandColor` | `ContrastPrimaryColor` |
+| Feedback error on dark bg | `FeedbackPrimaryColor` | `ContrastPrimaryColor` |
+| Feedback success on dark bg | `FeedbackSecondaryColor` | `ContrastPrimaryColor` |
+| Navbar (unchanged in dark mode) | `NavbarInvertedColor` | `NavbarBackgroundColor` |
+
+## Dark mode risk factors to flag
+
+- A **very light secondary brand color** (e.g. pastel yellow, light teal) may wash out against a dark-mode card bg — check `SecondaryBrandColor` on `ContrastPrimaryColor`.
+- A **light primary brand color** (e.g. CAT yellow `#FFCD11`) will have reduced contrast against light backgrounds when used as a label color in dark mode. Flag if luminance > 0.4.
+- **Feedback colors** — standard red and teal/green are generally safe in dark mode. Verify if the brand specifies non-standard semantic colors.
+
+## Luminance & contrast formulas
+
+For `#RRGGBB`:
+
+1. Normalize: `r = R/255, g = G/255, b = B/255`
+2. Linearize each channel: if `c ≤ 0.03928 → c/12.92`, else `((c+0.055)/1.055)^2.4`
+3. Relative luminance: `L = 0.2126·r + 0.7152·g + 0.0722·b`
+4. Contrast ratio: `(L_lighter + 0.05) / (L_darker + 0.05)`
+
+WCAG AA threshold for normal text: **4.5:1**.
+
+## Common fixes for failures
+
+| Failure | Suggested fix |
+|---|---|
+| Navbar pair fails (light navbar) | Use a darker brand neutral for `NavbarBackgroundColor` |
+| `FeedbackSelectedColor` on `SecondaryBrandColor` fails (light interactive) | Use `#1C1C1C` or darkest brand neutral for `FeedbackSelectedColor` |
+| `BrandInvertedColor` on `PrimaryBrandColor` fails (light primary) | Switch `BrandInvertedColor` to `#000000` or darkest neutral |
+| `SecondaryBrandColor` on `ContrastPrimaryColor` fails in dark mode | Pick a darker variant of the interactive color, or accept reduced contrast and note it in the proposal |
+
+Each suggested fix should specify which mode (light, dark, or both) it affects, so the user can weigh tradeoffs before applying.