Skip to content
Expo Development Foundation
Esc
↑↓navigate↵open⌘Jpreview
On this page

Quickstart

Install the Expo Development Foundation skills and start a routed session.

Prerequisites

  • Clone this repository.
  • Node.js 22.13 or newer.
  • Python 3.

1. Choose one installation strategy

Full vendored snapshot

Install the foundation-owned skills and local vendored copies of official Expo skills for reproducible offline routing:

./Scripts/install-skills.sh --tier all

Foundation-only plus canonical Expo skills

Keep Expo’s upstream skills canonical and install only this repository’s router and workflows:

npx skills@latest add expo/skills --skill '*'
./Scripts/install-skills.sh --tier foundation

Use --target-dir "$HOME/.agents/skills" with either strategy when that is the explicit directory configured for your workspace. Installing into a directory does not prove host discovery.

2. Check the same target and tier

For the full snapshot:

./Scripts/install-skills.sh --status --tier all

For foundation-only, use --status --tier foundation. Repeat the same --target-dir if you supplied one during installation.

3. Copy a prompt

Audit an existing app:

Use $expo-development-foundation to audit this existing Expo app at standard depth. Start with project orientation, remain read-only, cite file evidence for every finding, include design and accessibility when UI is present, run only safe local verification, and report skipped checks plus residual risk.

Create a new app:

Use $expo-development-foundation to create a new Expo app from this request. Route through $expo-bootstrap, choose only the required child skills, prefer Expo Go for compatible JavaScript-only work, and do not run EAS or other cloud actions without explicit authorization.

Change an existing feature:

Use $expo-development-foundation for this existing Expo app. Orient first, shortlist only the skills needed for the requested change, preserve the current architecture, implement only because this prompt authorizes the requested change, and close with $expo-verify.

4. Expect this first response

The router should report:

  • workspace classification;
  • a stack card for an existing app;
  • an ordered, focused skill shortlist; and
  • an explicit proceed or stop boundary based on authorization.

Maintaining the foundation

These checks are for maintainers, not the beginner install path:

npm run verify

The aggregate command clean-installs both lockfiles, verifies the catalog, installer, and consumer guidance, runs the docs validate/check/build gates, and checks the showcase with lint, TypeScript, deterministic tests, Expo Doctor, web export, and its local web smoke journey. The smoke journey uses SHOWCASE_CHROME_PATH when set, the default macOS Chrome path when present, and otherwise Playwright’s bundled Chromium. Remote CI runs the same docs check, showcase tests, and smoke journey (see .github/workflows/ci.yml). It does not run native-device checks, EAS, deployment, telemetry, or other cloud actions. Use the focused commands in the scripts reference when debugging one layer.

Was this page helpful?