Project: PrepRounds (working title) — mobile app for charge-nurse conversation practice, built for RevenueCat Shipaton 2026.
This is a 6-file spec package. Read in this order before writing any code:
| # | File | Purpose |
|---|---|---|
| 1 | 01-PRD.md |
What to build, for whom, in what priority order |
| 2 | 02-ARCHITECTURE-AND-DATA.md |
Frontend architecture, backend architecture, exact tech stack, folder structure, data model, API contracts |
| 3 | 03-DESIGN-SYSTEM-AND-SCREENS.md |
Design tokens, component library setup, and the full spec for every screen |
| 4 | 04-SCENARIO-PROMPTS.md |
Ready-to-paste TypeScript file with the 4 roleplay prompts + feedback-engine prompt |
| 5 | AGENTS.md |
Build order, guardrails, and rules for coding agents specifically |
If a decision isn’t specified in these files, stop and flag it — don’t invent a convention. Every naming choice, every package, every color, every prompt string is deliberately fixed across these files so that no two files disagree. If you find an apparent contradiction between files, AGENTS.md wins for process/convention questions and 02-ARCHITECTURE-AND-DATA.md wins for technical/schema questions — but treat any contradiction you find as a bug in the spec and flag it rather than silently picking one.
| If you need… | It lives in… | Do not… |
|---|---|---|
| Feature scope, user stories, acceptance criteria | 01-PRD.md |
Add features not listed there without flagging it |
| Exact package names & install commands | 02-ARCHITECTURE-AND-DATA.md §4 |
Guess a package name or version |
| Folder/file structure | 02-ARCHITECTURE-AND-DATA.md §5 |
Invent your own structure |
| Environment variable names | 02-ARCHITECTURE-AND-DATA.md §6 |
Use different variable names in different files |
| Database schema | 02-ARCHITECTURE-AND-DATA.md §10 |
Add/rename columns without updating this file |
| API request/response shapes | 02-ARCHITECTURE-AND-DATA.md §11 |
Invent a different response shape |
| Colors, type scale, spacing | 03-DESIGN-SYSTEM-AND-SCREENS.md §1–3 |
Pick your own colors/sizes |
| What each screen contains, including loading/empty/error states | 03-DESIGN-SYSTEM-AND-SCREENS.md §5 |
Skip a state or invent screen content |
| The 4 scenario prompts, verbatim | 04-SCENARIO-PROMPTS.md |
Paraphrase or regenerate these — copy them exactly |
| Build order, definition of done | AGENTS.md |
Build screens out of the specified order |
# 1. Scaffold
npx create-expo-app@latest preprounds --template blank-typescript
cd preprounds
# 2. Router
npx expo install expo-router react-native-safe-area-context react-native-screens expo-linking expo-constants expo-status-bar
# 3. UI system (see 02-ARCHITECTURE-AND-DATA.md §4 before running — order matters)
npx gluestack-ui init
# 4. Start dev server
npx expo start
Full package list, exact versions where it matters, and why each one was chosen are in 02-ARCHITECTURE-AND-DATA.md §4 — do not npm install anything not listed there without checking it against 01-PRD.md scope first.