What problem does it solve? Expo and EAS work spans many specialized skills, and picking the wrong one from project files alone leads to incorrect guidance. This Skill acts as the mandatory entry point that confirms a task is actually Expo work, classifies the user's real goal, and routes to the right expo-* or eas-* leaf skill. ## Core Features & Use Cases - Goal classification and routing: Maps casual phrasings like "ship it" or "make it look native" to the correct leaf skill such as eas-app-stores, expo-ui, or expo-router. - Shared setup rules: Centralizes cross-cutting rules like detecting the SDK version, using version-pinned docs, installing packages with npx expo install, and checking EAS auth and project linking. - Use Case: A user says "add navigation to my app and ship to the App Store." This Skill confirms the project has an expo dependency, detects the SDK version, then routes navigation work to expo-router and release work to eas-app-stores. ## Quick Start Use expo-overview to classify my Expo task and route me to the right skill before writing any code.
