Skip to content
Stack

iOS loadouts

Three routes to iOS. For native Swift, the agent builds, tests and looks at the app through MobileBuildMCP and leaves signing and pbxproj alone, and a second loadout keeps SwiftUI logic in a Swift package that swift test covers on Linux. For React Native, the agent works through Expo with SDK-matched installs and Expo's MCP server, and checks the native fingerprint before anything ships as an EAS Update.

Every one installs for Claude Code, Codex CLI, Cursor, Gemini CLI, Antigravity CLI and GitHub Copilot unless its card says otherwise.

Web apps
Verified install Not agent-tested

Expo and React Native with Expo MCP

Expo rules for agents plus Expo's official MCP server: npx expo install, Expo Router, no secrets in EXPO_PUBLIC_, no production EAS releases, check on a simulator.

  • 1 1 Rules
  • 1 1 Skills
  • 1 1 MCP
react-nativeexpotypescript
Web apps
Verified install Not agent-tested

iOS builds with MobileBuildMCP (XcodeBuildMCP)

Let the agent build, test, run and screenshot iOS and macOS apps through MobileBuildMCP, pinned with telemetry off, with Swift concurrency and pbxproj rules.

  • 1 1 Rules
  • 1 1 Skills
  • 1 1 MCP
swiftiosxcode
Web apps · Workflow
Verified install Not agent-tested

SwiftUI with a Swift package core tested by swift test in CI

SwiftUI screens as thin views over @Observable view models in a Swift package, tested with Swift Testing by swift test on Linux and macOS CI.

  • 1 1 Rules
  • 1 1 Skills
  • – 0 MCP
swiftswiftuiios

Often used with iOS

Looking for something narrower? Search within iOS or filter everything.