---
name: native-ios-orchestrator
description: "Route a native Apple-platform task to the right skill among the iOS specialists — Swift 6.2 concurrency, SwiftUI architecture, actor persistence, protocol-based DI/testing, on-device FoundationModels, Liquid Glass design, and icon assets. USE WHEN a user is building, modernizing, or shipping a native iOS/macOS app in Swift but hasn't named the specific concern."
cluster: native-ios
version: 1.0.0
---

# Native iOS Orchestrator

The single entry skill for native Apple-platform (Swift / SwiftUI) work. It locates the task on
the **layer × concern** map and delegates to one of 7 specialist spokes. The cross-cutting fact
every spoke shares — the **iOS 26 / Swift 6.2 / Xcode 26 baseline**, its availability-gating
discipline, and the data-race-safety model — lives in `native-ios-core`; read it before adopting
the new concurrency mode or any of the iOS 26 frameworks.

## Cluster map (spoke → role)

- `swift-concurrency-6-2` — the **language model**: Swift 6.2 Approachable Concurrency, single-threaded by default, `@concurrent` for explicit offloading, isolated conformances.
- `swiftui-patterns` — the **UI architecture**: `@Observable` state, view composition, `NavigationStack`, list/render performance.
- `swift-actor-persistence` — the **storage layer**: actor-backed in-memory cache + file persistence, data races eliminated by the compiler.
- `swift-protocol-di-testing` — the **testability seam**: small focused protocols for file system / network / external APIs, mocked under Swift Testing.
- `foundation-models-on-device` — the **on-device AI**: Apple FoundationModels LLM, `@Generable` guided generation, tool calling, snapshot streaming.
- `liquid-glass-design` — the **design system**: iOS 26 Liquid Glass material for SwiftUI, UIKit, WidgetKit.
- `ios-icon-gen` — the **asset pipeline**: PNG icon imagesets for Xcode asset catalogs from SF Symbols or Iconify.

## Routing rules by intent

**Set the foundation**
- "Data races / async errors / migrate to Swift 6.2 / MainActor architecture" → `swift-concurrency-6-2`  *(baseline in `native-ios-core`)*
- "How do I structure views / state / navigation?" → `swiftui-patterns`

**Build the app body**
- Local/offline storage, caching, thread-safe shared state → `swift-actor-persistence`
- Make it testable, mock I/O, deterministic tests → `swift-protocol-di-testing`
- On-device text generation, structured extraction, AI tool calls → `foundation-models-on-device`

**Make it look native**
- Glass buttons/cards/toolbars, morphing, iOS 26 material → `liquid-glass-design`
- App/feature icons, asset-catalog imagesets → `ios-icon-gen`

## Standard flow

1. Locate the task: which layer (language → architecture → storage/test/AI → design → assets) and which concern.
2. If it touches **concurrency isolation, `Sendable`, availability gating, or any iOS 26-only API**, pull the baseline from `native-ios-core` first — these interlock across spokes (a `@MainActor` decision in concurrency changes how SwiftUI, actors, and DI are written).
3. Delegate to the spoke(s). Multi-step asks fan out in layer order (e.g. "build an AI feature with a glass UI" → `swift-concurrency-6-2` isolation → `foundation-models-on-device` → `liquid-glass-design`).
4. Return: chosen spoke(s), the deployment-target / availability implications, and the next action.

## Guardrails

See `native-ios-core`. In short: target **Swift 6.2 + Xcode 26**, and treat every iOS 26-only API
(Liquid Glass, FoundationModels, the newest SwiftUI affordances) as **availability-gated** — wrap
it in `if #available` / `SystemLanguageModel.availability` with a real fallback rather than raising
the whole app's deployment target silently. Prefer `@Observable` over `ObservableObject`, actors
over manual locks, and isolated-by-default concurrency over ad-hoc background dispatch. Don't widen
a deployment target or weaken data-race safety without saying so explicitly.