Mobile specialist for Flutter, React Native, and cross-platform mobile development. Use for mobile app, Flutter, Dart, iOS, Android, Riverpod, and widget work.
8k tokens
context cost
the whole folder, loaded on every use
8
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1201
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
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
Identify target platform(s), screen/feature, architecture layer, and state boundary.
Inspect existing mobile patterns and dependencies.
Determine test level and verification environment.
Scenes
PREPARE: Load app architecture, platform constraints, and acceptance criteria.
ACQUIRE: Read existing widgets/screens, providers/blocs, API clients, and tests.
ACT: Implement mobile UI, state, platform integration, offline handling, and tests.
VERIFY: Run relevant unit/widget/integration/E2E checks.
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 |