name: Build for iOS
tagline: Use Codex to scaffold, build, and debug SwiftUI apps for iPhone and iPad.
summary: Use Codex to scaffold iOS SwiftUI projects, keep the build loop
CLI-first with xcodebuild or Tuist, and add XcodeBuildMCP or focused SwiftUI
skills when the work gets deeper.
skills:
-
token: build-ios-apps url: https://github.com/openai/plugins/tree/main/plugins/build-ios-apps description: Build or refactor SwiftUI UI, adopt modern iOS patterns such as Liquid Glass, audit runtime performance, and debug apps on simulators with XcodeBuildMCP-backed workflows. bestFor:
-
Greenfield iOS SwiftUI apps where you want Codex to scaffold the app and build loop from scratch
-
Existing iPhone and iPad projects where Codex needs schemes, simulator output, screenshots, or UI automation before the work is done
-
Teams that want long-running iOS UI tasks to stay agentic and CLI-first instead of depending on the Xcode GUI starterPrompt: title: Scaffold the App and Build Loop body: >- Scaffold a starter SwiftUI app and add a build-and-launch script I can wire to a
Buildaction in my local environment.Constraints:
-
Stay CLI-first. Prefer Apple's
xcodebuild; if a cleaner setup helps, it's okay to use Tuist. -
If this repo already contains a full Xcode project, use XcodeBuildMCP to list targets, pick the right scheme, build, launch, and capture screenshots while you iterate.
-
Reuse existing models, navigation patterns, and shared utilities when they already exist.
-
Keep the app focused on iPhone and iPad unless I explicitly ask for a shared Apple-platform implementation.
-
Use a small trustworthy validation loop after each change, then expand to broader builds only when the narrower check passes.
-
Tell me whether you treated this as a greenfield scaffold or an existing-project change.
Deliver:
-
the app scaffold or requested feature slice
-
a small build-and-launch script with the exact commands
-
the smallest relevant validation steps you ran
-
the exact scheme, simulator, and checks you used relatedLinks:
-
-
label: Model Context Protocol url: /codex/mcp
-
label: Agent skills url: /codex/skills techStack:
-
need: UI framework goodDefault: "SwiftUI" why: The fastest way to prototype views, navigation, and shared state for iPhone and iPad while keeping the UI code readable.
-
need: Build tooling goodDefault: xcodebuild or Tuist why: Both keep the native build loop in the terminal instead of depending on the Xcode GUI.
-
need: Project automation goodDefault: "XcodeBuildMCP" why: A strong option once you need Codex to inspect schemes and targets, launch the app, capture screenshots, and keep iterating without leaving the agentic loop.
-
need: Distribution tooling goodDefault: "App Store Connect CLI" why: Keep your agent fully in the loop and send your app build directly to the App Store.
Scaffold the app and build loop
For greenfield work, start with plain prompting. Ask Codex to scaffold a starter iOS SwiftUI app and write a small build-and-launch script you can wire to a Build action in a local environment.
Keep the loop CLI-first. Apple's xcodebuild can list schemes and handle build, test, archive, build-for-testing, and test-without-building actions from the terminal, which lets Codex stay in an agentic loop instead of bouncing into the Xcode GUI.
If you want a cleaner project generator and you're comfortable with third-party tooling, Tuist is a good next step. It can generate and build Xcode projects without needing the GUI, while still letting Codex build and launch the app from the terminal.
Use XcodeBuildMCP once you're inside a full Xcode project and need deeper automation. That's when schemes, targets, simulator control, screenshots, logs, and UI interaction matter enough that plain shell commands stop being the whole story.
Leverage skills
For the first pass, you often don't need a skill or MCP server. Add skills once the work gets specialized or you want stronger SwiftUI conventions baked into the run.
-
SwiftUI expert is a strong general-purpose SwiftUI skill with a lot of best practices already baked in.
-
SwiftUI Pro is a broad SwiftUI review skill for modern APIs, maintainability, accessibility, and performance.
-
Liquid Glass expert helps Codex adopt the new iOS 26 Liquid Glass APIs and tune custom components so they fit the latest system design.
-
SwiftUI performance helps when a feature feels slow or a SwiftUI view update path looks suspicious. It scans for common SwiftUI mistakes and produces a prioritized report of what to fix and where the biggest gains are.
-
Swift concurrency expert helps when cryptic errors and compiler warnings start fighting the change you want to make. On GPT-5.4, you may need it less often, but it's still useful when Swift concurrency diagnostics get noisy.
-
SwiftUI view refactor helps keep files smaller and make SwiftUI code more consistent across the repo.
-
SwiftUI patterns helps reach for predictable
@Observableand@Environmentarchitecture patterns as the app grows.
To learn more about how to install and use skills, see our skills documentation.
Iterate
Once you have a first pass working, or if you're starting from an existing project, you can start iterating on the UI or behavior.
For this part, be specific about what you want to change and how you want to change it.
Make that prompting layer explicit: tell Codex whether it's working in a greenfield repo or an existing Xcode project, which iOS devices or deployment targets must keep working, and what validation loop you expect.
Example prompt
For example, if you want to add a feature to an existing app, you can ask Codex for a change like this:
Practical tips
Start with basics
Start with plain prompting for greenfield work. Ask Codex to scaffold a starter SwiftUI app and write a small build-and-launch script you can wire to a Build action in a local environment. For that first pass, you often don't need any skill or MCP server.
Use a small trustworthy validation loop
After each change, tell Codex to run the narrowest command that actually proves the contract you touched. Expand to broader builds later. This keeps Codex fast without pretending a full app build is required for every edit.
Keep the loop CLI-first
Keep the loop CLI-first. Apple's xcodebuild tool can list schemes and run build, test, archive, build-for-testing, and test-without-building actions from the terminal, which lets Codex stay in an agentic loop instead of bouncing into the Xcode GUI.
Leverage XcodeBuildMCP
Use XcodeBuildMCP as soon as you are inside a full Xcode project and need deeper automation. That's the point where schemes, targets, simulator control, screenshots, logs, and UI interaction matter enough that plain shell commands stop being the whole story.