Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When scaffolding a brand-new Expo app with Expo Router, or deciding where a file should live in such a project. Never apply to existing apps.
src/-based folder skeleton (app/, components/, screens/, server/, utils/, hooks/).app/, reusable components in kebab-case, screen bodies in screens/, server API routes under app/api/ + server/, platform-specific file splits, and colocated styles/tests.A clean, convention-aligned starting structure for a new Expo project that separates config, routes, UI, server, and tests without migrating existing code.
Use Cases
A developer runs `npx create-expo-app` and starts a greenfield Expo Router project. They are unsure how to organize routes, shared UI, and server API code. Using this skill, they adopt the `src/`-based skeleton with `app/` for routes only, `components/` for reusable UI, `screens/` for screen bodies, and `app/api/` + `server/` for backend. This prevents messy colocation and sets a scalable foundation from day one.
A team lead reviews a junior dev's new Expo project and notices API routes mixed with screens and no clear server folder. They invoke this skill to show the canonical structure: group API under `app/api/`, keep `src/server/` for helpers, and split platform code into `.web.tsx` variants. The junior learns where each file belongs, reducing review churn and keeping the codebase consistent as it grows.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File