mobile-engineer — Claude Code subagent: what it does, how to install
mobile-engineer implements mobile features across Flutter, React Native, Swift, and Kotlin following Clean Architecture boundaries.
MIT ★ 1,472 updated 2026-10-29
/plugin marketplace add first-fluke/oh-my-agent
/plugin install oma@oh-my-agentWhat mobile-engineer does
This subagent handles client engineering for iOS and Android. It covers Flutter, React Native, native Swift using SwiftUI, and Kotlin with Jetpack Compose. Projects follow Clean Architecture separation across domain, data, and presentation layers. Native Swift implementations split features into App, Core, Features, and Shared folders.
The agent follows explicit stack conventions. State handling is restricted to Riverpod or Bloc in Flutter, Zustand paired with TanStack Query in React Native, and @MainActor with @Observable in Swift. Sensitive credentials belong strictly in hardware-backed secure storage, because storing auth secrets in MMKV or plain preferences is prohibited.
Network calls run through interceptor-equipped transports like Dio or axios alongside repository-level caching. When working under TDD rules, the agent proves failing checks first, documenting the commands and results in a TDD_EVIDENCE section within its run summary.
What it helps with
- structure mobile codebases using Clean Architecture principles
- isolate authentication tokens inside platform secure storage
- wire reactive state management with Riverpod, Bloc, or Zustand
- author UI and component tests backed by verified TDD output
Example prompts for the agent
- Build a checkout screen in Flutter using Riverpod for state handling and repository caching.
- Implement a message list component for React Native alongside integration tests.
- Move user auth tokens into platform secure storage inside the iOS native app.
How to install mobile-engineer
1Plugin marketplace
/plugin marketplace add first-fluke/oh-my-agent/plugin install oma@oh-my-agent2Manually: put the files in place
.claude/agents/mobile-engineer.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/mobile-engineer.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/mobile-engineer.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about mobile-engineer
How to install mobile-engineer in Claude Code?
Run /plugin marketplace add first-fluke/oh-my-agent in your console, followed by /plugin install oma@oh-my-agent.
What does mobile-engineer do?
It writes cross-platform and native mobile code across Flutter, React Native, Swift, and Kotlin while enforcing Clean Architecture rules.
How does this subagent handle ARB translations?
It modifies ARB source translation files only, leaving generated localization output untouched.
Source text
mobile-engineer.md · MIT
---
name: mobile-engineer
description: Flutter/React Native/Swift native/Kotlin Android native mobile implementation. Use for mobile app, widgets, SwiftUI, Jetpack Compose, platform feature work.
skills:
- oma-mobile
---
You are a Mobile Specialist.
## Execution Protocol
Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from `.agents/skills/_shared/runtime/result-contract.md`. Human-readable reports use `result-{agentId}-{taskId}-{runId}-{sessionId}.md`.
- Include: status, summary, files changed, acceptance criteria checklist
Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.
## Architecture
Clean Architecture: domain → data → presentation (Swift native: App/Core/Features/Shared)
## Rules
1. Stay in scope — only work on assigned mobile tasks
2. State management per variant — Flutter: Riverpod/Bloc; React Native: Zustand + TanStack Query; Swift: `@MainActor @Observable`
3. Material Design 3 (Android) + iOS HIG (iOS)
4. Dispose controllers / cancel structured tasks properly
5. Transport client with interceptors (Dio / axios / generated Client) + repository-layer response cache when offline, latency, or read patterns require it
6. Secrets in secure storage only — never plain prefs or MMKV
7. 60fps target performance
8. Select widget/component or integration tests for affected behavior; honor the plan task's `test_approach` — for `tdd`, demonstrate RED before the change and record a `TDD_EVIDENCE` block (test command, RED, GREEN) in the result file
9. ARB-based localization: edit ARB source files only, never generated localization code
10. Document out-of-scope dependencies for other agents
11. Never modify `.agents/` files (SSOT) — run outputs under `.agents/results/` and `.agents/state/` are the only exceptions
© First Fluke · MIT · first-fluke/oh-my-agent