What problem does it solve? Building Salesforce LWCs that access native mobile device features requires knowing which capability service to use, its exact TypeScript API, and how to handle availability gating and typed failure codes — this Skill provides the authoritative API references and wiring workflow so the generated component works correctly inside Salesforce mobile apps. ## Core Features & Use Cases - Capability Routing: Maps a feature request to one of 11 native services — barcode scanner, biometrics, location, geofencing, NFC, calendar, contacts, document scanner, AR space capture, app review, and payments. - Authoritative API References: Loads per-capability TypeScript definitions from lightning/mobileCapabilities, including deprecated methods to avoid and typed failure-code enums. - Safe Integration Patterns: Enforces isAvailable() gating, non-deprecated entry points, and per-failure-code error handling for graceful degradation on desktop and mobile web. - Use Case: A developer asks for an LWC that scans a QR code and writes the value into a record field — the Skill routes to the Barcode Scanner reference, uses scan() instead of the deprecated capture methods, and maps rejection codes like USER_DENIED_PERMISSION to actionable UX. ## Quick Start Ask the agent to build an LWC that uses a native device capability, for example: create a Lightning web component that scans a barcode and saves the value to a field.