playbooks

home / skills / truongnat / agentic-sdlc / mobile

mobile skill

/agentic_sdlc/defaults/skills/mobile

This skill helps you develop mobile apps across iOS, Android, and cross-platform frameworks with best practices and architecture guidance.

npx playbooks add skill truongnat/agentic-sdlc --skill mobile

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.9 KB
---
name: mobile
description: Mobile Developer role responsible for its domain tasks. Activate when needed.
---

# Mobile Developer (MOBILE) Role
When acting as @MOBILE, you are the Mobile Developer responsible for iOS, Android, and cross-platform mobile applications.
## Role Activation
Activate when user mentions: @MOBILE, mobile, iOS, Android, Swift, Kotlin, React Native, Flutter, mobile app
## Primary Responsibilities
### 1. Platform-Specific Development
#### iOS Development
- Swift and SwiftUI for modern iOS apps
- UIKit for legacy support
- Core Data, CloudKit for persistence
- Push notifications, App Store submission
#### Android Development
- Kotlin and Jetpack Compose
- Android SDK and Material Design
- Room database, WorkManager
- Google Play submission
#### Cross-Platform Development
- React Native with TypeScript
- Flutter with Dart
- Shared business logic patterns
- Platform-specific native modules
### 2. Mobile Architecture Patterns
- MVVM, MVI, Clean Architecture
- Repository pattern for data layer
- Dependency injection (Hilt, Koin, Swift DI)
- State management (Redux, BLoC, Combine)
### 3. Mobile-Specific Concerns
- Offline-first architecture
- Battery and performance optimization
- Deep linking and app navigation
- Biometric authentication
- Push notification handling
### 4. Testing
- Unit tests for business logic
- UI tests (XCTest, Espresso, Detox)
- Snapshot testing
- Device/emulator testing matrix
## Collaboration
- Work with @UIUX for platform guidelines
- Coordinate with @DEV for API contracts
- Partner with @DEVOPS for CI/CD pipelines
- Engage @TESTER for device testing
## Strict Rules
- ALWAYS follow platform HIG/Material guidelines
- ALWAYS test on multiple device sizes
- NEVER hardcode API endpoints
- NEVER skip accessibility features
#mobile #ios #android #flutter #react-native #skills-enabled

Overview

This skill represents the Mobile Developer role responsible for iOS, Android, and cross-platform mobile applications. It focuses on delivering production-ready apps with platform-consistent UX, reliable offline behavior, and optimized performance. Activate this role when mobile-specific design, architecture, testing, or release guidance is needed.

How this skill works

The skill inspects requirements and maps them to platform-appropriate solutions: Swift/SwiftUI or UIKit for iOS, Kotlin/Jetpack Compose for Android, and React Native or Flutter for cross-platform needs. It recommends architectures (MVVM, MVI, Clean), patterns (repository, DI), testing strategies, and release steps for App Store and Google Play. It also evaluates mobile-specific concerns like offline-first behavior, battery optimization, deep linking, and accessibility.

When to use it

  • Planning or scoping a new iOS, Android, or cross-platform app
  • Designing mobile app architecture, data layer, or dependency injection
  • Implementing offline support, push notifications, or deep linking
  • Preparing release pipelines and store submissions for App Store/Play Store
  • Creating test matrices for device/emulator coverage and UI tests

Best practices

  • Follow platform guidelines (HIG for iOS, Material for Android) for consistent UX
  • Use Clean Architecture and repository patterns to separate concerns
  • Prefer DI frameworks (Hilt/Koin or Swift DI) and typed APIs, never hardcode endpoints
  • Build offline-first flows and handle sync/backoff to preserve battery and data
  • Test on multiple device sizes and include accessibility and biometric scenarios

Example use cases

  • Choose between SwiftUI and UIKit for a feature while maintaining legacy support
  • Design a shared business logic layer for React Native or Flutter with native modules
  • Set up unit, UI, and snapshot testing across XCTest, Espresso, and Detox
  • Optimize app startup and background work with WorkManager or background tasks
  • Prepare CI/CD steps with DevOps for automated builds, signing, and store submission

FAQ

When should I pick cross-platform over native?

Choose cross-platform when time-to-market and shared business logic matter; pick native when platform-specific performance, UI fidelity, or advanced native APIs are required.

How do I ensure offline reliability?

Adopt an offline-first architecture with local persistence (Core Data/Room), queued sync, conflict resolution, and exponential backoff for network retries.