What problem does it solve? Mobile teams must juggle platform design guidelines, legally mandated accessibility requirements, and complex offline-first data architecture, and getting any of these wrong leads to app store rejections, regulatory fines, or data loss. ## Core Features & Use Cases - Platform UI Standards: Enforces Apple HIG (44pt hit targets, Dynamic Type) and Material Design 3 (48dp touch targets, dynamic color), plus dark mode, design tokens, and optimistic-UI states. - Accessibility Compliance: Covers WCAG 2.2 Level AA (including the new 24×24px target size rule) and the EU Accessibility Act enforced since June 2025, with penalties up to €1,000,000 in Spain and criminal liability in Ireland. - Architecture & Persistence Guidance: Provides Clean Architecture, MVVM/MVI, Repository pattern, offline-first sync with LWW/CRDT conflict resolution, and concrete library guidance for MMKV, WatermelonDB, Realm (EOL), and SQLCipher/op-sqlite/expo-sqlite. - Use Case: When building a React Native app that must work offline and pass EU accessibility audits, use this Skill to choose the right persistence library, design compliant touch targets, and set up push notifications via Azure Notification Hubs with FCM v1. ## Quick Start Review my React Native app's settings screen for WCAG 2.2 AA compliance and recommend an offline-first persistence library.