iOS builds with MobileBuildMCP (XcodeBuildMCP)

# AGENTS.md: iOS and macOS app with MobileBuildMCP

Swift app built with Xcode. The agent builds, runs and tests through MobileBuildMCP (formerly XcodeBuildMCP), not by
guessing `xcodebuild` flags.

## Tools
- MCP server `mobilebuildmcp` (pinned in the MCP config). On first use in a session, list projects and schemes, and set
  the session defaults (project or workspace, scheme, simulator) once instead of passing them on every call.
- Telemetry is off in the MCP config (`MOBILEBUILDMCP_SENTRY_DISABLED`). Keep it that way unless the human changes it.
- If the server is unavailable, fall back to `xcodebuild -scheme <scheme> -destination 'platform=iOS Simulator,name=<device>' build test`.

## Done means
- The app builds for the simulator with no new warnings, the tests for the scheme pass, and you launched the app and
  looked at the screen you changed (screenshot or UI hierarchy through the MCP server).

## Swift rules
- Swift concurrency: UI work on `@MainActor`; no `DispatchQueue.main.async` in new code. Respect strict concurrency
  checking if the project enables it; do not silence warnings with `@unchecked Sendable` or `nonisolated(unsafe)`
  without explaining why it is safe.
- SwiftUI: small views, state owned in one place (`@State`, `@Observable` models), no business logic in `body`.
- No force unwraps (`!`) or `try!` on data from outside the app. Errors are typed and shown to the user where it matters.
- Tests with Swift Testing (`@Test`, `#expect`) for new code, unless the project only uses XCTest.

## Never
- Never edit `project.pbxproj` by hand when the change can be made through a tool, and never reorder or reformat it.
  If you must add a file, prefer a folder the project already syncs or ask the human.
- Never change signing settings, bundle identifiers, entitlements or provisioning without the human asking.
- Never upload to TestFlight or the App Store.

Use the `ios-build-loop` skill for every change.

# CLAUDE.md

@AGENTS.md

## Claude Code notes
- Skills from this loadout live in `.claude/skills/`: `ios-build-loop`. Use them when their description matches the task.
- MCP servers for this project are in `.mcp.json`. If a server is not connected, tell the human rather than working around it.
- Follow AGENTS.md above; where this file and AGENTS.md disagree, AGENTS.md wins.

<!-- From the Agent Loadout "iOS builds with MobileBuildMCP (XcodeBuildMCP)" v1.0.0 — https://loadout.jnw-it.com/loadouts/ios-mobilebuildmcp/ -->

# GEMINI.md

@./AGENTS.md

## Gemini CLI notes
- Skills from this loadout live in `.agents/skills/`: `ios-build-loop`. Use them when their description matches the task.
- Follow AGENTS.md above; where this file and AGENTS.md disagree, AGENTS.md wins.

<!-- From the Agent Loadout "iOS builds with MobileBuildMCP (XcodeBuildMCP)" v1.0.0 — https://loadout.jnw-it.com/loadouts/ios-mobilebuildmcp/ -->

---
name: ios-build-loop
description: Build, test, run and look at an iOS or macOS change through MobileBuildMCP, then fix what the build log or the screen shows. Use for every change to a Swift app.
---

# iOS build loop

1. Session setup (once): discover projects and schemes, list simulators, and set session defaults for project or
   workspace, scheme and simulator. Prefer a recent iPhone simulator that is already booted.
2. Baseline: build and run the tests before changing anything, so later failures are known to be yours.
3. Make the change. Keep it small; one screen or one behaviour.
4. Build for the simulator. Read errors and new warnings from the structured build output and fix them before going on.
5. Run the tests for the scheme. A failing test you did not touch means stop and report.
6. Launch the app on the simulator, go to the changed screen and take a screenshot or read the UI hierarchy.
   Compare with what was asked; if it is wrong, go back to step 3.
7. Capture logs if the change involves runtime behaviour; look for new errors.
8. Report: what changed, build and test results, and the screenshot.

On a device: device tools need code signing set up in Xcode by the human. Do not change signing to make it work.

{
  "mcpServers": {
    "mobilebuildmcp": {
      "command": "npx",
      "args": ["-y", "mobilebuildmcp@2.7.1", "mcp"],
      "env": {
        "MOBILEBUILDMCP_SENTRY_DISABLED": "true"
      }
    }
  }
}