expo-template

Imported from mrmeg/expo-template (AGENTS.md). Install upstream with npx skills add mrmeg/expo-template. Copyright stays with the author.

Project Guidance

Bun-managed Expo template with reusable UI and media packages. Code directly unless the user asks for a plan.

How To Work

• Read this file first, then load only what the task needs.
• Validate with fresh command output; never claim tests, builds, UI checks, or CI passed from memory.
• Keep durable template guidance in docs/ or the relevant package README.
• Reusable UI goes in packages/ui; reusable media contracts and processing in packages/media.
• App integrations stay under client/, server/, app/api/, or shared/.

Docs

Tech Stack

Project Notes

• Use the exact package scripts in package.json; do not substitute generic Expo or npm commands when a local Bun script exists.
• Quote route paths with parentheses or brackets in shell commands, for example 'app/(main)/(tabs)/index.tsx'.
• Design-system rules — raw colors, off-scale spacing, appearance overrides on @mrmeg/expo-ui components, raw primitives the design system already wraps — are enforced by @mrmeg/eslint-plugin-expo-ui (packages/lint/README.md) through bun run lint, which covers app/ only. bun lint:ui lints app, client, and shared for design-system violations alone, --changed narrows it to the files you touched, and --doctor [file] checks the plugin, the config, and the design system are wired. Read the message and use the token, variant, or component it names; never disable one of these rules without a -- reason on the disable comment.
• Auth, billing, media, and Sentry must fail closed when env is missing; a blank .env keeps the template explorable.
• Web is server-rendered per request: web.output: "server" plus unstable_useServerRendering runs routes, loaders, middleware, and API routes on the server, so the first response carries real route markup. The server has no DOM: anything the first render needs comes off the request (server/lib/ssrViewport.ts, server/lib/ssrOnboarding.ts), and styles must be registered at module scope for client/features/app/SsrStyleFlush.tsx to serialize them — see docs/server-guide.md. Verify web changes in a browser against bun run build && bun run start, not only Jest or tsc.
• Five gallery routes under app/(main)/(demos) — showcase/index.tsx, themed-showcase.tsx, components/index.tsx, components/[id].tsx, blocks/index.tsx — are one-line lazy shells; edit the bodies in client/showcase/*Screen.tsx. Live previews stay out of the eager web bundle because they are reachable only through client/showcase/gallery.tsx, via the single import() in client/showcase/lazyGallery.tsx; client/showcase/__tests__/gallerySplitPoint.test.ts fails on a static import from outside client/showcase/.
• Generated artifacts, all gated by bun run verify and CI — regenerate and commit, never hand-edit: client/templates/registry.generated.ts and client/blocks/registry.generated.ts (bun run gen:templates / gen:blocks); llms-full.txt and llms-examples.txt (bun run docs:llms, built by scripts/build-llms-full.mjs from its source-doc list and directory walks — rerun after editing those docs or adding/removing demo routes, screens, components, or form wrappers). bun run docs:versions:check holds README.md's version claims to package.json.

Agent Workflow

Use this workflow only for planned work. Normal coding requests proceed directly.

• write-spec creates a self-contained spec in the tracked Agent/ folder; review-spec marks it ready or blocked.
• shift implements ready specs. dayshift pins interactive mode; nightshift runs ready AFK specs without questions.
• Each spec becomes one agent/* branch and draft PR against its declared base-branch. After the PR opens, set the spec's status: in-review and its pr link, and commit that on the base branch. Never include Agent/ files in agent/* PR diffs.
• review-shift reviews and merges those PRs.
• Keep target branches clean and synchronized. Verify with fresh command output.