From sage
Provides integration patterns for Expo + React Navigation/Expo Router + Zustand + MMKV + TanStack Query in React Native apps. Covers auth flows, persistence, offline caching, project structure, and anti-patterns.
npx claudepluginhub xoai/sageThis skill uses the workspace's default tool permissions.
**Layer 3 — Stack Composition**
Provides production architecture patterns for React Native apps with Expo Router, navigation, native modules, offline sync, state management, and project structure for mobile development.
Provides production-ready patterns for React Native development with Expo, covering navigation, state management, native modules, and offline-first architecture. Useful for new projects, complex navigation, and mobile optimization.
Builds production React Native apps with Expo, covering navigation, state management, native modules, offline sync, and cross-platform patterns. Use for new projects, native integrations, and mobile architecture.
Share bugs, ideas, or general feedback.
Layer 3 — Stack Composition
Integration patterns for the most common React Native stack: Expo + Expo Router/React Navigation + Zustand + MMKV + TanStack Query.
Each tool's docs explain how it works alone. They don't explain how they work together: where the Zustand store plugs into the navigation guard, how MMKV persistence integrates with Zustand hydration, how TanStack Query's cache interacts with offline state, how Expo Router layouts compose with auth flows.
These integration seams are where bugs live. This pack documents the gaps.
| Type | Files | Coverage |
|---|---|---|
| Integration | 4 | Expo Router + auth, Zustand + MMKV persistence, TanStack Query + offline, project structure |
| Anti-patterns | 3 | Auth in wrong layer, store hydration race, query key chaos |
| Constitution | 1 | 4 stack integration principles |