oma-mobile
Implement Flutter, React Native, native Swift, or native Kotlin Android apps. Use for mobile screens, widgets, platform integrations, and application data flows.
How do I install this agent skill?
npx skills add https://github.com/first-fluke/oh-my-agent --skill oma-mobileIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The oma-mobile skill is a comprehensive set of instructions and templates for implementing mobile applications across multiple platforms. It adheres to security best practices and does not contain any malicious patterns.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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, Jetpack Compose, Kotlin, 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
- The checks selected for the change, which of them ran, and what was not verified
Dependencies
- Flutter/Dart, React Native, Swift, or Kotlin/Gradle toolchain as detected from the project
- Riverpod/Bloc, Dio, Hilt, Ktor, platform SDKs, and Maestro where applicable
resources/execution-protocol.md,resources/checklist.md, and the stack reference (stack/when it exists, otherwise the matchingvariants/<platform>/)- The project's unit, widget, integration, and E2E test commands, and a simulator or emulator when a check needs one
Structural Flow
Transitions
- If business logic is complex, keep it in domain/data layers before presentation.
- If network calls are needed, use the variant transport (Dio / axios / generated Swift
Client/ generated Kotlin*Apiover Ktor) with interceptors and offline handling. - If a critical user flow changes, add or update its E2E coverage (Maestro; XCUITest on Swift native).
- If backend contracts are missing, coordinate with backend/API work.
Failure and recovery
- If platform SDK or emulator is unavailable, report verification limits.
- If a permission or native capability is missing, add explicit platform configuration or document blocker.
- If a check that ran fails, fix it before handoff or report the failing check.
Exit
- Success: mobile feature is implemented for the target platforms; required checks that ran pass and unrun checks are reported.
- Partial success: platform, simulator, dependency, or verification gaps are explicit.
Logical Operations
Canonical workflow path
- Detect the platform and stack (see Stack Detection) and identify the target platform(s), screen or feature, architecture layer, state boundary, platform constraints, and acceptance criteria. State assumptions where a required SDK, permission, or API contract is unavailable.
- Locate files and inspect symbols or content with the configured code-intelligence provider. For Serena, use
find_file,search_for_pattern,get_symbols_overview, andfind_symbol. Native search is limited to the provider exclusions and non-code paths permitted by the project's search policy. - Read the existing domain, data, and presentation code: widgets or screens, providers or blocs, API clients, tests, and dependencies.
- Implement the mobile UI, state, platform integration, offline handling, and tests, following the Guardrails. Check resource disposal, permissions, and offline behavior.
- Determine the test level and verification environment, then select the project's mobile verification commands (the
verify:block ofstack/stack.yamlwhen present, otherwise the variant's): typically unit/widget tests and E2E for critical flows. Run them only when the user or the active workflow requires it, never build unless the user asked for a build, and report what was not verified.
- Check the applicable checklist items and report the behavior, the platforms covered, what was verified, and what was not.
Resource scope and effects
Reads and edits mobile source, tests, and platform configuration; reads the stack reference, snippets, and resources. A change may affect permissions, app lifecycle, offline data, or performance. Test, emulator, simulator, and E2E commands run only when the user or the active workflow requires them; builds run only on explicit request. Backend APIs are called when the feature integrates remotely.
Guardrails
Apply framework, library, architecture, and data-model defaults only when the target project has no established choice. Scoped edits do not authorize a stack migration or unrelated infrastructure.
- Clean Architecture: domain -> data -> presentation (Swift native:
App/Core/Features/Shared; Kotlin native:app/{ui,data,di}+api-client); business logic never lives in widgets, views, or composables - State management is the variant's solution — Flutter: Riverpod/Bloc; React Native: Zustand + TanStack Query; Swift:
@MainActor @Observable; Kotlin:@HiltViewModel+StateFlow. No raw setState or ad-hoc state for complex logic - Material Design 3 (Android) + iOS HIG (iOS)
- Release resources with the platform's lifecycle: Flutter controllers in
dispose(); React Native effect cleanups; Swift structured.task {}; KotlinviewModelScope - Use the platform transport with auth/retry/logging interception and offline handling: Flutter uses Dio, React Native uses axios behind TanStack Query, Swift uses generated
Clientmiddleware, and Kotlin uses Ktor plugins on the generated*Apiclient. - 60fps target; cover the supported target platforms (Swift iOS needs iOS only; Kotlin Android needs Android only). Secrets live in secure storage only (flutter_secure_storage / Keychain / react-native-keychain / Android Keystore-backed storage) — never plain prefs or MMKV
- E2E for critical user flows: Maestro (Flutter / React Native / Kotlin) or XCUITest (Swift native)
- Swift native: SwiftUI +
@MainActor @Observableview models (Observation framework, iOS 17+) — non-isolated VMs mutating observed state from aTaskare a Swift 6 strict-concurrency error - Swift native: use the existing API layer. When the project adopts OpenAPI generation, use its generated Client for covered endpoints; a UI-only edit does not introduce a generator.
- Swift native: when response caching is required, use the existing Repository cache; for a new hyperoslo/Cache implementation, use a ResponseCache actor — cache DECODED models (never
HTTPBody), serve stale-while-revalidate on reads, invalidate keys on writes; view models depend on a protocol seam, not the concrete service (seevariants/swift-ios/snippets.md§10) - Swift native: follow
App/Core/Features/Sharedproject layout - Swift native: iOS Human Interface Guidelines for all UI decisions
- Swift native: XCTest or Swift Testing for units, XCUITest for critical flows; cancel work via structured
.task {}(auto-cancels on disappear) — never indeinit, which is nonisolated and cannot touch@MainActorstate under Swift 6 (isolated deinit requires Swift 6.2+) - Swift native: restore edge swipe-back at the route layer — nav-bar-hidden screens (
.toolbar(.hidden, for: .navigationBar)) lose it, so register push routes via aswipeBackDestinationwrapper, not per-screen (seevariants/swift-ios/snippets.md§9) - Flutter: when offline response caching is required, use the existing repository cache; if adding Drift, read cached entities then revalidate (stale-while-revalidate), and invalidate/refresh affected rows on every write; cache decoded entities at the data layer, never at the Dio transport (see
variants/flutter/snippets.md§3 and the Response Cache rules invariants/flutter/tech-stack.md) - React Native: preserve the existing server-state layer; for TanStack Query with explicit
staleTime/gcTime— invalidate affected query keys on every mutation, persist account-scoped cache to MMKV only when offline persistence is required; screens consume query/mutation hooks, never call axios directly (seevariants/react-native/snippets.md) - Kotlin native: Jetpack Compose +
@HiltViewModelexposing oneStateFlow<UiState>collected withcollectAsStateWithLifecycle; network work inviewModelScope,CancellationExceptionalways rethrown - Kotlin native: use the existing API layer. When the project adopts OpenAPI generation (
org.openapi.generator,kotlin/jvm-ktor), call the generated*Apifor covered endpoints and keep the Ktor engine (OkHttp on device,MockEnginein tests) injected where the client is constructed — Ktor is an engine-agnostic layer, not an OkHttp replacement; a UI-only edit does not introduce a generator (seevariants/kotlin-android/snippets.md§1, §3) - Kotlin native: when response caching is required, use the existing repository cache; for a new Room implementation cache DECODED models with explicit TTL, stale-while-revalidate on reads, upsert/delete on writes — never OkHttp
Cacheor KtorHttpCache; view models depend on an interface seam, not the concrete repository (seevariants/kotlin-android/snippets.md§4, §8) - Kotlin native: follow the
app/{ui,data,di}+api-clientlayout; type-safe Navigation Compose routes; Material Design 3; JUnit +ktor-client-mockcontract tests, Compose UI tests or Maestro for critical flows
Stack Detection
<!-- oma-docs:ignore-start -->- Project files first: detect the platform from
Package.swift(Swift iOS),settings.gradle.kts+com.android.application(Kotlin Android),pubspec.yaml(Flutter), orpackage.json+react-native(React Native), and read the existing code. - Stack reference second: use
stack/when it exists; otherwise the matchingvariants/<platform>/./stack-setwritesstack/from the detected project, seeded from the variant, andoma verify agent mobilereadsstack/stack.yaml. Treat either as supplementary reference for conventions and snippets — the project's own code wins. - Neither applies: ask the user or suggest running
/stack-set.
Stack-Specific Reference
File names are relative to the stack reference directory selected above. Load only the selected platform's files.
<!-- oma-docs:ignore-start -->- Stack manifest:
stack.yaml: structured declaration (language,framework,state,navigation,http_client, …) and theverify:contract. Schema:variants/stack.schema.json. - Tech stack narrative:
tech-stack.md: human-readable reference only;stack.yamlwins on conflict. - Code snippets (data layer, state, screen, tests):
snippets.md
References
- Stack generation spec:
resources/stack-generation.md(loaded by/stack-setwhen it generates this skill'sstack/) - Execution steps (follow for the selected task):
resources/execution-protocol.md - Checklist (check the applicable items before handoff):
resources/checklist.md - Error recovery (on an observed failure):
resources/error-playbook.md - Tech stack index (platform selection, shared response-cache contract):
resources/tech-stack.md - Variant registry:
variants/README.md - Swift iOS variant:
variants/swift-ios/tech-stack.md,variants/swift-ios/snippets.md - Kotlin Android variant:
variants/kotlin-android/tech-stack.md,variants/kotlin-android/snippets.md - Flutter variant:
variants/flutter/tech-stack.md,variants/flutter/snippets.md - React Native variant:
variants/react-native/tech-stack.md,variants/react-native/snippets.md - Context loading:
references/_shared/core/context-loading.md - Clarification:
references/_shared/core/clarification-protocol.md - Context budget:
references/_shared/core/context-budget.md - Lessons learned:
references/_shared/core/lessons-learned.md(matching prior failure or requested retrospective) - Observability handoff:
../oma-observability/SKILL.md§Integrations — offline queuing, crash analytics, battery-aware sampling
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/first-fluke/oh-my-agent/oma-mobile">View oma-mobile on skillZs</a>