ericrisco/rsc-harness / skills/expo
expo
VerifiedUse when shipping a React Native app with Expo — EAS Build/Submit/Update, eas.json profiles and channels, config plugins, prebuild/CNG, runtime-version policy, OTA updates that never land, SDK upgrades, the New Architecture. NOT RN UI, navigation or native-module authoring (that is `react-native`), NOT a Dart app (that is `flutter`).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.2 KB |
| evals/README.md | markdown | 959 B |
| evals/cases.yaml | config | 3.3 KB |
| references/config-plugins.md | markdown | 4.4 KB |
| references/eas-update.md | markdown | 5.5 KB |
| scripts/verify.shexecutable | script | 5.4 KB |
evals/cases.yaml
View on GitHubskill: expo
should_trigger:
- prompt: "Set up eas.json with dev, preview, and production profiles and push an iOS build to TestFlight."
why: "Core EAS Build + Submit + build-profile configuration — the heart of this skill."
- prompt: "My EAS Update published fine but none of the devices ever get the new JS bundle."
why: "Non-obvious; the runtime-version exact-match footgun, the #1 reason updates silently never apply."
- prompt: "How do I add a custom AndroidManifest permission without ejecting or editing native code?"
why: "Config plugin / CNG — declaring native config in JS instead of hand-editing android/."
- prompt: "com configuro EAS Update amb branques i canals per a staging i producció?"
why: "Catalan; channel/branch model for staged OTA rollouts."
- prompt: "expo-doctor says a dependency isn't New-Architecture compatible and newArchEnabled is gone from app.json — how do I ship?"
why: "Non-obvious; New Arch is mandatory since SDK 55 with no legacy fallback, so a non-compliant dep is a hard blocker, not a flag flip."
- prompt: "Write an EAS Workflow that builds Android then submits to the Play Store."
why: "EAS Workflows YAML with build->submit chaining via needs/outputs."
- prompt: "subir la app a la Play Store con EAS y configurar el runtimeVersion con fingerprint"
why: "Spanish; EAS Submit plus runtime-version policy choice."
should_not_trigger:
- prompt: "Build a custom swipeable card list with React Native Reanimated."
route_to: "react-native"
why: "Pure RN UI/animation, no EAS/Expo toolchain or shipping concern."
- prompt: "Set up a GitHub Actions workflow to run my Jest tests on every push."
route_to: "github-actions"
why: "Generic CI unrelated to EAS Workflows; only route here if the user explicitly wants EAS CI."
- prompt: "How do I structure a Flutter app with Riverpod and go_router?"
route_to: "flutter"
why: "Different ecosystem (Dart), not React Native / Expo."
- prompt: "Write a native Swift widget extension for iOS."
route_to: "swift-ios"
why: "Native-Swift-only work with no Expo/CNG angle."
- prompt: "Memoize this React component so it stops re-rendering on every parent update."
route_to: "react"
why: "Web/component performance, no mobile shipping or native config."
capability:
- scenario: "I have an Expo SDK 55 app. Configure eas.json for preview and production, set up EAS Update so I can ship JS fixes safely, and give me the build and submit commands."
must_include:
- "eas.json with a build.production profile + channel mapping and a preview profile with distribution internal"
- "runtimeVersion fingerprint policy recommended (or appVersion), with the exact-match rule explained: an update applies only when BOTH platform AND runtimeVersion match exactly"
- "explicit commands: eas build -p ios --profile production and eas submit -p ios --profile production"
- "eas update --branch production --message <msg> for JS-only OTA, noting native changes need a new build"
- "warning never to hand-edit ios/ or android/ (use a config plugin / prebuild --clean) and never to commit a keystore/.p12/.mobileprovision"
- "note that the New Architecture is mandatory since SDK 55 (Legacy Architecture removed, newArchEnabled deleted from app.json) so the app is already on New Arch"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |