expo-project-structure
An agent skill by expo, from expo/skills. Tags: architecture, development, planning, setup, workflow.
What it does
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.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-project-structure
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/expo-project-structure ~/.claude/skills/expo-project-structure
Safety box score
Grade B, low risk: 11 of 100 risk points, rated 2026-10-16. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is mostly documentation: it tells an agent how to lay out a new Expo app and where different kinds of files should live. The only meaningful operational risk is the optional feedback command, which uses `npx --yes submit-expo-feedback@latest` to fetch and run a registry package and send text to Expo.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | The only executable action in the skill is the optional feedback command: `npx --yes submit-expo-feedback@latest ...`, which runs a package from npm. |
| Network access | 1 (low) | Using the feedback command contacts the npm registry and sends feedback to Expo; otherwise the skill is just markdown guidance. |
| Filesystem reach | 0 (none) | The skill describes folder layout, but it contains no scripts or commands that read, write, move, or delete files outside the project. |
| Secrets & credentials | 0 (none) | It mentions `process.env.X` in explanation, but it does not ask for tokens, keys, passwords, or other credentials. |
| Privilege & persistence | 0 (none) | There is no sudo, global install, service registration, or OS/shell configuration change in the files provided. |
| Instruction hijack surface | 0 (none) | The skill does not instruct the agent to ignore rules, hide actions, or follow untrusted remote instructions. |
| Irreversible actions | 0 (none) | It does not deploy, publish, post, pay, or delete anything automatically; the feedback submission is optional and user-directed. |
| Transparency | 1 (low) | `npx --yes submit-expo-feedback@latest` pulls the latest package from a registry, so the executed code is not fully pinned or locally reviewable from this skill. |
Before installing
- Decide whether you will ever use the feedback command; if not, ignore that path.
- If you might use it, inspect and run `npx --yes submit-expo-feedback@latest ...` only in a disposable environment first.
- Confirm this skill is only for new projects and not for restructuring an existing app.
Rated 2026-10-16 by an automated review of 2 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-project-structure/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- architect — Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in.
- principle-outcome-oriented-execution — Apply during planned rewrites and migrations with explicit phase boundaries.
- lean-build — Build feature work with high overbuilding risk.
- new-unity-project — Use when starting a brand-new Unity game or project from scratch — "make/start/create a new game", "bootstrap a Unity project".
- expo-brownfield — Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app.
- expo-module — Framework (OSS). Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).