expo-orchestrator
Skill8 starsChanged 3 months agoMITView on GitHub
Expo + React Native cross-platform mobile app development orchestrator — workflow selection (managed/bare/dev-client), project setup, eas profile discipline, release strategy. Triggers on expo, react native, eas, mobil, app store, play store, ios, android, app.json, eas.json, prebuild, expo-router, expo-modules.
- Installs packages
In this repository63 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ai-automationSkill
- consultingSkill
- contentSkill
- customer-successSkill
- data-analyticsSkill
- designSkill
- design-tokensSkill
- developmentSkill
- devopsSkill
- ecommerceSkill
- emailSkill
- expo-app-configSkill
- expo-config-pluginSkill
- expo-dev-clientSkill
- expo-eas-buildSkill
- expo-eas-submitSkill
- expo-eas-updateSkill
- expo-modulesSkill
- expo-notificationsSkill
- expo-prebuildSkill
- expo-routerSkill
- expo-troubleshootingSkill
- financeSkill
- frontend-tasteSkill
- marketingSkill
- market-researchSkill
- mobileSkill
- pentest-adSkill
- pentest-apiSkill
- pentest-bizlogicSkill
- pentest-bugbountySkill
- pentest-cicdSkill
- pentest-cloudSkill
- pentest-credentialsSkill
- pentest-ctfSkill
- pentest-detectionSkill
- pentest-engagementSkill
- pentest-exploit-chainSkill
- pentest-forensicsSkill
- pentest-llmSkill
- pentest-malwareSkill
- pentest-mobileSkill
- pentest-opsec-evidenceSkill
- pentest-orchestratorSkill
- pentest-privescSkill
- pentest-reconSkill
- pentest-reportSkill
- pentest-socialSkill
- pentest-stigSkill
- pentest-threat-modelSkill
- pentest-webSkill
- pentest-wirelessSkill
- productivitySkill
- productSkill
- salesSkill
- security-checkSkill
- securitySkill
- seo-crawl-budgetSkill
- seoSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 112
When a new project or feature arrives, ask first:
- Distinctive: line 120
Don't make a recommendation without this information — the recommended workflow changes.
- Distinctive: line 130
Always verify user intent.
- Distinctive: line 134
When you make a recommendation:
- Distinctive: line 139
Next step: when to move to which skill
- Very specific: line 143
Expo SDK + package version mismatch: verify with npx expo install --check, then fix
- Very specific: line 144
EAS project ID missing: run eas init, check extra.eas.projectId in app.json
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
expo-orchestrator
The main orchestrator for Expo CLI + EAS-based React Native projects. Guides workflow selection, project setup, package selection, and release strategy. Routes to the other expo-* skills.
What It Does
- Workflow selection: a trade-off matrix for the Managed / Bare / Dev Client decision
- Project setup:
npx create-expo-app+ template selection (default/tabs/bare-minimum) - Package selection: a list of critical Expo SDK packages + alternatives evaluation
- EAS account connection:
eas login,eas whoami, project ID management - Release planning: TestFlight/internal track → production flow
- Skill routing: subcategory selection and in-family delegation
Routing Matrix
| Question / Situation | Which skill? |
| File-based routing, deep linking, layout | expo-router |
eas build profile setup, credentials | expo-eas-build |
| App Store / Play Store submit | expo-eas-submit |
| OTA update, channel, runtime version | expo-eas-update |
withInfoPlist, withAndroidManifest plugin | expo-config-plugin |
| Managed → bare transition, prebuild | expo-prebuild |
| Writing Swift/Kotlin native modules | expo-modules |
| Dev build vs Expo Go decision | expo-dev-client |
| Push notification (FCM/APNs) | expo-notifications |
app.json / app.config.ts settings | expo-app-config |
| Cache, version mismatch, build errors | expo-troubleshooting |
Workflow Selection Matrix
Managed Workflow
When: quick prototyping, no need to write native code, Expo SDK packages suffice, OTA updates are critical. Limit: you can't use 3rd-party native libs (only those a config plugin supports); EAS Build is required for the App Store.
Bare Workflow
When: writing native modules, a 3rd-party iOS/Android SDK is required, custom build steps, familiarity with Xcode/Android Studio. Limit: Expo Go won't work (dev-client required), native upgrades are on you, OTA updates need EAS Update + runtime-version discipline.
Dev Client (middle ground)
When: most of the managed advantages (OTA, EAS) + a few native modules. The default recommendation in modern Expo.
Command: npx expo install expo-dev-client && eas build --profile development
Typical Flow (from scratch to production)
- Create the project
npx create-expo-app@latest MyApp --template default cd MyApp - EAS account connection
npm install -g eas-cli eas login eas init # assigns the project ID to app.json - Dev client (recommended)
→ thenpx expo install expo-dev-client eas build --profile development --platform allexpo-dev-clientskill - App config & router
app.json/app.config.ts: bundle ID, version, scheme →expo-app-config- File-based router:
app/_layout.tsx+app/(tabs)/index.tsx→expo-router
- Build profiles (
eas.json)- development / preview / production →
expo-eas-build
- development / preview / production →
- OTA updates
eas update:configure, channels, runtime versions →expo-eas-update
- Store submit
eas submit --platform ios/android→expo-eas-submit
Recommended Packages (default setup)
npx expo install \
expo-router expo-dev-client \
expo-constants expo-linking expo-status-bar \
expo-splash-screen expo-system-ui \
react-native-safe-area-context react-native-screensAs needed:
- Auth:
expo-auth-session,expo-secure-store - Notifications:
expo-notifications→expo-notificationsskill - Media:
expo-image,expo-av,expo-image-picker - Storage:
@react-native-async-storage/async-storage - Database:
expo-sqlite
Up-Front Information Gathering (at the start of every engagement)
When a new project or feature arrives, ask first:
- Workflow status: managed / bare / dev-client?
- Are the EAS account and project ID set up?
- Platform target: iOS / Android / web / all?
- Distribution strategy: internal / TestFlight / production?
- Is an OTA strategy needed? (it speeds the release cycle)
- Is a native module needed? (it exceeds the managed limit)
Don't make a recommendation without this information — the recommended workflow changes.
Hard Refusal
Red list for this skill:
- Violating app store review rules (privacy, IAP bypass, deceptive UI)
- Jailbreak/root detection bypass
- Premium content bypass-for-gain
- Unauthorized reverse engineering of other apps
Always verify user intent. No unauthorized targets.
Output Format
When you make a recommendation:
- Workflow decision + rationale (1-2 lines)
- Command sequence (copy-paste ready)
- Recommended skill (subcategory)
- Risks and decisions: who owns native upgrades, is OTA needed, cost
- Next step: when to move to which skill
Common Failure Patterns
- Expo SDK + package version mismatch: verify with
npx expo install --check, then fix - EAS project ID missing: run
eas init, checkextra.eas.projectIdin app.json - iOS bundle ID change: renew provisioning profile + push cert —
expo-eas-build - Android upload key lost: is EAS reading the credentials, there should be a backup —
expo-eas-build - Metro bundler cache:
npx expo start --clearorwatchman watch-del-all
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

