iOS Agent Skill

Create an editable Swift app starter, implementation brief and optional XcodeGen specification/icon layers. Writes a NEW starter project; does not implement the full app idea. To have the build agent plan, write, build and screenshot the whole app, use ios_create_project and the /ios-build workflow instead.

Use this after visually reviewing a local set. Copy validated PNG files and export metadata to a NEW directory, refusing invalid or modified outputs. No upload or automatic App Store submission.

Use when designing or revising app colors. Deterministic OKLCH seed/intent palette, four appearances, contrast report, named-color Swift snippets and existing assets-CLI token JSON. Read-only: no project changes, network. Image input accepts opaque samples or an explicitly provided local sRGB PNG.

Use this to render supplied PNG/JPEG captures offline into NEW local directories with neutral frames, supplied copy, hashed metadata and a gallery. Does not capture or upload. Single-image tool requires one screen and template; variants requires multiple templates.

Use this to render supplied PNG/JPEG captures offline into NEW local directories with neutral frames, supplied copy, hashed metadata and a gallery. Does not capture or upload. Single-image tool requires one screen and template; variants requires multiple templates.

Get a compact technology overview and local source routes by default. Use view full only when the entire guide and API topic map are required.

Search dated Apple update and release-note landing pages with version-specific source links. Does not claim live results.

Get heading offsets so only the relevant section needs to be read.

Use this to choose a Screenshot Studio layout. Inspect text positions, device placement, background, callouts and safe-region requirements before rendering.

Use this when adding or reviewing Apple integrations. Get a supported integration’s APIs, guide routes, operations, permissions and device verification requirements.

Use this before sharing/exporting a local screenshot set. Verify dimensions, RGB PNG format, hashes, recorded bounds, text contrast and duplicate sources. This is not Apple approval or a complete design review.

Install a built .app bundle into a simulator using xcrun simctl install. Use after build_project or after locating a derived-data app bundle.

Use when a refinement needs another capability: applies more capability modules (with their dependencies) to an existing project and regenerates the Xcode project.

Use when the app needs a Swift package that no Apple framework covers: adds a Swift Package Manager dependency to project.yml and regenerates the Xcode project.

Use this after writing code to build for the iOS Simulator with xcodebuild. Returns {success, errors:[{file,line,column,message}], warnings, durationMs}, never the raw log. Enforces 8 attempts and 25 minutes per cycle; the clock starts at the cycle's first build. Pass newCycle (and change) on the first build of a refinement or a resumed run to start a fresh budget.

Use when planning an app to find capability modules (sign-in, payments, maps, charts, launch screen, ...) with status, cost model and required credentials, plus catalog entries that have no module yet. recipeFor returns implementation guidance for one id.

Use this after ios_plan to create the SwiftUI app project (XcodeGen project.yml, Config xcconfigs, gitignored .env secrets, starter sources) and apply capabilities in dependency order. Returns paths, scheme, files and each capability's usage notes for code generation.

Use this after a successful build to review actual light, dark and largest Dynamic Type screenshot images for one top-level screen, with approved brief and HIG checklist. capture=true first refreshes the full matrix on the simulator. Images are shared with the connected model; use synthetic sample data. A model opinion is not accessibility certification.

Use this to inspect a local HTML screen with the experimental read-only inline-style adapter. Returns versioned App IR, source hashes and unsupported-feature evidence. Does not execute scripts, fetch URLs, generate files or claim conversion fidelity. Source text is shared with the connected client; choose a non-sensitive file.

Use when the app crashes or misbehaves after launch: returns recent log lines from the running app in the simulator (unified logging, at most 500 lines).

Use this first for a new app, before any code: validates the plan (screens, navigation, design direction and palette, model sample records, capabilities), includes the default SwiftUI design system, resolves module dependencies, and writes PLAN.md with costs, credentials and what will be built. New models need at least two synthetic sampleData records. Screen ids are kebab-case; capability ids come from ios_capabilities.

Use before building an app with the iOS build agent: checks macOS, Node, Xcode, the iOS Simulator SDK, an available simulator and XcodeGen, and gives the install command for anything missing.

Use this at every stage of an /ios-build run to record the stage and the short status line shown to the user, so RUN_REPORT.md contains the same progress log.

Use this to finish every /ios-build run: writes RUN_REPORT.md from the run state with result, light/dark/XXL screenshot matrix per top-level screen when the full build loop ran, generated palette contrast evidence, capabilities (applied, status, awaiting credentials), builds, what needs the user's accounts or money, next steps and the progress log. Standalone MCP screenshots remain single captures and do not claim appearance or text-size coverage.

Use this after a successful ios_build to boot a simulator if needed (newest installed iOS runtime unless a UDID is given), install the app and launch it. Synthetic sample data is enabled by default for a useful demo; set sampleData=false to see the app's normal state. screen opens that screen via -ios-agent-screen.

Use this after ios_run to save a PNG of the simulator screen under .ios-agent/screenshots/<name>.png and record it for RUN_REPORT.md.

Use this to write or delete the app's Swift and resource files under <AppName>/ in the project. Adding or removing files regenerates the Xcode project. Paths are relative to the project folder; nothing outside it can be written.

Launch an installed app in the simulator by bundle identifier. Optional arguments are passed after the bundle id and are useful for UI-test/debug launch flags.

Validate the metadata of an Agent Skill repository rather than Swift source: SKILL.md frontmatter (required keys, kebab-case name, semver version, description length limits), subagent definitions in .claude/agents/ (name matches filename, unknown tool names, and read-only agents that are nonetheless granted Edit or Write), whether generated mirror files such as CLAUDE.md and AGENTS.md have drifted from SKILL.md, and backtick-quoted doc paths that do not resolve. Use when authoring or reviewing a skill, before publishing a release, or when a subagent or skill is not being invoked as expected.

Use this before creating local App Store screenshot sets. List structurally distinct layouts and dated output profiles. No network, capture, upload or Apple approval.

Use this when adding or reviewing Apple integrations. List supported Apple system integration workflows, conditional permissions and verification limits.

Use this to render a new locale from supplied translated copy, preserving screen order and templates. No hosted translation. Font coverage and overflow must pass; existing sets are never overwritten.

Open a URL in the simulator using xcrun simctl openurl. Use to verify deep links, universal links, onboarding routes, and state restoration.

Return a separate-layer icon specification, Apple workflow and appearance checks. Does not fabricate a native .icon document.

Return an implementation workflow and safe CLI argument array for a named app. No files are created and no build is claimed.

Prepare a local category-only GitHub draft for a confirmed significant ios-agent-mcp knowledge gap, incorrect guidance, or package failure that blocks development. Do not report minor warnings or defects in the user app. The terminal AI should show the fixed-field preview and open submissionUrl automatically for these qualifying issues; if browser access is unavailable, display the link. The user reviews and clicks Submit. This tool makes no network request and never submits automatically. Never include app source, prompts, logs, paths, credentials, or other private details. Do not reopen a di…

Use this to locate the generated local contact sheet and HTML gallery after validating a screenshot set. Returns local paths only; does not open a browser or upload.

Source-preview private feedback for a failure in iOS Agent tools, not the user app. First preview fixed categories. Show ALL fields, destination and privacy notice in chat. Submit only after the user explicitly approves that preview; never infer approval from a tool failure. No GitHub login needed for the user. Never send source, diagnostics, paths, credentials or free text. Not available until the operator configures an HTTPS receiver. Do not repeatedly offer after dismissal.

Read exact bundled file content in bounded character ranges. Use nextOffset to continue without omission; no network or user filesystem access. Offset is a JavaScript UTF-16 string index.

Use this when adding or reviewing Apple integrations. Suggest verification of integrations already evidenced in source. Does not recommend unrelated features or infer product requirements.

Use this to render supplied PNG/JPEG captures offline into NEW local directories with neutral frames, supplied copy, hashed metadata and a gallery. Does not capture or upload. Single-image tool requires one screen and template; variants requires multiple templates.

Review SiriKit/INIntent migration opportunities and, when explicitly requested, missing Apple Intelligence entity schemas or onscreen entity associations. Findings are heuristic advisories, not blanket deprecations or proof of invalid code. Use when integrating Siri, Shortcuts or Apple Intelligence.

Use when integrating or reviewing Supabase, Firebase, CloudKit, Amplify, Appwrite, Apollo, REST or WebSockets. Detects concrete imports/dependencies/configuration and redacted auth/security evidence. Read-only; no service calls or deployment claims.

Use when reviewing an existing project’s color decisions. Read-only color inventory, duplicate colors, catalog appearance coverage and conservative direct named-color text contrast. Reports evidence and limitations; custom branding is not an error.

Check a Swift project for architecture and testability defects: dependencies defaulting to live implementations, the presentation layer naming concrete data-layer types (URLSession, APIClient, ModelContext), singletons resolved inside view models, the domain layer importing UI frameworks, nested NavigationStacks, and deprecated NavigationView. Use when reviewing MVVM or Clean Architecture code, or when a screen cannot be previewed without a network.

Check a Swift project for Swift 6 concurrency and isolation defects: @Observable types missing @MainActor, Task.detached, DispatchQueue.main.async in async code, @unchecked Sendable, nonisolated(unsafe), unstructured Tasks in onAppear, empty catch blocks, and types named Task that shadow _Concurrency.Task. Use when reviewing Swift code, migrating to Swift 6, or diagnosing a data race.

Check a Swift project for retain cycles and lifetime defects: repeating Timers and block-based NotificationCenter observers capturing self strongly, Combine sinks stored in a cancellables set owned by the same object, non-weak delegate properties, stored closure properties capturing self, `unowned self` in escaping closures, and long-running unstructured Tasks that keep an object alive after its screen is gone. Use when memory grows over time, when deinit is never called, or before shipping a screen with timers or subscriptions.

Check for runtime cost that shows up as dropped frames: DateFormatter and JSONDecoder allocated inside `body`, collections sorted or filtered on every render, ForEach over indices instead of stable identity, non-lazy stacks inside a ScrollView, AsyncImage with no frame, blocking file or network I/O on the render path, and GeometryReader wrapping an entire body. Use when scrolling stutters, launch is slow, or before shipping a list-heavy screen.

Check a Swift project for security defects: hardcoded API keys, tokens, and passwords in source; credentials written to UserDefaults instead of the Keychain; App Transport Security disabled; cleartext http:// endpoints; TLS server trust accepted without evaluation; MD5 and SHA-1; Keychain items with over-permissive accessibility; non-cryptographic randomness used for nonces and salts; secrets written to logs; and string interpolation into evaluated JavaScript. Use before shipping, during a security review, or when handling credentials.

Check a Swift test suite for defects that make it unreliable or vacuous: tests that wait by sleeping, tests with no assertion at all, `await` inside an XCTAssert autoclosure (which does not compile), live URLSession calls in tests, `try!`, static mutable state that makes results order-dependent, long expectation timeouts covering for races, and XCTAssertTrue on an equality that hides both values on failure. Also reports when a project has no tests or very few. Use when tests are flaky, before trusting a green suite, or when adding coverage.

Check SwiftUI code for view and state defects: fixed font sizes and heights that break Dynamic Type, AnyView, deprecated .cornerRadius, literal spacing values instead of design tokens, materials applied over solid backgrounds, transient presentation state stored on models, legacy ObservableObject and @EnvironmentObject, and try!. Use when reviewing or building SwiftUI screens.

Use this when adding or reviewing Apple integrations. Review concrete API usage, selected privacy configuration and entitlements; reuse App Intents checks. Unknown target/configuration is reported, not treated as missing.

Run xcodebuild test for a project or workspace. Use to verify runtime/test behavior before visual review. Requires an explicit destination.

Use this when adding or reviewing Apple integrations. Return a reusable Swift file preview for a supported system integration. Read-only: never writes or overwrites project files. iOS 17+ starter; app-specific wiring and device tests required.

Capture a simulator screenshot to a PNG path using xcrun simctl io screenshot. Use as evidence for visual review and before/after comparison.

Find Apple frameworks, tools, services and legacy technologies in the bundled 405-entry source snapshot.

Search complete repository guides, Swift source, templates and assets offline. Returns compact file matches without loading bodies. Source files and guide code blocks have different verification status.

Boot a simulator by UDID using xcrun simctl boot. Use before install_app, launch_app, screenshot, or open_deep_link. This does not erase or reset simulator content.

Report selected Xcode, installed runtimes and real device profiles, including Duo when installed. Does not download or update Xcode.

List available Simulator devices using xcrun simctl. Use before booting, installing, launching, or capturing screenshots when you do not know the simulator UDID.

Start a token-protected loopback screenshot viewer for a booted device. Open the returned URL in the client sidebar/browser. Read-only visual preview; interact in the native Simulator. Not a public hosted simulator.

Stop this server’s preview for a device and remove its temporary screenshots; leaves the Simulator running.

Boot and wait for a selected available device, then open its native Simulator window for touch/keyboard interaction.

Shut down a simulator by UDID using xcrun simctl shutdown. Use after runtime validation to clean up a booted simulator. This does not erase content.

Terminate a running simulator app by bundle identifier without uninstalling it or resetting its state.

Discover Xcode MCP bridge, handshake and capabilities; discovery does not prove authorization. Use before generating Apple API code.

Discover actual Xcode tools, schemas, resources and prompts with category hints; unknown tools remain visible. Use before generating Apple API code.