ios-app-workflowlisted

# iOS App Workflow Coordinate an end-to-end iOS delivery without loading unrelated framework guidance or silently changing the product contract. ## Trigger Boundary Use this skill for a new app, a substantial multi-file feature, a broad refactor, or a request to finish and verify an iOS experience. For a focused issue, use only the relevant specialist skill—for example `swift-concurrency` for one isolation diagnostic or `swiftdata` for one migration problem. Do not load all installed iOS skills. Select the smallest set that covers the requested behavior and actual project stack. If a routed specialist skill is unavailable, continue from project evidence and primary documentation rather than blocking the delivery. ## Project Preflight Before implementation, inspect what is locally discoverable: - workspace/project, schemes, targets, supported platforms, and bundle identifier - deployment target, Xcode/SDK, Swift language and concurrency settings - existing architecture, folder conventions, naming, dependencies, and persistence - test targets, previews, accessibility conventions, assets, and local agent instructions - Git status and user-owned changes that must be preserved Keep the existing platform and deployment settings unless the user requested a change. When adopting a newer API, provide an availability path appropriate to the current target. Verify version claims against SDK headers, Swift Evolution/release notes, or primary Apple documentation. ## Select Speci