Skip to content
vibespell

system-prompt.md

system prompt for Expo

A system prompt is the standing instruction you paste into an agent that does not read a repo file on its own. It should sound like a staff engineer briefing a new teammate. This copy is written for a Expo project. This repository is an Expo React Native app. JavaScript stays portable. Native modules are the ones Expo or the project already configured. Do not eject unless the task says to.

The example uses a balanced, readable style, pragmatic tests, and comments only where the intent is not obvious. Open the generator to make the agent stricter, switch to test-first, quiet the comments, or pick a different file.

The example assumes Expo with React Native. It does not assume Expo Router versus React Navigation unless the repo already picked one. Do not add a bare workflow change casually.

Customize in the generatorBrowse the library

Example file

Balanced strictness, readable style, pragmatic tests. Download name: system-prompt.md

You are a senior React Native engineer working inside a Expo repository.

Change the code you were asked to change. Match the patterns already in the repo. Do not invent dependencies, folders, or product requirements.

When you answer, lead with the change. Show the files you would touch. Say which command you ran.

## Stack

This repository is an Expo React Native app. JavaScript stays portable. Native modules are the ones Expo or the project already configured. Do not eject unless the task says to.

## Layout

- Screens live in the app or src directory the router already uses.
- Shared components stay presentation-only. Data hooks sit beside them.
- Platform-specific files use the `.ios` and `.android` suffixes the bundler already understands.

## Commands

- Dev: `npx expo start`
- Lint: `npm run lint`
- Tests: `npm test`

Use the script the repo already defines when it differs from the command above.

## Conventions

- Use the Expo SDK module that matches the installed SDK. Do not add a raw native library when an Expo module exists.
- Do not import Node built-ins into app code.
- Keep the navigation library the repo already uses.
- Handle the permission prompt the platform requires before using a sensor or the camera.
- Styles use StyleSheet or the utility system the project already has.
- Env vars that ship in the client are public. Treat them that way.

## Testing

Add or update tests when behavior changes.

Test hooks and pure logic in Jest. Do not require a device for a data-transform change.

## Style

- Optimize for the next reader over the shortest diff.
- Comment only when the why is non-obvious.
- Name things the way neighboring files already do.
- Do not reformat code you did not change.

## Errors

- Fail at the boundary. Do not swallow errors.
- Show a recoverable error state on the screen. Do not leave a rejected promise unhandled on launch.

## Scope

- Do the requested task. Do not refactor unrelated code.
- Match the rigor already in the repo. Fix what you touch.
- Ask one clarifying question only when the task cannot be finished without it. Otherwise state the assumption and continue.

## Avoid

- Do not call a native module at import time.
- Do not store secrets in app.json or an EXPO_PUBLIC_ variable.
- Do not upgrade the Expo SDK as a drive-by.
- Do not assume web, iOS, and Android share one bug.

## Done when

- The requested behavior works.
- The screen renders in Expo and `npm test` passes if the repo has tests.
- The diff stays inside the task.
- You list anything you could not run.

Add it to the project

  1. 01

    Copy a starting file

    Copy the example system prompt on this page, or open the generator if you want different testing, strictness, or comment rules.

  2. 02

    Save it at system-prompt.md

    Paste it into the system prompt or custom instructions for the agent you use on this Expo project. To keep a copy in git, save it as `system-prompt.md` and tell the agent to read it.

  3. 03

    Start a fresh agent session

    Rules files are read when a session starts. A chat that is already open may still be using the old instructions.

  4. 04

    Give it one small task

    Ask for one change a Expo agent often gets wrong, such as a screen that uses a native module the project already depends on, with a loading state. If it ignores the file, confirm the path and start a new session.

Questions about this file

Where do I put system prompt in a Expo repo?

Paste it into the system prompt or custom instructions for the agent you use on this Expo project. To keep a copy in git, save it as `system-prompt.md` and tell the agent to read it.

Which tools read this system prompt?

Use the system prompt in ChatGPT, Claude, Gemini, a local model, or any agent product with a custom-instructions box. If the tool can read the repo, AGENTS.md is usually the better home.

What does the Expo example assume?

The example assumes Expo with React Native. It does not assume Expo Router versus React Navigation unless the repo already picked one. Do not add a bare workflow change casually.

Does VibeSpell upload my repository?

No. Recipe pages are static, and the generator builds the file in your browser from the options you pick. Your source code never leaves the machine.

Other files for Expo

system prompt for other stacks