React Native Orchestrator
Entry skill for React Native UI and interaction craft — independent of how the app is
built or shipped. It routes by what you're crafting (layout, motion, touch, data, screens)
or reviewing (whole-product UI/UX flow, source-of-truth gaps, route/state/API continuity).
The runtime model (New Architecture, Reanimated, navigation, performance) lives in
react-native-core. Toolchain/build/ship belongs to the expo cluster.
Cluster map (routing targets)
react-native-core — RN runtime model: New Architecture (Fabric/TurboModules/JSI), styling approaches, navigation options, the Reanimated + Gesture Handler stack, platform differences, performance, and integrated product-flow audits.react-native-design — styling, navigation, and Reanimated animations; the day-to-day RN UI craft.mobile-touch — gestures, haptic feedback, touch interactions, native-feel micro-animations.sleek-design-mobile-apps — high-level screen/app design ("design a mobile app", build screens) incl. Sleek projects.native-data-fetching — (shared with expo) network requests, React Query/SWR, caching, offline, error handling.
Routing Rules by Intent
- Styling / layout / navigation / animation →
react-native-design (+ react-native-core for the Reanimated/nav model).
- Gestures, haptics, touch feel →
mobile-touch.
- Design a screen / whole app visually →
sleek-design-mobile-apps.
- Whole-product / integrated UI/UX flow audit →
react-native-core integrated-flow reference + react-native-design; add native-data-fetching for API/cache/offline gaps and the expo cluster for Expo Router/toolchain evidence.
- Fetch / cache / sync data →
native-data-fetching.
- Toolchain (EAS build/submit/update, dev client, Expo Router, native modules, SDK upgrade) → expo cluster (
expo-orchestrator).
- Native iOS (SwiftUI, UIKit, HIG) → native-ios cluster (
mobile-ios-design).
Standard Operating Flow
- Identify the craft: layout/motion, touch, screen design, data, or whole-flow review.
- For whole-flow review, read the product contract first: actors, role gates, success states, safety/consent, revenue or token rules, and live-vs-demo boundaries.
- Pull the relevant model from
react-native-core (e.g. Reanimated worklets, list performance, Platform splits, integrated-flow audit checklist).
- Delegate to the spoke(s). If the request implies Expo Router, build, ship, or native module evidence, redirect that part to
expo-orchestrator.
- Return: chosen spoke(s), runtime concerns in play (UI-thread vs JS-thread, New Arch), implementation gaps, verification path, and next action.
Guardrails
See react-native-core. In short: run animations/gestures on the UI thread (Reanimated
worklets + Gesture Handler) — never block the JS thread; animate transforms, not layout, for
60fps; respect prefers-reduced-motion / reduce-motion settings; use Platform/platform-file
splits instead of runtime OS branching where it matters; and virtualize long lists
(FlatList/FlashList) rather than mapping arrays.
For integrated-flow audits, do not start with screen polish. Trace the flow contract from
source of truth to route graph, state authority, API/cache, persistence, recovery states, and
verification evidence. Fixture or mock fallbacks are acceptable only when they are explicitly
labeled as simulator/demo paths and cannot masquerade as production proof.
Loading spokes on demand
To keep CLI startup context lean, this cluster's spokes are not separately registered as skills — only this orchestrator and its *-core are enumerated. When you route to a spoke named above, load it on demand by reading its file:
~/.agents/skill-clusters/skills/<spoke-name>/SKILL.md (or skills/<spoke-name>/SKILL.md inside the skill-clusters repo).
1---2name: react-native-orchestrator3description: Route a React Native craft task to the right spoke — styling/navigation/Reanimated animation, touch/gesture/haptics, data fetching, full screen/app visual design, or integrated product-flow UI/UX audits. USE WHEN building or reviewing React Native UI and interaction (toolchain-agnostic). For the Expo toolchain (EAS, dev client, Expo Router, native modules) hand off to the expo cluster; for native SwiftUI/iOS, the native-ios cluster.4---56# React Native Orchestrator78Entry skill for **React Native UI and interaction craft** — independent of how the app is9built or shipped. It routes by what you're crafting (layout, motion, touch, data, screens)10or reviewing (whole-product UI/UX flow, source-of-truth gaps, route/state/API continuity).11The runtime model (New Architecture, Reanimated, navigation, performance) lives in12`react-native-core`. Toolchain/build/ship belongs to the **expo** cluster.1314## Cluster map (routing targets)1516- `react-native-core` — RN runtime model: New Architecture (Fabric/TurboModules/JSI), styling approaches, navigation options, the Reanimated + Gesture Handler stack, platform differences, performance, and integrated product-flow audits.17- `react-native-design` — styling, navigation, and **Reanimated** animations; the day-to-day RN UI craft.18- `mobile-touch` — gestures, haptic feedback, touch interactions, native-feel micro-animations.19- `sleek-design-mobile-apps` — high-level screen/app **design** ("design a mobile app", build screens) incl. Sleek projects.20- `native-data-fetching` — *(shared with expo)* network requests, React Query/SWR, caching, offline, error handling.2122## Routing Rules by Intent2324- **Styling / layout / navigation / animation** → `react-native-design` (+ `react-native-core` for the Reanimated/nav model).25- **Gestures, haptics, touch feel** → `mobile-touch`.26- **Design a screen / whole app visually** → `sleek-design-mobile-apps`.27- **Whole-product / integrated UI/UX flow audit** → `react-native-core` integrated-flow reference + `react-native-design`; add `native-data-fetching` for API/cache/offline gaps and the **expo cluster** for Expo Router/toolchain evidence.28- **Fetch / cache / sync data** → `native-data-fetching`.29- **Toolchain** (EAS build/submit/update, dev client, Expo Router, native modules, SDK upgrade) → **expo cluster** (`expo-orchestrator`).30- **Native iOS** (SwiftUI, UIKit, HIG) → **native-ios cluster** (`mobile-ios-design`).3132## Standard Operating Flow33341. Identify the craft: layout/motion, touch, screen design, data, or whole-flow review.352. For whole-flow review, read the product contract first: actors, role gates, success states, safety/consent, revenue or token rules, and live-vs-demo boundaries.363. Pull the relevant model from `react-native-core` (e.g. Reanimated worklets, list performance, Platform splits, integrated-flow audit checklist).374. Delegate to the spoke(s). If the request implies Expo Router, build, ship, or native module evidence, redirect that part to `expo-orchestrator`.385. Return: chosen spoke(s), runtime concerns in play (UI-thread vs JS-thread, New Arch), implementation gaps, verification path, and next action.3940## Guardrails4142See `react-native-core`. In short: run animations/gestures on the **UI thread** (Reanimated43worklets + Gesture Handler) — never block the JS thread; animate transforms, not layout, for4460fps; respect `prefers-reduced-motion` / reduce-motion settings; use `Platform`/platform-file45splits instead of runtime OS branching where it matters; and virtualize long lists46(FlatList/FlashList) rather than mapping arrays.4748For integrated-flow audits, do not start with screen polish. Trace the flow contract from49source of truth to route graph, state authority, API/cache, persistence, recovery states, and50verification evidence. Fixture or mock fallbacks are acceptable only when they are explicitly51labeled as simulator/demo paths and cannot masquerade as production proof.5253## Loading spokes on demand5455To keep CLI startup context lean, this cluster's spokes are **not** separately registered as skills — only this orchestrator and its `*-core` are enumerated. When you route to a spoke named above, **load it on demand** by reading its file:5657`~/.agents/skill-clusters/skills/<spoke-name>/SKILL.md` (or `skills/<spoke-name>/SKILL.md` inside the skill-clusters repo).
Sheshiyer