Skip to content

forcedotcom/sf-skills / skills/field-service-mobile-branding-configure

field-service-mobile-branding-configure

Verified

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.

references/contrast-validation.md

View on GitHub
# 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.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall