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 Expo work, classifies the user's goal, and routes to the right expo-* or eas-* leaf skill. ## Core Features & Use Cases - Goal Classification and Routing: Translates casual phrasings like "ship it" or "make it look native" into concrete goals and maps them to the correct leaf skill such as eas-app-stores, expo-router, or expo-ui. - Shared Setup Rules: Centralizes cross-cutting rules every Expo skill needs, including SDK version detection, version-pinned documentation URLs, npx expo install for packages, managed vs. bare project detection, and EAS authentication checks. - Use Case: A user says "add navigation to my app and ship to the App Store." This Skill confirms the expo dependency, detects the SDK version, then routes navigation work to expo-router and release work to eas-app-stores. ## Quick Start Use the expo-overview skill to classify my Expo app request and route me to the right expo or eas skill before writing any code.