What problem does it solve? When starting a new Expo app, developers often struggle to decide where files should live — routes, components, screens, server code, and tests can end up scattered or mixed into the routing directory. This Skill provides a clear, opinionated folder layout so new projects start with a maintainable structure from day one. ## Core Features & Use Cases - Routes-only app directory: Keeps src/app/ strictly for Expo Router routes, with screen bodies moved to src/screens/ and reusable UI in src/components/. - Server code separation: Groups API routes under app/api/ with shared server-only helpers in src/server/, keeping secret env vars away from frontend code. - Platform-specific files and colocation: Covers .ios/.android/.web file variants, colocated tests, and colocated styles. - Use Case: You are scaffolding a brand-new Expo app with Expo Router and need to decide where a new settings screen, a shared button component, and a server API route should each live — this Skill gives you the exact placement rules. ## Quick Start Ask the agent to lay out a new Expo project using the expo-project-structure conventions for routes, screens, components, and server code.
