Expo orchestrator
Route an Expo task to the right spoke across the app lifecycle — dev environment (dev client, NativeWind), Expo Router app-building, in-app API routes, native modules, EAS build/submit/update, and SDK upgrades. USE WHEN building or shipping an Expo / React Native app with the Expo toolchain but the specific step isn't named. For RN UI/animation/gesture craft that isn't Expo-specific, hand off to the react-native cluster.From its SKILL.md
npx -y skills add Sheshiyer/skill-clusters --skill expo-orchestratorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.6 KB, 789 tokens by cl100k_base, as published. Nobody here has run it
Expo Orchestrator
Entry skill for the Expo toolchain. It locates the task in the Expo lifecycle (set up →
build UI → add native/server → ship via EAS → maintain) and delegates. The platform model —
EAS, app config + config plugins, Expo Go vs dev client vs prebuild/CNG, SDK version policy —
lives in expo-core; read it before changing native config or upgrading.
Cluster map (routing targets)
expo-core— EAS (Build/Submit/Update/Hosting),app.json/app.config, config plugins, managed↔bare spectrum, SDK versioning.expo-dev-client— build & distribute a custom dev client (local / TestFlight) beyond Expo Go.expo-tailwind-setup— Tailwind v4 + NativeWind v5 styling for universal RN.building-native-ui— building app screens with Expo Router: fundamentals, components, navigation, animations, native tabs.expo-api-routes— server API routes in Expo Router + EAS Hosting.expo-module— native modules/views via the Expo Modules API (Swift/Kotlin/TypeScript).expo-cicd-workflows— CI for EAS (build/submit pipelines).expo-deployment— release: EAS Build → Submit → Update (OTA).upgrading-expo— SDK upgrades and dependency alignment.native-data-fetching— (shared with react-native) fetch/React Query/SWR, caching, offline.
Routing Rules by Intent
- Dev environment →
expo-dev-client(need native modules / leaving Expo Go),expo-tailwind-setup(styling). - Build screens & navigation →
building-native-ui(Expo Router). - In-app backend →
expo-api-routes. - Drop to native (Swift/Kotlin) →
expo-module. - Ship it →
expo-cicd-workflows+expo-deployment(EAS). Confirm the SDK/runtime version first (expo-core). - Data layer →
native-data-fetching. - Upgrade SDK →
upgrading-expo. - RN craft that isn't Expo-specific (Reanimated, gestures/haptics, pure RN styling/nav, screen design) → react-native cluster (
react-native-orchestrator).
Standard Operating Flow
- Place the task in the lifecycle (setup → UI → native/server → ship → maintain).
- If it touches native config, EAS, or SDK version, pull the model from
expo-corefirst. - Delegate; for "ship" asks, sequence build → submit → update and confirm signing/version.
- Return: chosen spoke(s), EAS/config implications, target platform(s), next action.
Guardrails
See expo-core. In short: keep the SDK version the source of truth (it pins the RN version
and native deps — don't mix); prefer config plugins over manual native edits so prebuild stays
reproducible; confirm credentials/identifiers before an EAS Submit; treat a managed→bare
ejection as a one-way decision worth stating.
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).
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.