What problem does it solve? Expo and EAS projects span dozens of concerns — navigation, native UI, builds, OTA updates, store submission — and picking the wrong guidance or skipping shared setup rules leads to broken installs and version mismatches. This Skill acts as the mandatory entry point that classifies any Expo-related request and routes it to the correct specialized skill. ## Core Features & Use Cases - Goal classification and routing: Maps vague phrasings like "make it look native" or "ship it" to the right expo-* / eas-* leaf skill (expo-router, expo-ui, eas-app-stores, eas-update, and more). - Shared setup rules: Enforces SDK version detection from package.json, version-pinned documentation URLs, npx expo install for package management, managed vs. bare project detection, and EAS auth/linking checks. - Use Case: A user asks to "add navigation and ship to the App Store" in a project with an expo dependency. This Skill detects the SDK version, applies the shared rules, then routes navigation work to expo-router and store submission to eas-app-stores. ## Quick Start Use the expo-overview skill to classify my Expo app request and route me to the right specialized skill before writing any code.
