What problem does it solve? When starting a new Expo app, developers often struggle to decide where files should live, especially with Expo Router's file-based routing where every file in the app directory becomes a route. This Skill provides a proven folder layout so new projects start with clear separation between routes, screens, components, and server code. ## Core Features & Use Cases - Routes-only app directory: Keeps src/app/ strictly for Expo Router routes, with screen bodies moved to src/screens/ so complex UI has a proper home. - Server code separation: Groups API routes under app/api/ with shared server-only helpers in src/server/, keeping Node-side code apart from frontend code. - Platform-specific files and colocation: Covers .ios/.android/.web file variants, colocated styles and tests, and kebab-case component naming matching the default template. - Use Case: You just ran create-expo-app and need to decide where a new settings screen, a reusable button, and a /api/user endpoint should go. This Skill gives you the exact layout and the reasoning behind each placement. ## Quick Start Use the expo-project-structure skill to lay out my new Expo Router app with the recommended src directory structure.
