OUTCOMES
What this Prompt helps you deliver
- The iOS app runs in a simulator or on a device
- xcodebuild verification passes
BEFORE YOU START
Before you start
- A Mac with a compatible Xcode is available
- The backend API is reachable
What AI should inspect first
apps/tabtin-iosAGENTS.mddocs/agent/commands.mdREADY TO RUN
Complete Prompt
Copy the complete Prompt with its execution and acceptance boundaries.
Start the TabTin iOS client so I can turn it into my own mobile product. Use the repository’s current project settings and complete dependencies, backend connectivity, compilation, and runtime verification; do not merely describe buttons in Xcode.
Read AGENTS.md, docs/agent/commands.md, the mobile rules, and apps/tabtin-ios. Inspect macOS, Xcode, command-line tools, simulators, Swift, and signing team. Ensure the backend address is reachable from the simulator or device—do not assume device localhost means the Mac. Preserve existing signing and user changes.
Identify the project entry, Scheme, deployment target, package dependencies, and environment source. Resolve dependencies and choose an available simulator; explain account/team needs before device signing. Configure the development backend and permissions without embedding secrets in source. Build from the command line to reveal real compiler errors, fix them narrowly, and then run the app. Verify sign-in, Organization entry, navigation, and one core data screen against live data.
After every change, run an explicit xcodebuild and record Scheme, Destination, and result. Launch the simulator or device and inspect network behavior, permission prompts, basic light/dark appearance, and console errors. Identify push, camera, or other device-only coverage that remains.
Report target, backend, build command, result, screens verified, signing state, and device-only follow-up. Do not upload TestFlight or change Bundle ID/signing assets unless requested.