Skip to main content
skill CX Codex

build-iphone-apps — Claude Code skill: what it does, how to install

build-iphone-apps builds native iPhone apps in Swift using SwiftUI and UIKit via terminal commands without opening the Xcode IDE. Handles everything from code to App Store shipping.

MIT ★ 1,988 updated 2026-04-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources
Open on GitHub

What build-iphone-apps does

This skill frames Claude Code as the developer and the user as the product owner. You provide requirements and inspect visual outcomes in the simulator, while the assistant generates Swift code and verifies functionality directly through xcodebuild, xcrun simctl, and xcsift. The setup targets iOS 26 while preserving backwards compatibility down to iOS 18.

Preconfigured workflows guide project scaffolding, bug investigations, feature work, unit testing, performance profiling, and TestFlight submissions. Every code modification triggers a strict loop: compile for the iPhone 16 simulator, run the test target, and confirm a crash-free launch.

Without macOS command-line tools and local simulator runtimes configured, the agent cannot compile or verify your app.

What it helps with

  • scaffold a native SwiftUI or UIKit iPhone project from the command line
  • run automated xcodebuild test suites inside the iOS simulator
  • inspect screen behavior and layout through xcrun simctl
  • prepare release builds for TestFlight and App Store distribution

Example prompts for the agent

  • Build a new habit tracking iOS app using SwiftUI
  • Find and fix the memory leak in the data sync routine
  • Prepare this iOS build for TestFlight and run all verification tests

How to install build-iphone-apps

1Plugin marketplace

/plugin marketplace add glittercowboy/taches-cc-resources
/plugin install taches-cc-resources@taches-cc-resources

This installs the whole taches-cc-resources plugin with all its skills

2Skills CLI (Vercel)

npx skills add glittercowboy/taches-cc-resources --skill build-iphone-apps -a claude-code

3Manually: put the files in place

~/.claude/skills/iphone-apps/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/iphone-apps/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about build-iphone-apps

How to install build-iphone-apps in Claude Code?

Run /plugin marketplace add glittercowboy/taches-cc-resources in Claude Code, then execute /plugin install taches-cc-resources@taches-cc-resources.

What does build-iphone-apps do?

It manages the end-to-end lifecycle of iOS apps in Swift via the terminal, covering creation, debugging, unit testing, optimization, and App Store submission.

Does this skill require the Xcode graphical interface?

No, it operates purely via the command line, though your macOS machine must have xcodebuild and xcrun simctl available to compile and test code.

Source text

SKILL.md · MIT
---
name: build-iphone-apps
description: Build professional native iPhone apps in Swift with SwiftUI and UIKit. Full lifecycle - build, debug, test, optimize, ship. CLI-only, no Xcode. Targets iOS 26 with iOS 18 compatibility.
---

<essential_principles>
## How We Work

**The user is the product owner. Claude is the developer.**

The user does not write code. The user does not read code. The user describes what they want and judges whether the result is acceptable. Claude implements, verifies, and reports outcomes.

### 1. Prove, Don't Promise

Never say "this should work." Prove it:
```bash
xcodebuild -destination 'platform=iOS Simulator,name=iPhone 16' build 2>&1 | xcsift
xcodebuild test -destination 'platform=iOS Simulator,name=iPhone 16'
xcrun simctl boot "iPhone 16" && xcrun simctl launch booted com.app.bundle
```
If you didn't run it, you don't know it works.

### 2. Tests for Correctness, Eyes for Quality

| Question | How to Answer |
|----------|---------------|
| Does the logic work? | Write test, see it pass |
| Does it look right? | Launch in simulator, user looks at it |
| Does it feel right? | User uses it |
| Does it crash? | Test + launch |
| Is it fast enough? | Profiler |

Tests verify *correctness*. The user verifies *desirability*.

### 3. Report Outcomes, Not Code

**Bad:** "I refactored DataService to use async/await with weak self capture"
**Good:** "Fixed the memory leak. `leaks` now shows 0 leaks. App tested stable for 5 minutes."

The user doesn't care what you changed. The user cares what's different.

### 4. Small Steps, Always Verified

```
Change → Verify → Report → Next change
```

Never batch up work. Never say "I made several changes." Each change is verified before the next. If something breaks, you know exactly what caused it.

### 5. Ask Before, Not After

Unclear requirement? Ask now.
Multiple valid approaches? Ask which.
Scope creep? Ask if wanted.
Big refactor needed? Ask permission.

Wrong: Build for 30 minutes, then "is this what you wanted?"
Right: "Before I start, does X mean Y or Z?"

### 6. Always Leave It Working

Every stopping point = working state. Tests pass, app launches, changes committed. The user can walk away anytime and come back to something that works.
</essential_principles>

<intake>
**Ask the user:**

What would you like to do?
1. Build a new app
2. Debug an existing app
3. Add a feature
4. Write/run tests
5. Optimize performance
6. Ship/release
7. Something else

**Then read the matching workflow from `workflows/` and follow it.**
</intake>

<routing>
| Response | Workflow |
|----------|----------|
| 1, "new", "create", "build", "start" | `workflows/build-new-app.md` |
| 2, "broken", "fix", "debug", "crash", "bug" | `workflows/debug-app.md` |
| 3, "add", "feature", "implement", "change" | `workflows/add-feature.md` |
| 4, "test", "tests", "TDD", "coverage" | `workflows/write-tests.md` |
| 5, "slow", "optimize", "performance", "fast" | `workflows/optimize-performance.md` |
| 6, "ship", "release", "TestFlight", "App Store" | `workflows/ship-app.md` |
| 7, other | Clarify, then select workflow or references |
</routing>

<verification_loop>
## After Every Change

```bash
# 1. Does it build?
xcodebuild -scheme AppName -destination 'platform=iOS Simulator,name=iPhone 16' build 2>&1 | xcsift

# 2. Do tests pass?
xcodebuild -scheme AppName -destination 'platform=iOS Simulator,name=iPhone 16' test

# 3. Does it launch? (if UI changed)
xcrun simctl boot "iPhone 16" 2>/dev/null || true
xcrun simctl install booted ./build/Build/Products/Debug-iphonesimulator/AppName.app
xcrun simctl launch booted com.company.AppName
```

Report to the user:
- "Build: ✓"
- "Tests: 12 pass, 0 fail"
- "App launches in simulator, ready for you to check [specific thing]"
</verification_loop>

<when_to_test>
## Testing Decision

**Write a test when:**
- Logic that must be correct (calculations, transformations, rules)
- State changes (add, delete, update operations)
- Edge cases that could break (nil, empty, boundaries)
- Bug fix (test reproduces bug, then proves it's fixed)
- Refactoring (tests prove behavior unchanged)

**Skip tests when:**
- Pure UI exploration ("make it blue and see if I like it")
- Rapid prototyping ("just get something on screen")
- Subjective quality ("does this feel right?")
- One-off verification (launch and check manually)

**The principle:** Tests let the user verify correctness without reading code. If the user needs to verify it works, and it's not purely visual, write a test.
</when_to_test>

<reference_index>
## Domain Knowledge

All in `references/`:

**Architecture:** app-architecture, swiftui-patterns, navigation-patterns
**Data:** data-persistence, networking
**Platform Features:** push-notifications, storekit, background-tasks
**Quality:** polish-and-ux, accessibility, performance
**Assets & Security:** app-icons, security, app-store
**Development:** project-scaffolding, cli-workflow, cli-observability, testing, ci-cd
</reference_index>

<workflows_index>
## Workflows

All in `workflows/`:

| File | Purpose |
|------|---------|
| build-new-app.md | Create new iOS app from scratch |
| debug-app.md | Find and fix bugs |
| add-feature.md | Add to existing app |
| write-tests.md | Write and run tests |
| optimize-performance.md | Profile and speed up |
| ship-app.md | TestFlight, App Store submission |
</workflows_index>

© Lex Christopherson · MIT · glittercowboy/taches-cc-resources

Similar skills

All skills for Mobile →

From the same set48

The whole set →
history history — a command to research historical attempts at solving a task: what was tried before, what worked, what mistakes to avoid. Helps prevent repeating errors and apply lessons from experience. CX Codex +1 ★ 1,988repo stars technical Researches technical implementation options, evaluates libraries and tradeoffs, and saves a ready architecture brief into Markdown. CX Codex +1 ★ 1,988repo stars feasibility feasibility is a command that assesses whether a project can meet its constraints and recommends whether to proceed, revise terms, or stop. CX Codex +1 ★ 1,988repo stars landscape Maps a domain landscape: identifies key players, available tools, trends and gaps. Takes a domain name or works in current context without arguments. CX Codex +1 ★ 1,988repo stars run-prompt This command sends prompts from ./prompts/ to fresh sub-task contexts, one at a time or in parallel. Use it to run independent work concurrently or keep dependent tasks in order. CX Codex +1 ★ 1,988repo stars open-source Finds existing open-source libraries and tools for the problem at hand, checks whether they are still maintained, and says whether to use one or build your own. CX Codex +1 ★ 1,988repo stars create-mcp-servers create-mcp-servers guides development of Model Context Protocol servers in Python and TypeScript for Claude Code, covering architecture, secrets isolation, and debugging. CX Codex +1 ★ 1,988repo stars slash-command-auditor slash-command-auditor audits Claude Code slash-command .md files for structure, arguments, context loading, tool scope, and security issues. CX Codex ★ 1,988repo stars

Project sponsors

Companies that keep this analytics open