What problem does it solve? When scaffolding a new Expo app, developers often struggle to decide where files should live — routes, components, screens, server code, and platform-specific variants can end up scattered or mixed together. This Skill provides a concrete, opinionated folder layout for new Expo projects so structure decisions are made once and consistently. ## Core Features & Use Cases - Complete layout blueprint: A full directory tree covering src/app routes, components/, screens/, server/, hooks/, and utils/, ready to follow when starting a project. - Routes-only app directory: Enforces Expo Router conventions where every file in src/app is a route, with screen bodies extracted into screens/ and reusable UI in components/. - Server code separation: Groups +api routes under app/api/ and shared server helpers in src/server/, keeping secret-reading Node code apart from frontend code. - Platform-specific files: Guidance on .ios, .android, .native, and .web file variants with identical props and a required default file. - Use Case: You just ran create-expo-app and need to decide where a new settings screen, a shared button component, and a server API route should go — this Skill gives you the exact placement rules. ## Quick Start Ask the AI to lay out a new Expo app following the expo-project-structure conventions, placing routes, screens, components, and server code in their designated folders.
