expo-project-structure

Solid

Framework (OSS). Folder structure for a new Expo app. Use when scaffolding or laying out a new Expo project with Expo Router, or deciding where a file should live in one. For new projects only — never restructure an existing app to match.

Data & Documents 135 stars 6 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 79/100

Stars 20%
71
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Expo Project Structure A starting skeleton for a **new** Expo app — one with no committed folder structure yet. **Apply only to new projects.** If the app already has a layout, follow its existing conventions and leave files where they are — a default to start from, never a standard to enforce or migrate toward. When unsure whether a project is new, ask before moving anything. The whole layout, assembled from the rules below: ``` ├── assets/ ├── scripts/ ├── src/ │ ├── app/ # Expo Router routes ONLY — every file is a route │ │ ├── api/ # server API routes, grouped here │ │ │ ├── user+api.ts │ │ │ └── settings+api.ts │ │ ├── _layout.tsx │ │ ├── _layout.web.tsx # platform-specific layout │ │ ├── index.tsx │ │ └── settings.tsx │ ├── components/ # reusable UI: button, card, table… │ │ ├── table/ # complex component → folder + index.tsx │ │ │ ├── cell.tsx │ │ │ └── index.tsx │ │ ├── bar-chart.tsx │ │ ├── bar-chart.web.tsx # platform-specific variant │ │ └── button.tsx │ ├── screens/ # screen bodies that route files render │ │ ├── home/ │ │ │ ├── card.tsx # used only by Home — not shared │ │ │ └── index.tsx # rendered by src/app/index.tsx │ │ └── settings.tsx │ ├── server/ # server-only helpers used by app/api │ │ ├── auth.ts │ ...

Details

Author
arcboxlabs
Repository
arcboxlabs/linkcode
Created
2 months ago
Last Updated
today
Language
TypeScript
License
NOASSERTION

Similar Skills

Semantically similar based on skill content — not just same category