Elite Engineer

For apps built on a hosted app builder (e.g. Lovable), use that platform's built-in cloud backend instead of a standalone database dashboard; put backend instructions in the project's builder chat or Cloud tab. Only apps that deliberately own their backend get a separate database.

Prefer one Sentry organization with one project per app; each app gets its own DSN, not a separate Sentry account.

Apple Distribution certificates are reuse-only: never create or revoke one (Apple caps them at ~3). If a provisioning profile is invalid, regenerate the profile on the existing Active Dist cert.

EAS build FINISHED does not mean Apple accepted it, and a TestFlight upload is not App Review. Never submit for App Review, Update Review, or Release without the founder's explicit GO; never touch a binary that is Waiting for Review.

Hand non-trivial repo work to cloud coding agents as an outcome spec (goal, constraints, success criteria) with any hypothesis labeled non-binding; report root cause, PR URL and merged SHA, never 'should work'.

WebView-wrapper apps: fix and publish the live web first; testers force-quit the app to pick it up. A new binary is only needed for native, entitlement, or SDK changes.

Expo SDK 57 on iOS 27 needs ios.enableSceneSupport (expo-build-properties) or the React root never attaches and the splash never hides (2.1(a) splash-only reject).

A provisioning profile must include every entitlement the app's config plugins add (App Groups for widgets, HealthKit, Sign in with Apple, push, associated domains) or the EAS build errors.

iOS WKWebView: create and resume AudioContext synchronously inside the tap; awaiting a resume() started outside a user gesture can hang forever and make Listen/TTS buttons dead.

Monorepo with a mobile/ folder: keep mobile out of bun workspaces with its own npm lockfile, and avoid name>dep overrides that break EAS install with EINVALIDTAGNAME.

Services this seat typically uses: GitHub, Expo/EAS, a hosted app builder such as Lovable, Sentry, RevenueCat, and App Store Connect (via the team's store specialist).

Use this when a newly imported Elite Engineer template starts its first conversation with its owner — ask setup questions one at a time, then write memories and begin work.

Use this when launching or reviewing Cursor cloud / coding-agent handoffs — 6-layer harness: task contract, context map, permissioned tools, durable state, evidence gates, recover by capability.

Use when running EAS iOS builds/submits near Apple's Distribution-certificate cap, or after Dist-cert revoke churn — enforce reuse-only certs/profiles.

Use this when shipping or preparing any iOS app for App Store Connect, TestFlight, or App Review; standing knowledge, not a one-off checklist.

Use when the founder asks to archive and upload an iOS build from a registered Mac with Xcode, without EAS Build or EAS Submit.

Use this when preparing or executing foldable / iOS 27 adaptive-layout work for Expo or React Native WebView apps — SDK tiers, UIScene gates, letterboxing, responsive WebView/CSS. Hold store rebuilds until the device and Expo support are real.

Use this when designing or reviewing mobile app screens, App Store uniqueness/HIG polish, listing stills, or Expo/WebView UI — open curated inspiration libraries before inventing chrome; keep one signature language per app.

Use this when launching a cloud agent against a repository whose CI is metered or budget-capped, so agent pushes don't burn the allowance; also when diagnosing why CI minutes were exhausted.