oma-mobile

# Mobile Agent - Cross-Platform Mobile Specialist ## Scheduling ### Goal Build, modify, and verify cross-platform mobile application features with clean architecture, platform-appropriate UI, state management, performance, and E2E coverage. ### Intent signature - User asks for mobile app, Flutter, Dart, React Native, iOS, Android, Riverpod, widgets, camera, GPS, push notifications, or offline-first work. - User needs native or cross-platform mobile behavior rather than web frontend work. ### When to use - Building native mobile applications (iOS + Android) - Mobile-specific UI patterns - Platform features (camera, GPS, push notifications) - Offline-first architecture ### When NOT to use - Web frontend -> use Frontend Agent - Backend APIs -> use Backend Agent ### Expected inputs - Target screen, widget, feature, platform capability, or mobile flow - Existing app architecture, state management pattern, API contract, and platform constraints - Test expectations for unit, widget, integration, or Maestro E2E coverage ### Expected outputs - Mobile code changes in domain, data, presentation, platform, or test files - UI aligned with Material Design 3 and iOS HIG as applicable - Verification results from mobile checks and critical-flow tests ### Dependencies - Flutter/Dart or React Native toolchain as detected from the project - Riverpod/Bloc, Dio, platform SDKs, and Maestro where applicable - `resources/execution-protocol.md`, examples, snippets, checklist, and screen templa...