mobile-platform-architect
Architects cross-platform and native mobile applications, providing guidance on state management, navigation, and platform-specific best practices for React Native, Flutter, iOS, and Android.
Best use case
mobile-platform-architect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Architects cross-platform and native mobile applications, providing guidance on state management, navigation, and platform-specific best practices for React Native, Flutter, iOS, and Android.
Teams using mobile-platform-architect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/mobile-platform-architect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How mobile-platform-architect Compares
| Feature / Agent | mobile-platform-architect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Architects cross-platform and native mobile applications, providing guidance on state management, navigation, and platform-specific best practices for React Native, Flutter, iOS, and Android.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Mobile Platform Architect
You are a Lead Mobile Developer with expertise in both Cross-Platform (React Native, Flutter) and Native (Swift/Kotlin) ecosystems. You design apps that feel native, perform well, and scale.
## Core Competencies
- **Frameworks:** React Native (Expo), Flutter, SwiftUI, Jetpack Compose.
- **Architecture:** MVVM, Clean Architecture, Redux/MobX/Bloc/Riverpod.
- **Native Integration:** Bridging native modules, handling permissions, background tasks.
- **UX/UI:** Human Interface Guidelines (Apple) and Material Design (Google).
## Instructions
1. **Select the Stack:**
- Analyze the requirements. If the app needs complex 3D or heavy native APIs -> Native. If it's a CRUD app -> Cross-platform.
- justify the choice (e.g., "Choose React Native because the team already knows React").
2. **Architectural Structure:**
- Define the folder structure.
- **State Management:** Recommend a library based on complexity (e.g., Context API for simple, Redux Toolkit/Zustand for complex).
- **Navigation:** Suggest the standard router (React Navigation, GoRouter).
3. **Performance Optimization:**
- **React Native:** Discuss FlatList optimization, Memoization, Hermes engine.
- **Flutter:** Discuss widget rebuilds, const constructors.
- **General:** Image caching, minimizing over-draw.
4. **Device Features:**
- Explain how to handle: Push Notifications, Geolocation, Offline Storage (AsyncStorage/SQLite/Realm), Camera.
5. **Deployment:**
- Briefly mention CI/CD (Fastlane) and store submission guidelines (App Store Review Guidelines).
## Tone
- Practical and user-centric. Focus on the "feel" of the application (60fps is non-negotiable).Related Skills
recursive-systems-architect
Designs self-referential and recursive systems that examine, modify, or generate themselves, including metacognitive architectures and strange loops.
posse-distribution-architecture
Implement POSSE (Publish on Own Site, Syndicate Elsewhere) content distribution with canonical URLs, cross-platform syndication, backfeed collection, and resilient delivery. Covers multi-platform publishing automation and IndieWeb patterns. Triggers on POSSE implementation, content syndication architecture, or IndieWeb publishing requests.
oauth-flow-architect
Implements OAuth 2.0 and OpenID Connect authentication flows with proper security, token management, and common provider integrations.
knowledge-architecture
Design knowledge systems using ontological principles—organizing by what things ARE rather than arbitrary hierarchies. Use when structuring personal knowledge bases, designing documentation systems, creating cross-domain linking patterns, building the {OS.me} ecosystem, or architecting information that reveals rather than obscures essential nature. Triggers on knowledge management, documentation architecture, information ontology, or systematic organization of complex domains.
github-profile-architect
Architects high-impact GitHub Profile READMEs using the "Special Repository" mechanism. optimizing for recruitment signaling, visual semiotics, and dynamic automation (Actions, WakaTime).
dotfile-systems-architect
Guides the creation of a "Minimal Root" home directory using the XDG Base Directory specification and a Bare Git Repository. Manages config separation, secrets, and cross-platform syncing.
data-pipeline-architect
Designs ETL/ELT data pipelines with proper extraction, transformation, and loading patterns, including orchestration, error handling, and data quality validation.
community-platform-patterns
Build community platforms with user profiles, discussion forums, event management, and moderation tools. Covers real-time features, content moderation, and community engagement patterns. Triggers on community platform development, forum design, or social feature requests.
taxonomy-modeling-design
Phase 2 of the pentaphase structural-overhaul protocol. Classifies entities, standardizes attributes, establishes relationships, and designs the access framework. Use when the user invokes phase 2 of an overhaul, asks to "design the taxonomy" or "model the structure", or has completed a landscape audit and is ready to redesign. Consumes phase-1-landscape-report.md; produces phase-2-taxonomy-model.md.
systemic-ingestion-normalization
Phase 4 of the pentaphase structural-overhaul protocol. Purges redundancies, enriches and aligns legacy entities to the new schema, executes phased ingestion into the new environment, and audits integrity. Use when the user invokes phase 4 of an overhaul, asks to "migrate the data" or "ingest into the new system", or has a configured environment ready to accept legacy entities. Consumes phase-3-environment-spec.md; produces phase-4-ingestion-report.md.
system-environment-configuration
Phase 3 of the pentaphase structural-overhaul protocol. Translates the taxonomy model into objective technical criteria, evaluates candidate mechanisms or frameworks, instantiates the chosen architecture, and programs validation rules. Use when the user invokes phase 3 of an overhaul, asks to "select a system" or "configure the environment", or has a taxonomy model and is ready to choose technology. Consumes phase-2-taxonomy-model.md; produces phase-3-environment-spec.md.
pentaphase-orchestrator
Threads the full five-phase structural-overhaul protocol — landscape discovery, taxonomy design, environment configuration, systemic ingestion, governance evolution — for any substrate the user names. Use when the user requests a structural overhaul, system redesign, or end-to-end restructuring of a documentation system, asset registry, code monorepo, knowledge base, or operational workflow; or when they explicitly invoke the pentaphase methodology. Coordinates handoffs between phase-skills and seats validation gates between phases.