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.
What this skill does
# 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 in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.