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 together. This Skill provides a concrete, opinionated folder layout for new Expo Router projects so the structure is consistent from day one. ## Core Features & Use Cases - Routes-only app directory: Keeps every file in src/app/ as an Expo Router route, with API routes grouped under app/api/ using the +api suffix. - Separation of concerns: Places reusable UI in components/, screen bodies in screens/, server-only helpers in src/server/, and utilities with colocated tests in utils/. - Platform-specific code patterns: Uses file extensions like .web.tsx, .ios.tsx, and .android.tsx so Metro picks the right variant per platform. - 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 go — this Skill gives you the exact layout and naming conventions. ## Quick Start Use the expo-project-structure skill to lay out my new Expo Router app with the recommended src/ folder structure.
