oma-mobile

Implement and verify cross-platform mobile features for Flutter or React Native.

46|2|Updated Mar 23, 2025
One-click install
npx skills add https://github.com/gracefullight/krds --skill oma-mobile-gracefullight
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oma-mobile
Source: https://github.com/gracefullight/krds/tree/main/.agents/skills/oma-mobile
Command: npx skills add https://github.com/gracefullight/krds --skill oma-mobile-gracefullight

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Helps teams build and modify cross-platform mobile app features without sacrificing clean architecture, platform-correct UI, state management, performance, or end-to-end verification.

Core Features & Use Cases

  • Cross-platform feature delivery: Implement mobile UI and behavior for iOS and Android using Flutter/Dart or React Native.
  • Clean architecture + state management: Apply domain/data/presentation separation with Riverpod (or Bloc) to keep logic testable and maintainable.
  • Platform integration & offline-first support: Integrate mobile capabilities like camera, GPS, push notifications, and offline-first flows.
  • Verification coverage: Run unit/widget/integration checks and use Maestro for critical user flows, ensuring lifecycle and permissions are handled correctly.
  • Use case: Create a new “Notes” feature that works offline first, syncs on reconnect, and includes empty/error/offline UI states verified with widget tests and Maestro E2E.

Quick Start

Ask for “an offline-first Flutter notes feature for iOS and Android with Riverpod, Dio-based sync, and Maestro E2E coverage for the critical flow.”

Frequently Asked Questions about oma-mobile

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

FAQPage Schema
How do I build an offline-first Flutter feature with sync and error states?

To build an offline-first Flutter feature, you coordinate clean architecture layers with Riverpod for state management and Dio for API integration, handling empty, error, and offline UI states while syncing data upon network reconnect.

What is the best way to test cross-platform mobile user flows in React Native?

Testing cross-platform mobile user flows is best achieved by running unit and widget tests for individual components, followed by Maestro E2E tests to verify critical user journeys and platform-specific lifecycle behaviors.

Can I use Riverpod and Dio for mobile API integration and state management?

Yes, you can use Riverpod to maintain testable presentation and domain logic separation, while Dio handles API integration and data fetching, ensuring deterministic file edits across mobile architectural layers.

How do you handle device permissions and lifecycle for GPS and camera in mobile apps?

Handling device permissions and lifecycle for GPS and camera requires platform-specific UI behavior integration, guarding permissions correctly during the lifecycle, and verifying error recovery through targeted widget and integration tests.

Does this approach support integrating push notifications with offline-first workflows?

Yes, the approach supports integrating push notifications and device capabilities within offline-first workflows by applying clean architecture separation and verifying platform-specific behavior through integration and E2E checks.