Skip to content
supastack
Browse documentation
MobileExpo

For AI agents: fetch the complete documentation index at /llms.txt, the full documentation corpus at /llms-full.txt, the agent skill at /skill.md, or this page as Markdown at /docs/mobile/agent-setup.md (or send Accept: text/markdown).

Let an agent set it up

Paste one ready-made prompt into a coding agent, let it run the Mobile setup on your computer, and check the report it writes about each step.

Ask about this guide
Open in

You can delegate the boring part

This repository was written so a coding agent can read it. It ships a map file (llms.txt), a rules file (AGENTS.md), per-file memory notes (.ai/) and task skills (.agents/skills/). Open a terminal inside your copy of the repository to run it — the standalone Mobile checkout does not include the prompts/ folder, so the ready-made prompt is printed in this guide instead of a file.

Delegating the typing does not mean skipping the checks. The agent works inside your copy of the repository and must report what it did with evidence. The sections below show what a good report looks like, so you stay in charge of the result.

This path sets up the Expo app and its connection to the Web backend — the server that handles accounts and data. If your checkout also contains apps/web, the agent can run that backend locally; a Mobile-only checkout needs the reachable backend address you were given.

What you need first

Finish the preparation guide first: Node.js, Git and an editor installed, the GitHub invitation accepted, and the supastack folder downloaded to your computer. The agent works inside that folder, so everything in Before you start still applies.

You also need a tool that can act as a coding agent — an editor with a built-in AI coding agent (an AI IDE), or an agent that runs in your terminal (an agent CLI). Any current agent-capable tool works; the prompt already spells out what it must read and run, so you do not need to write instructions yourself.

Finally, decide the two things the prompt asks for: the backend address your device can reach — a computer LAN address for a local backend or your provided HTTPS address — and where you will view the app: Expo Go on a phone, an iOS Simulator on a Mac, or an Android emulator.

Copy the prompt, fill in two blanks, paste

The prompt is the code block below — select and copy the whole block.

Two placeholders need your choices. Replace <API_URL> with the backend address your device can reach — your computer's LAN address plus port 3000 for a local backend on the same Wi-Fi, or your provided HTTPS address. Replace <DEVICE: expo-go | simulator> with expo-go for a physical phone or simulator for an installed iOS/Android simulator. The numbered steps stay exactly as written.

Set up this supastack Mobile checkout end to end and open the Expo app on **<DEVICE: expo-go | simulator>** against the backend at **<API_URL>**.
1. Read llms.txt, AGENTS.md and docs/agent-security.md before changing anything.
2. Run corepack pnpm install.
3. Create apps/mobile/.env.local from the names in .env.example: EXPO_PUBLIC_API_URL=<API_URL>, EXPO_PUBLIC_APP_SCHEME=supastack and EXPO_PUBLIC_MOBILE_PURCHASES_PROVIDER=off. Never invent a variable absent from .env.example.
4. If apps/web exists in this checkout, start it in a second terminal; otherwise verify <API_URL> answers from this computer and report its status.
5. Start Expo with corepack pnpm --filter @supastack/mobile start and report the QR preview or simulator launch with the real output.
6. Stop after any step fails twice and report the failing command and first error. Ask before deleting anything.

What the agent does with the prompt

The prompt points the agent at the map, the rules and the security checklist, then tells it to work through the setup in order and prove each phase. In plain terms, the agent:

  • Reads the repository map (llms.txt), the project rules (AGENTS.md) and the credential-handling rules (docs/agent-security.md) before touching anything.
  • Creates apps/mobile/.env.local from .env.example names only, with the API address and scheme you supplied — the agent never invents an EXPO_PUBLIC_ setting absent from the example file.
  • Verifies the backend answers at your address — starting apps/web itself only when that folder exists in this checkout — instead of assuming a server that is not there.
  • Installs dependencies and starts the Expo development server, then reports the QR preview or simulator launch with the actual output.
  • Stops and reports after the same step fails twice — it does not work around a failure or delete anything without asking.

What you check in the agent's report

A good report shows evidence, not claims. Look for the backend URL answering, the dependency install completing and the Expo server output behind each PASS — not a sentence like 'everything works'.

The prompt tells the agent to stop and report after the same step fails twice — not to work around the failure — and to ask you before anything destructive. If your agent keeps improvising after repeated failures, stop it and take the first error to the troubleshooting guide.

Two things must never appear: a security feature switched off to silence an error, and a secret value such as a password or key printed into the chat or the report. If you see either, treat the run as failed.

Keep the preview and real sign-in separate in your head. A successful QR preview shows screens only — real accounts need the backend's database, and real purchases need an EAS development build. 'The preview opened' is not yet 'accounts work'.

If you would rather do it by hand

Every step the agent performs is written out in the manual guides below — the same commands, the same checks, at your pace.