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", "make it look native", or "add navigation" to the correct leaf skill such as eas-app-stores, expo-ui, or expo-router. - 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 "I'm new to Expo, where do I start?" The Skill scaffolds a project with create-expo-app, detects the SDK version from package.json, then routes to expo-project-structure and expo-native-ui for the actual build work. ## Quick Start Use the expo-overview skill to classify my Expo app request and route me to the right skill before writing any code.
