← All use cases

Build for iOS

Set up, build, and troubleshoot SwiftUI apps for both iPhone and iPad with ZeroTwo.

ZeroTwo can set up iOS SwiftUI projects, keep builds CLI-first through `xcodebuild` or Tuist, and bring in the Build iOS Apps plugin with XcodeBuildMCP once the work calls for more depth.

Advanced
1h

Skills & Plugins

  • Build iOS Apps
    Covers SwiftUI patterns, Liquid Glass, view refactoring, performance audits, App Intents, and simulator debugging (desktop app; needs a Mac with Xcode).

Scaffold the app and build loop

For a new app, plain prompting suffices: ask for a starter SwiftUI app and a small build-and-launch script. Stay CLI-first with xcodebuild, which lists schemes and runs build, test, and archive actions. Tuist can generate projects headlessly. Once a full Xcode project needs simulator control, screenshots, and logs, add the Build iOS Apps plugin, which wires in XcodeBuildMCP for those jobs.

The plugin runs from the ZeroTwo desktop app on a Mac with Xcode and the iOS Simulator installed; the cloud sandbox is Linux and cannot build iOS apps.

Leverage skills

Skills are optional at first; add them as work specializes. The Build iOS Apps plugin ships skills for SwiftUI UI patterns, Liquid Glass adoption, view refactoring, performance audits, App Intents, simulator debugging, ETTrace profiling, and memory-leak investigation. See the plugins and skills docs.

Iterate

Be specific about each change, and state whether the project is greenfield or existing, which devices and targets must work, and what validation you expect.

Example prompt

Ask for a feature such as onboarding that reuses existing models and navigation, uses XcodeBuildMCP to build and launch, targets iPhone and iPad, and reports the scheme, simulator, and checks used.

Practical tips

Start with basics

Greenfield work usually needs no skill or MCP server.

Use a small trustworthy validation loop

Run the narrowest command that proves what you changed; widen later.

Keep the loop CLI-first

Terminal builds keep ZeroTwo out of the Xcode GUI.

Leverage XcodeBuildMCP

Reach for it when plain shell commands stop being enough.

Related use cases