mobile-platform-offline-validate

Name: mobile-platform-offline-validate
Availability: InStock
Author: angryracoon

Review Lightning Web Components for mobile offline priming blockers.

Updated Jun 17, 2026

Search Tags:#graphql #eslint #salesforce #lwc #offline validation #komaci

Ready to run

npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill mobile-platform-offline-validate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mobile-platform-offline-validate
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/mobile-platform-offline-validate
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill mobile-platform-offline-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @salesforce/eslint-plugin-lwc-graph-analyzer, eslint, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies Lightning Web Component patterns that block mobile offline data priming in Salesforce Mobile App Plus and Field Service Mobile App, then explains how to fix them.

Core Features & Use Cases

Conditional Rendering Review: Flags modern lwc:if, lwc:elseif, and lwc:else usage that must be rewritten for offline compatibility.
GraphQL Wire Analysis: Detects inline GraphQL queries in wire configurations and recommends extracting them into component getters.
Komaci ESLint Remediation: Translates supported @salesforce/eslint-plugin-lwc-graph-analyzer findings into concrete code-level fixes.
Use Case: Review a component bundle before release to catch offline priming failures and produce an actionable issue list with suggested fixes.

Quick Start

Ask for a mobile offline review of the target LWC bundle and request a Komaci compatibility report with code-level remediation steps.

Frequently Asked Questions about mobile-platform-offline-validate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fix LWC offline priming blockers for Salesforce Mobile App Plus?▼

LWC offline priming blockers are fixed by rewriting lwc:if directives, extracting inline GraphQL queries into getters, and remediating lwc-graph-analyzer violations. Reviewing component bundles identifies these patterns before release.

Why does conditional rendering with lwc:if break Field Service Mobile App offline compatibility?▼

Conditional rendering with lwc:if breaks offline compatibility because it disrupts mobile offline data priming. Rewriting lwc:if, lwc:elseif, and lwc:else directives restores component support for offline environments.

How do I extract inline GraphQL queries in LWC wire adapters for offline validation?▼

Extract inline GraphQL queries in LWC wire adapters by moving them into component getters. This refactoring is required to pass offline compatibility checks and ensure successful mobile data priming.

Can I use the Komaci eslint-plugin-lwc-graph-analyzer to check Lightning Web Components offline support?▼

Yes, the eslint-plugin-lwc-graph-analyzer checks Lightning Web Components offline support. Supported Komaci ESLint findings are translated into concrete code-level fixes to resolve offline data priming issues.

What are the limitations of offline validation for LWC bundles using GraphQL wire adapters?▼

Offline validation for LWC bundles using GraphQL wire adapters requires extracting inline queries into getters. Limitations include remediating only supported lwc-graph-analyzer violations and rewriting all conditional rendering directives.