What problem does it solve? When scaffolding a new Expo app, developers often struggle to decide where files should live — routes, screens, components, 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 consistently from day one. ## Core Features & Use Cases - Complete project skeleton: A full directory tree covering src/app routes, components/, screens/, server/, utils/, hooks/, and root config files like app.json and eas.json. - Routes-only app directory: Enforces Expo Router conventions where every file in src/app is a route, with screen bodies extracted into screens/ and API routes grouped under app/api/ with +api suffixes. - Platform-specific code patterns: Guidance on splitting components into .ios, .android, .native, and .web variants, plus colocating styles and tests next to source files. - Use Case: You are starting a brand-new Expo app with Expo Router and need to decide where to put a settings screen, a reusable button component, and a server API route — this Skill gives you the exact placement for each. ## Quick Start Use the expo-project-structure skill to lay out the folder structure for my new Expo Router app.
