Agent skill · forcedotcom
mobile-platform-offline-validate
Review a Lightning Web Component for **mobile offline** compatibility — the Komaci offline static analyzer that pre-primes the data graph for Salesforce Mobile App Plus and Field Service Mobile App. Produces a finding list with code-level fixes covering inline GraphQL queries in `@wire` configurations, modern `lwc:if` / `lwc:elseif` / `lwc:else` directives, and Komaci ESLint rule violations (private wire properties, non-local reactive references, getter side-effects). Use when the user asks for a \"mobile offline review\", \"Komaci check\", \"offline priming audit\", \"offline priming failure\", or \"offline data graph error\", or to validate an LWC against the `@salesforce/eslint-plugin-lwc-graph-analyzer` recommended ruleset. Do not use for generic LWC code review (use an appropriate domain review skill) or for building LWCs with native mobile capabilities (use `mobile-platform-native-capabilities-integrate`).
What it needs
About 4k tokens when loaded.
What this skill does
Reviewing LWC Mobile Offline Run a structured offline-priming compliance pass over a Lightning Web Component, producing a report of issues found and code-level fixes to bring the component into compliance with Komaci's static analysis requirements for the Salesforce Mobile App Plus and Field Service Mobile App. When to Use The user asks for a "mobile offline review", "Komaci check", or "offline priming audit" on a specific LWC. Preparing a component to ship in Salesforce Mobile App Plus or Field Service Mobile App offline mode. Investigating priming failures reported by the offline analyzer. Do NOT use this skill for: Building an LWC that uses native mobile capabilities (barcode scanner, biometrics, location, etc.) — use mobile-platform-native-capabilities-integrate. Generic LWC code review — use the appropriate domain skill (reviewing-lws-security, reviewing-lwc-rtl, accessibility-code-review). Prerequisites Component path (LWC bundle under modules/…). Access to the component's JS/TS and HTML templates. Local Node + npm; ability to run npx eslint with the @salesforce/eslint-plugin-lwc-graph-analyzer plugin. Knowledge Base Mobile Offline Grounding explains the three violation categories and why each blocks offline priming. Read it before judging. The per-reviewer references below are the source of truth for the rules and remediations: Inline GraphQL wire configuration: Inline GraphQL Reviewer lwc:if conditional rendering compatibility: lwc:if Reviewer Komaci ESLint static analysis: Komaci ESLint Reviewer Workflow Step 1 — Scope the review Identify the component bundle: .html, .js/.ts. CSS and meta files are not in scope for offline priming. If the bundle has multiple HTML templates, all are reviewed. Step 2 — Read the grounding and per-reviewer references Read Mobile Offline Grounding and the three per-reviewer references end-to-end before judging. Cite the specific reviewer when emitting each finding so the report is auditable. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills forcedotcom/mobile-platform-offline-validate--0cc920