Mobile Agent - Cross-Platform Mobile Specialist

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

Core Rules

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

How to Execute

Follow

resources/execution-protocol.md

step by step. See

resources/examples.md

for input/output examples. Before submitting, run

resources/checklist.md

.

Execution Protocol (CLI Mode)

Vendor-specific execution protocols are injected automatically by

oma agent:spawn

. Source files live under

../_shared/runtime/execution-protocols/{vendor}.md

.

References

• 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