Nagarjuna2997/ios-agent-skill

**Give your coding agent the Apple references, Swift source and local tools it needs to build and review an iOS app.**
Watch the website walkthrough · Explore the website
Describe an app in one sentence and the /ios-build agent plans it, writes the SwiftUI code and Xcode project, then builds and runs it in the simulator (what has been verified, example apps on the website). For an existing project, the same package gives your coding agent reviews, local Apple references and simulator tools to check its work.
Explore the website · Client setup guides · npm · Release notes
Build an app from one sentence
/ios-build " " asks Claude Code to plan an iOS app, write its SwiftUI code and Xcode project, apply capability modules (sign-in, storage, payments, maps and more), then build, run and screenshot it in the iOS Simulator, ending with a report of what needs your accounts or money. Published tools are in ios-agent-mcp 2.10.2 (npm verified October 15, 2026), including plan-driven design tokens, sample data, palette-aligned assets, light/dark/XXL screenshot evidence, deployment-target checks and App Store readiness reports. Four existing apps built and ran on Xcode 27.0; see examples/agent for refreshed evidence.
Quickstart
Install the published server and Claude Code command:
Then, in any Claude Code session on a Mac with Xcode 16 or later:
**Shipping (unreleased GitHub source):** ios-agent-mcp ship prepares screenshot sets and metadata, then offers separately approved signing/archive and TestFlight upload steps. Setup and limitations. Live signed distribution is not yet verified; npm is unchanged.
**Windows/Linux or cloud client:** the GitHub source now includes build --remote for unsigned builds and simulator screenshots on GitHub Actions. It requires a destination repository, GitHub CLI authentication and pinned toolkit/Xcode versions. See remote macOS setup and billing. npm publication is deferred.
XcodeGen is optional: without it, the agent writes a folder-synchronized Xcode project itself. The steps are described in docs/tooling/ios-build-agent.md. The four screenshot examples reused existing app folders; this exact one-sentence quickstart has not yet been run from planning through code generation in one Mac session.
Examples
| Habit tracker | Notes with search | Three-tab feed | Food delivery |
|---|---|---|---|
| | | | |
Plans, generated sources, run reports and what was and was not exercised: examples/agent.
Capabilities
Every capability is a folder in capabilities/ with a manifest, recipe, Swift template, apply hook and verify hook. The catalog lists the wider landscape for planning and cost estimates. The counts below are generated from the manifests.
| Status | Capabilities |
|---|---|
| Verified on a Mac | 7 |
| Module exists, not yet verified on a Mac | 41 |
| ...of which the Swift compiled on a Mac (combined compile check) | 41 |
| Blocked | 0 |
| Listed for planning only | 114 |
162 catalog entries in 31 categories; generated from capabilities/CATALOG.md.
Needs your accounts
The agent builds and runs everything in the simulator without accounts. Capabilities that need a service declare the keys in their manifest. Client keys, such as a publishable key, go in the project's gitignored .env file and reach the app through a generated xcconfig. Until they are set, the keys are REPLACE_ME placeholders, so the app still builds and shows a configuration message. Server secrets are never put in the app. PLAN.md lists what each run needs and the cost model of each service. Running on a device, using TestFlight or publishing needs your Apple Developer Program membership.
Not yet
- The design-system, firebase-auth, firebase-firestore, google-sign-in, stripe-payments, rive-animation and webview-animation capabilities have passed isolated Mac compile verification. Provider accounts and runtime transactions remain unverified; a combined compile check is not a substitute for each module's verify run (see the compile check).