Expo and React Native with Expo MCP

# AGENTS.md: Expo / React Native app

React Native app on Expo with Expo Router and TypeScript. Check the Expo SDK version in `package.json` before using an API.

## Commands
- Start: `npx expo start`. Lint: `npx expo lint`. Types: `npx tsc --noEmit`. Tests: the project's test script.
- Health check after dependency changes: `npx expo-doctor`.
- Add a package: `npx expo install <package>` so the version matches the SDK. Never plain `npm install` for native packages.
- Done means: lint, type-check and tests pass, and expo-doctor reports no problems you introduced.

## Project rules
- Routes are files in `app/` (Expo Router). Layouts in `_layout.tsx`; do not hand-roll a navigator alongside the router.
- Native config lives in `app.json` or `app.config.ts` and config plugins. If `ios/` and `android/` are generated
  (Continuous Native Generation, listed in `.gitignore`), never edit them; change config and run `npx expo prebuild --clean`.
- Packages with native code need a development build, not Expo Go. Say so when you add one.
- `EXPO_PUBLIC_` variables are compiled into the app and visible to anyone. Never put secrets in them; secrets stay on a server.
- Use platform-specific files (`.ios.tsx`, `.android.tsx`) or `Platform.select` only when behaviour really differs.
- Lists use `FlatList` or `FlashList`, never `map` inside a `ScrollView` for long data.

## Releases
- Never run `eas build --profile production`, `eas submit` or `eas update` on a production channel without the human
  asking for it in this session. Preview builds and updates to a preview channel are fine when asked.
- Bumping the Expo SDK is its own task: follow the upgrade guide, run `npx expo install --fix`, then expo-doctor.

## Expo MCP and skills
- The Expo MCP server (`expo` in the MCP config) gives live docs, EAS build logs and, with a running dev server,
  simulator screenshots. Prefer it over guessing APIs from memory. It signs in with your Expo account (OAuth).
- Use the `expo-change` skill for any feature or fix.

# CLAUDE.md

@AGENTS.md

## Claude Code notes
- Skills from this loadout live in `.claude/skills/`: `expo-change`. Use them when their description matches the task.
- MCP servers for this project are in `.mcp.json`. If a server is not connected, tell the human rather than working around it.
- Follow AGENTS.md above; where this file and AGENTS.md disagree, AGENTS.md wins.

<!-- From the Agent Loadout "Expo and React Native with Expo MCP" v1.0.0 — https://loadout.jnw-it.com/loadouts/expo-react-native/ -->

# GEMINI.md

@./AGENTS.md

## Gemini CLI notes
- Skills from this loadout live in `.agents/skills/`: `expo-change`. Use them when their description matches the task.
- Follow AGENTS.md above; where this file and AGENTS.md disagree, AGENTS.md wins.

<!-- From the Agent Loadout "Expo and React Native with Expo MCP" v1.0.0 — https://loadout.jnw-it.com/loadouts/expo-react-native/ -->

---
name: expo-change
description: Make a feature or fix in an Expo app with SDK-matched packages, Expo Router conventions, a check on a simulator or device and no production releases. Use for any change to an Expo / React Native app.
---

# Expo change

1. Read `package.json` (Expo SDK), `app.json` or `app.config.ts`, and the routes in `app/` that the change touches.
2. Look up the API in the current docs (Expo MCP `search_documentation` / `read_documentation`, or docs.expo.dev) for
   this SDK version. Do not rely on memory for package APIs; they change between SDKs.
3. New packages: `npx expo install <package>`. If it has native code, note that a development build is needed.
4. Make the change in TypeScript, following the router layout. Keep secrets out of `EXPO_PUBLIC_` variables.
5. Run `npx expo lint`, `npx tsc --noEmit`, the tests and, after dependency changes, `npx expo-doctor`.
6. Check it runs: with the dev server up, open the screen on a simulator or device. With Expo MCP local capabilities,
   take a screenshot and look at it; otherwise ask the human to check and describe what to look for.
7. Report: files changed, packages added (and whether a new dev build is needed), check results, screenshot if taken.

{
  "mcpServers": {
    "expo": {
      "type": "http",
      "url": "https://mcp.expo.dev/mcp"
    }
  }
}