EXPO + REACT NATIVE AGENTS.MD

A mobile app built with Expo and React Native. The rules keep native dependencies matched to the Expo SDK, keep an agent out of the generated native folders, and make clear that builds and store submissions are not agent tasks.

Zero retention: everything you type stays in this browser. Verify it yourself in DevTools.
The Expo + React Native filesCustomize in the generator
AGENTS.mdFor Codex, Cursor, Copilot, Jules, Windsurf and more
# AGENTS.md

Project: expo-app. A React Native mobile app built with Expo and Expo Router, shipped to the App Store and Google Play.

This file is the single source of truth for every coding agent working in this repository. The tool-specific files (CLAUDE.md, GEMINI.md, .github/copilot-instructions.md and .cursor/rules/project.mdc) point here. Edit this file, not those.

## Stack

- Language: TypeScript
- Framework: Expo (React Native)
- Hosting: App Store and Google Play
- Tests: Jest
- Package manager: npm

## Commands

Run these from the repository root.

- Install dependencies: `npm install`
- Run locally: `npx expo start`
- Build: `npx expo export`
- Run all tests: `npx jest`
- Run one test file: `npx jest app/path/to/file.test.tsx`
- Lint: `npx expo lint`
- Type-check: `npx tsc --noEmit`
- Format: `npx prettier --write .`

## Project layout

- `app/`: Expo Router routes (file-based)
- `components/`: Shared components
- `hooks/`: Custom hooks
- `assets/`: Images and fonts
- `app.config.ts`: Expo config: plugins, permissions, identifiers

## Code style

- Indent with 2 spaces. Never tabs.
- TypeScript runs in strict mode. Do not use `any`; use `unknown` and narrow it, or write the real type.
- Match the style and patterns of the surrounding code, even where you would personally choose differently.
- Use named exports. Do not add default exports.
- Never swallow an error. Handle it where you can act on it, or rethrow it with context about what failed.
- Commit messages follow Conventional Commits: `feat:`, `fix:`, `refactor:`, `test:`, `docs:`, `chore:`, with an imperative summary under 72 characters.
- Every new UI control works with a keyboard, has a visible focus state and an accessible name.

## Working rules

- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Do not hand-edit generated files or lockfiles; change the source and regenerate.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.

## Product constraints

- Treat user data as sensitive: never log personal data, tokens or request bodies, and collect nothing the feature does not need.
- Design and test every screen at phone width first, then scale up.

## Project-specific notes

- Install native-capable packages with `npx expo install <pkg>` so versions match the current Expo SDK; never plain `npm install` for those.
- Do not create or edit `ios/` and `android/`; native configuration goes through `app.config.ts` and config plugins (Continuous Native Generation).
- Use Expo Router file-based routes in `app/`; navigate with `Link` and `router`, not React Navigation imperative setup.
- Every `EXPO_PUBLIC_` variable ships inside the app binary and is public. Never put secrets there.
- Store tokens with `expo-secure-store`, not AsyncStorage.
- Use `StyleSheet.create` or the existing styling system; test layouts on both iOS and Android sizes.
- Never run `eas build --auto-submit` or `eas submit`; builds and store submissions are done by a human.

## Project phase

This project is in active development. Follow the patterns that already exist; consistency beats novelty.
CLAUDE.mdFor Claude Code
# CLAUDE.md

@AGENTS.md

## Claude Code

- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file, so every agent stays in sync.
- Put Claude-only preferences below this line. Personal, uncommitted notes belong in CLAUDE.local.md.
GEMINI.mdFor Gemini CLI
# GEMINI.md

@./AGENTS.md

## Gemini CLI

- The shared project instructions are imported from AGENTS.md on the line above. Edit AGENTS.md, not this file.
- Alternative: delete this file and set "context": { "fileName": ["AGENTS.md"] } in .gemini/settings.json so Gemini CLI reads AGENTS.md directly.
.github/copilot-instructions.mdFor GitHub Copilot
# Copilot instructions

Project: expo-app. A React Native mobile app built with Expo and Expo Router, shipped to the App Store and Google Play.

The full instructions are in AGENTS.md at the repository root. Read it before you change code; if anything here disagrees with it, AGENTS.md wins. The essentials are repeated below for Copilot surfaces that only read this file.

## Stack

- Language: TypeScript
- Framework: Expo (React Native)
- Hosting: App Store and Google Play
- Tests: Jest
- Package manager: npm

## Commands

- Install dependencies: `npm install`
- Run locally: `npx expo start`
- Build: `npx expo export`
- Run all tests: `npx jest`
- Run one test file: `npx jest app/path/to/file.test.tsx`
- Lint: `npx expo lint`
- Type-check: `npx tsc --noEmit`
- Format: `npx prettier --write .`

## Working rules

- Before you say a task is done, run the test, lint and type-check commands above and make sure they pass. If you could not run them, say so.
- Never write secrets, API keys, tokens or passwords into code, tests, fixtures, logs or commits. Read them from environment variables, and never commit `.env` files.
- Do not add a new dependency without asking first. Prefer the standard library and what is already installed.
- Do not hand-edit generated files or lockfiles; change the source and regenerate.
- Change only what the task needs. Do not refactor, rename or reformat unrelated code.
.cursor/rules/project.mdcFor Cursor
---
description: Project instructions for every task (mirrors AGENTS.md)
globs:
alwaysApply: true
---

# Project rules

The project instructions live in @AGENTS.md at the repository root, which Cursor loads automatically. They are not repeated here, so they cost context only once. Edit AGENTS.md, not this rule.

Before you change code, check the Commands and Working rules sections of AGENTS.md, and run its test and lint commands before you say a task is done.

Put Cursor-only rules below, or add scoped rules as more .mdc files with `globs` (for example `src/components/**/*.tsx`).

These are the exact files the generator writes for this preset. Change any command or rule in the generator and download your own set.

About the Expo + React Native preset

What Is in the Expo + React Native AGENTS.md?

The preset describes a a React Native mobile app built with Expo and Expo Router, shipped to the App Store and Google Play. Its AGENTS.md is 52 non-empty lines with 8 exact commands, 5 key directories, and 7 stack-specific rules on top of the shared working rules.

  • Commands: npm install, npx expo start, npx expo export, npx jest, npx jest app/path/to/file.test.tsx, npx expo lint, npx tsc --noEmit, npx prettier --write ..
  • Layout: app/, components/, hooks/, assets/, app.config.ts.
  • Wrappers: CLAUDE.md and GEMINI.md import AGENTS.md; the Copilot file repeats the essentials; the Cursor rule points to AGENTS.md.

Why These Rules for Expo + React Native?

Version mismatches break native builds

React Native modules must match the native code in the Expo SDK. npm install picks the latest version, which often does not. expo install resolves the compatible one and is the most important single rule here.

Native folders are generated

With Continuous Native Generation, ios/ and android/ are rebuilt from config. Agent edits there vanish on the next prebuild and cause confusing build failures.

Everything in the bundle is public

Mobile apps can be unpacked. Public env variables and hard-coded keys are readable by anyone with the app installed.

Submissions are irreversible

An accidental store submission can trigger review, rejection or a broken release for real users.

Which Stack Rules Does the File Add?

  • Install native-capable packages with npx expo install <pkg> so versions match the current Expo SDK; never plain npm install for those.
  • Do not create or edit ios/ and android/; native configuration goes through app.config.ts and config plugins (Continuous Native Generation).
  • Use Expo Router file-based routes in app/; navigate with Link and router, not React Navigation imperative setup.
  • Every EXPO_PUBLIC_ variable ships inside the app binary and is public. Never put secrets there.
  • Store tokens with expo-secure-store, not AsyncStorage.
  • Use StyleSheet.create or the existing styling system; test layouts on both iOS and Android sizes.
  • Never run eas build --auto-submit or eas submit; builds and store submissions are done by a human.

How Do You Add These Files to a Expo + React Native Repository?

  1. Download the zip above. It is laid out exactly as the files go into the repository.
  2. Unzip it at the repository root. AGENTS.md, CLAUDE.md and GEMINI.md go next to your README; the Copilot file goes in .github/ and the Cursor rule in .cursor/rules/.
  3. Open AGENTS.md and check every command against your package scripts or Makefile.
  4. Delete wrappers for tools your team does not use, and any old .cursorrules or .windsurfrules file.
  5. Commit, then run the linter on AGENTS.md whenever you change it.

Want different commands or rules? Load this preset into the generator, change anything, and download your own set.

Which Agents Will Read These Files?

AGENTS.md is read directly by Codex, Cursor, Windsurf, Cline, Zed and Jules, and by GitHub Copilot's cloud agent, code review and CLI. Claude Code reads it through the generated CLAUDE.md, and Gemini CLI through GEMINI.md. See the compatibility table for details, last verified 2026-11-13.

Which Similar Stacks Are in the Library?

All presets are on the stacks page.

Frequently Asked Questions

Does this work for bare React Native without Expo?

Partly. The component rules apply, but bare projects edit native folders directly and use different commands. Edit the notes in the generator.

Why is the build command expo export?

It bundles the JavaScript for all platforms without a native build or an EAS account, which makes it a safe local check that the app compiles.

How do agents test on a device?

They usually cannot. The agent runs tests and type checks; you check behavior in Expo Go or a development build.

Are these Expo + React Native files free to use?

Yes. Copy them into any project, commercial or not, without attribution. They are a starting point: adjust the commands and rules to match your repository.

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word for it. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing you type is sent. The check takes under a minute.

  1. Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
  2. Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your input.
  3. Click the clear icon in the Network tab so that the log is empty.
  4. Switch between the file tabs, copy a file and download the zip.
  5. Look at the Network tab again. It is still empty. Downloads are built in the page as Blob URLs, so even the zip never touches a server. For extra proof, turn on offline mode after the page loads: everything keeps working.

Only the feedback form can add a line to that log, and it sends only the vote and comment you type into it. 2prompt has no server code at all: no API, no model and no database of your files. The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site, the fonts and the anonymous analytics endpoint.

Was this helpful?