Implement Flutter, React Native, native Swift, or native Kotlin Android apps. Use for mobile screens, widgets, platform integrations, and application data flows.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/oma-mobile/SKILL.mdBuild, modify, and verify cross-platform mobile application features with clean architecture, platform-appropriate UI, state management, performance, and E2E coverage.
resources/execution-protocol.md, resources/checklist.md, and the stack reference (stack/ when it exists, otherwise the matching variants/<platform>/)Client / generated Kotlin *Api over Ktor) with interceptors and offline handling.find_file, search_for_pattern, get_symbols_overview, and find_symbol. Native search is limited to the provider exclusions and non-code paths permitted by the project's search policy.verify: block of stack/stack.yaml when 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.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.
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.
App/Core/Features/Shared; Kotlin native: app/{ui,data,di} + api-client); business logic never lives in widgets, views, or composables@MainActor @Observable; Kotlin: @HiltViewModel + StateFlow. No raw setState or ad-hoc state for complex logicdispose(); React Native effect cleanups; Swift structured .task {}; Kotlin viewModelScopeClient middleware, and Kotlin uses Ktor plugins on the generated *Api client.@MainActor @Observable view models (Observation framework, iOS 17+) — non-isolated VMs mutating observed state from a Task are a Swift 6 strict-concurrency errorHTTPBody), serve stale-while-revalidate on reads, invalidate keys on writes; view models depend on a protocol seam, not the concrete service (see variants/swift-ios/snippets.md §10)App/Core/Features/Shared project layout.task {} (auto-cancels on disappear) — never in deinit, which is nonisolated and cannot touch @MainActor state under Swift 6 (isolated deinit requires Swift 6.2+).toolbar(.hidden, for: .navigationBar)) lose it, so register push routes via a swipeBackDestination wrapper, not per-screen (see variants/swift-ios/snippets.md §9)variants/flutter/snippets.md §3 and the Response Cache rules in variants/flutter/tech-stack.md)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 (see variants/react-native/snippets.md)@HiltViewModel exposing one StateFlow<UiState> collected with collectAsStateWithLifecycle; network work in viewModelScope, CancellationException always rethrownorg.openapi.generator, kotlin / jvm-ktor), call the generated *Api for covered endpoints and keep the Ktor engine (OkHttp on device, MockEngine in 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 (see variants/kotlin-android/snippets.md §1, §3)Cache or Ktor HttpCache; view models depend on an interface seam, not the concrete repository (see variants/kotlin-android/snippets.md §4, §8)app/{ui,data,di} + api-client layout; type-safe Navigation Compose routes; Material Design 3; JUnit + ktor-client-mock contract tests, Compose UI tests or Maestro for critical flowsPackage.swift (Swift iOS), settings.gradle.kts + com.android.application (Kotlin Android), pubspec.yaml (Flutter), or package.json + react-native (React Native), and read the existing code.stack/ when it exists; otherwise the matching variants/<platform>/. /stack-set writes stack/ from the detected project, seeded from the variant, and oma verify agent mobile reads stack/stack.yaml. Treat either as supplementary reference for conventions and snippets — the project's own code wins./stack-set.File names are relative to the stack reference directory selected above. Load only the selected platform's files.
stack.yaml: structured declaration (language, framework, state, navigation, http_client, …) and the verify: contract. Schema: variants/stack.schema.json.tech-stack.md: human-readable reference only; stack.yaml wins on conflict.snippets.mdresources/stack-generation.md (loaded by /stack-set when it generates this skill's stack/)resources/execution-protocol.mdresources/checklist.mdresources/error-playbook.mdresources/tech-stack.mdvariants/README.mdvariants/swift-ios/tech-stack.md, variants/swift-ios/snippets.mdvariants/kotlin-android/tech-stack.md, variants/kotlin-android/snippets.mdvariants/flutter/tech-stack.md, variants/flutter/snippets.mdvariants/react-native/tech-stack.md, variants/react-native/snippets.mdreferences/_shared/core/context-loading.mdreferences/_shared/core/clarification-protocol.mdreferences/_shared/core/context-budget.mdreferences/_shared/core/lessons-learned.md (matching prior failure or requested retrospective)../oma-observability/SKILL.md §Integrations — offline queuing, crash analytics, battery-aware samplingfirst-fluke/oh-my-agent
2bd468c
Also appears in
on Nov 18, 2026
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.