When to activate
- Designing navigation structure for a new mobile app
- Choosing state management approach (Redux, Zustand, Riverpod, etc.)
- Defining data layer architecture (API clients, caching, persistence)
- Setting up module boundaries and feature-based folder structure
- Migrating from monolithic to modular architecture
When NOT to use
- For backend API architecture (use API Developer Stack)
- For web app architecture
- For UI component design (framework-specific skills)
Instructions
- Define app complexity tier. Simple (1-5 screens), Medium (5-20 screens, 2-3 features), Complex (20+ screens, deep linking, offline).
- Choose navigation pattern. Stack (simple), Tab + Stack (medium), Drawer + Tab + Stack (complex). Map user flows.
- Select state management. Local state for UI, global store for shared data, server state for API. Match to framework (Zustand/Redux for RN, Riverpod/Bloc for Flutter, @Observable for SwiftUI).
- Design data layer. Repository pattern: API client → cache (in-memory + persistent) → repository → view model → UI.
- Define module boundaries. Feature-based folders:
features/auth/, features/feed/, features/profile/. Shared: core/, shared/ui/, shared/utils/.
- Plan deep linking. Map URL schemes to screens:
app://profile/123 → ProfileScreen(userId: "123").
- Document architecture decisions. ADRs for each major choice with alternatives considered.
Example
Architecture Decision: Medium-complexity e-commerce app
Navigation: Bottom tabs (Home, Search, Cart, Profile) + Stack per tab
State: Zustand (global: cart, auth) + React Query (server: products, orders)
Data: API client (axios) → React Query cache → MMKV persistence
Modules:
features/auth/ — Login, register, forgot password
features/catalog/ — Product list, detail, search
features/cart/ — Cart, checkout, payment
features/profile/ — Account, orders, settings
core/ — Navigation, theme, i18n, analytics
shared/ — UI components, utils, types
1---2name: app-architecture3description: Design mobile app architecture — navigation patterns, state management, data layer, and module boundaries4allowed-tools: [Read, Write, Grep]5effort: high6metadata:7 source: https://skillmd.com/skills/uitbreidenos/app-architecture8---910## When to activate1112- Designing navigation structure for a new mobile app13- Choosing state management approach (Redux, Zustand, Riverpod, etc.)14- Defining data layer architecture (API clients, caching, persistence)15- Setting up module boundaries and feature-based folder structure16- Migrating from monolithic to modular architecture1718## When NOT to use1920- For backend API architecture (use API Developer Stack)21- For web app architecture22- For UI component design (framework-specific skills)2324## Instructions25261. **Define app complexity tier.** Simple (1-5 screens), Medium (5-20 screens, 2-3 features), Complex (20+ screens, deep linking, offline).272. **Choose navigation pattern.** Stack (simple), Tab + Stack (medium), Drawer + Tab + Stack (complex). Map user flows.283. **Select state management.** Local state for UI, global store for shared data, server state for API. Match to framework (Zustand/Redux for RN, Riverpod/Bloc for Flutter, @Observable for SwiftUI).294. **Design data layer.** Repository pattern: API client → cache (in-memory + persistent) → repository → view model → UI.305. **Define module boundaries.** Feature-based folders: `features/auth/`, `features/feed/`, `features/profile/`. Shared: `core/`, `shared/ui/`, `shared/utils/`.316. **Plan deep linking.** Map URL schemes to screens: `app://profile/123` → ProfileScreen(userId: "123").327. **Document architecture decisions.** ADRs for each major choice with alternatives considered.3334## Example3536```37Architecture Decision: Medium-complexity e-commerce app3839Navigation: Bottom tabs (Home, Search, Cart, Profile) + Stack per tab40State: Zustand (global: cart, auth) + React Query (server: products, orders)41Data: API client (axios) → React Query cache → MMKV persistence42Modules:43 features/auth/ — Login, register, forgot password44 features/catalog/ — Product list, detail, search45 features/cart/ — Cart, checkout, payment46 features/profile/ — Account, orders, settings47 core/ — Navigation, theme, i18n, analytics48 shared/ — UI components, utils, types49```