Skip to main content
skill CX Codex

oma-mobile · first-fluke, oma — Claude Code skill for Flutter and React Native work

oma-mobile — a mobile-focused skill: it builds screens and widgets in Flutter or React Native, wires camera, GPS, push and offline handling, then runs the checks.

MIT ★ 1,472 updated 2026-10-29

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent
Open on GitHub

What oma-mobile does

The skill switches the agent into a mobile specialist role. It handles Flutter/Dart and React Native, keeps code split by clean architecture (domain, data, presentation), and expects Riverpod or Bloc for state plus Dio with interceptors for network calls. Android screens follow Material Design 3, iOS screens follow iOS HIG.

Supporting files ship with it: an execution protocol, examples, snippets, a checklist and a Dart screen template under resources/. The agent surveys the codebase with rg --files and a search for Riverpod|Bloc|Dio|Widget|Maestro, then implements and verifies. Maestro covers E2E runs on critical flows. Complex business logic stays in the domain and data layers rather than inside the widgets.

Web frontend and backend API work belong to other agents in the set. Verification depends on a working SDK and emulator or simulator — without them the agent reports the gap instead of claiming a pass. A missing backend contract is also flagged as a blocker, so agree on the API shape before handing over a screen that fetches data.

What it helps with

  • build a Flutter screen with a widget and Riverpod state
  • wire camera, GPS or push notifications with the right permissions
  • add offline support and network error handling through Dio
  • run widget tests and a Maestro E2E pass on a key flow
  • split a feature into domain, data and presentation layers

Example prompts for the agent

  • Build a profile screen in Flutter with Riverpod and move the data loading into the data layer
  • Add a camera permission request and a capture screen for both iOS and Android
  • Cover the offline cart flow with a widget test and check the critical path in Maestro

How to install oma-mobile

1Plugin marketplace

/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agent

This installs the whole oma plugin with all its skills

2Skills CLI (Vercel)

npx skills add first-fluke/oh-my-agent --skill oma-mobile -a claude-code

3Manually: put the files in place

~/.claude/skills/oma-mobile/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/oma-mobile/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about oma-mobile

How do I install oma-mobile in Claude Code?

Use the marketplace: /plugin marketplace add first-fluke/oh-my-agent first, then /plugin install oma@oh-my-agent. The skill file lands at ~/.claude/skills/oma-mobile/SKILL.md.

What does oma-mobile do?

It takes a mobile feature from preparation to verification: reads existing screens and providers, writes UI and state code, configures permissions and offline handling, then runs tests.

Does it replace the frontend agent?

No. oma-mobile targets native and cross-platform apps; web frontend and backend API tasks go to the Frontend Agent and Backend Agent.

Source text

SKILL.md · MIT
---
name: oma-mobile
description: Mobile specialist for Flutter, React Native, and cross-platform mobile development. Use for mobile app, Flutter, Dart, iOS, Android, Riverpod, and widget work.
---

# 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 template

### Control-flow features
- Branches by platform, state management pattern, offline requirement, native permission, and test level
- Reads and writes mobile codebase files
- May call build, test, simulator, emulator, or E2E commands

## Structural Flow

### Entry
1. Identify target platform(s), screen/feature, architecture layer, and state boundary.
2. Inspect existing mobile patterns and dependencies.
3. Determine test level and verification environment.

### Scenes
1. **PREPARE**: Load app architecture, platform constraints, and acceptance criteria.
2. **ACQUIRE**: Read existing widgets/screens, providers/blocs, API clients, and tests.
3. **ACT**: Implement mobile UI, state, platform integration, offline handling, and tests.
4. **VERIFY**: Run relevant unit/widget/integration/E2E checks.
5. **FINALIZE**: Report behavior, platforms covered, and verification results.

### Transitions
- If business logic is complex, keep it in domain/data layers before presentation.
- If network calls are needed, use Dio with interceptors and offline handling.
- If a critical user flow changes, add or update Maestro E2E coverage.
- 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 tests fail, fix before handoff or report the failing check.

### Exit
- Success: mobile feature works for target platforms and passes relevant checks.
- Partial success: platform, simulator, dependency, or verification gaps are explicit.

## Logical Operations

### Actions
| Action | SSL primitive | Evidence |
|--------|---------------|----------|
| Inspect mobile architecture | `READ` | Domain/data/presentation files |
| Select state and platform strategy | `SELECT` | Riverpod/Bloc and platform constraints |
| Implement mobile code | `WRITE` | Widgets, screens, providers, clients |
| Validate lifecycle and permissions | `VALIDATE` | Dispose, permissions, offline behavior |
| Call verification tools | `CALL_TOOL` | Tests, builds, Maestro |
| Report result | `NOTIFY` | Final summary |

### Tools and instruments
- Flutter/Dart or React Native stack
- Riverpod/Bloc, Dio, platform SDKs, Maestro
- Unit, widget, integration, and E2E test commands

### Canonical workflow path
```bash
rg --files
rg "Riverpod|Bloc|Dio|Widget|Maestro|dispose\\(|permission" .
```

Then run the project's mobile verification commands, typically unit/widget tests and Maestro E2E for critical flows.

### Resource scope
| Scope | Resource target |
|-------|-----------------|
| `CODEBASE` | Mobile source, tests, platform config |
| `LOCAL_FS` | Templates, snippets, resources |
| `PROCESS` | Build, test, emulator, simulator, E2E commands |
| `NETWORK` | Backend APIs when the feature integrates remotely |

### Preconditions
- Target mobile feature and platform scope are identifiable.
- Required SDKs, permissions, and API contracts are available or assumptions are stated.

### Effects and side effects
- Mutates mobile source, tests, and platform configuration.
- May affect permissions, app lifecycle, offline data, or performance.

### Guardrails
1. Clean Architecture: domain -> data -> presentation
2. Riverpod/Bloc for state management (no raw setState for complex logic)
3. Material Design 3 (Android) + iOS HIG (iOS)
4. All controllers disposed in `dispose()` method
5. Dio with interceptors for API calls; handle offline gracefully
6. 60fps target; test on both platforms
7. Use Maestro for E2E testing of critical user flows

## References
Follow `resources/execution-protocol.md` step by step.
See `resources/examples.md` for input/output examples.
Before submitting, run `resources/checklist.md`.
Vendor-specific execution protocols are injected automatically by `oma agent:spawn`.
Source files live under `../_shared/runtime/execution-protocols/{vendor}.md`.
- Execution steps: `resources/execution-protocol.md`
- Code examples: `resources/examples.md`
- Code snippets: `resources/snippets.md`
- Checklist: `resources/checklist.md`
- Error recovery: `resources/error-playbook.md`
- Tech stack: `resources/tech-stack.md`
- Screen template: `resources/screen-template.dart`
- Context loading: `../_shared/core/context-loading.md`
- Reasoning templates: `../_shared/core/reasoning-templates.md`
- Clarification: `../_shared/core/clarification-protocol.md`
- Context budget: `../_shared/core/context-budget.md`
- Lessons learned: `../_shared/core/lessons-learned.md`

© First Fluke · MIT · first-fluke/oh-my-agent

Similar skills

All skills for Mobile →

oma-mobile by other authors comes first.

oma-mobile First Fluke oma-mobile is a skill that builds and edits mobile screens and features in Flutter, React Native, Swift, or Kotlin. It inspects existing widgets, providers, and API clients before code changes. CX Codex +1 ★ 1,472repo stars flutter-dev MiniMax-AI flutter-dev is a Claude Code skill for building Flutter apps, with guidance on state management, navigation, and testing. It activates for widget work, responsive layouts, and performance tuning. CX Codex +1 2,000installs flutter-expert davila7 flutter-expert sets up Claude Code for cross-platform app engineering with Flutter 3.x and Dart 3. Helps handle state management, platform channels, and Impeller tuning. CX Codex +1 437installs senior-mobile borghei senior-mobile — a mobile development skill that runs in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. CX Codex +1 316installs mobile-development samhvw8 A mobile development reference for your agent: picking between React Native, Flutter and native, offline sync, push, biometrics and store releases. CX Codex +1 112installs flutter-mobile rohitg00 flutter-mobile — a Claude Code plugin for Flutter app development. Create widgets and set up platform channels to connect Dart code with native iOS and Android functionality. ★ 2,858repo stars mobile-developer VoltAgent Community mobile-developer — a subagent for React Native and Flutter apps that covers native features, offline-first architecture, and platform-aware performance work. CX Codex 7,777installs

From the same set69

The whole set →
frontend frontend — a rule for React and Next.js projects: shadcn/ui components, Tailwind CSS v4, FSD-lite architecture, Server Components by default. CX Codex +1 ★ 1,472repo stars oma-docs Verifies documentation links, syncs docs against Git diffs, and flags translation drift. Runs through the oma docs CLI or falls back to manual markdown parsing. CX Codex +1 ★ 1,472repo stars oma-scm oma-scm — a skill that gives an agent a safe process for commits, branches, merges and conflict resolution. Use it when repository history matters and a careless force-push is not an option. CX Codex +1 ★ 1,472repo stars oma-skill-creation oma-skill-creation is a Claude Code skill for building and refining OMA skills in SSL-lite format for Claude Code and Codex. It runs during authoring, routing reviews, and contract validation. CX Codex +1 ★ 1,472repo stars oma-debug oma-debug — a skill for Claude Code and Codex isolates bugs, writes targeted fixes, and creates regression tests. Runs when tests fail, services crash, or code suffers from race conditions. CX Codex +1 ★ 1,472repo stars oma-qa The oma-qa skill for Claude Code and Codex reviews changes for security, performance, accessibility, and correctness. It checks a diff, runs relevant tools, and reports reproducible findings with fixes. CX Codex +1 ★ 1,472repo stars oma-search oma-search — a skill for Claude Code and Codex that routes queries across external documentation, web search, and remote code. It picks the matching retrieval channel and returns answers backed by citations. CX Codex +1 ★ 1,472repo stars oma-pm oma-pm is a Claude Code skill that turns product requirements into a prioritized task plan with dependencies and acceptance criteria. It prepares the plan before work is handed to specialist agents. CX Codex +1 ★ 1,472repo stars

Project sponsors

Companies that keep this analytics open