← ClaudeAtlas

ios-app-workflowlisted

Plan, build, refactor, and verify a complete iOS app or substantial end-to-end feature. Use when work spans project structure, SwiftUI implementation, persistence, testing, and Simulator delivery; do not use for a narrow framework question or isolated compiler error.
thienqo/ios-skills · ★ 11 · AI & Automation · score 69
Install: claude install-skill thienqo/ios-skills
# iOS App Workflow Coordinate an end-to-end iOS delivery without loading unrelated framework guidance or silently changing the product contract. ## Contents - [Trigger Boundary](#trigger-boundary) - [Project Preflight](#project-preflight) - [Select Specialist Skills](#select-specialist-skills) - [Delivery Contract](#delivery-contract) - [Structure and Naming](#structure-and-naming) - [Implementation](#implementation) - [Verification](#verification) - [Completion](#completion) - [iOS 27 Updates](#ios-27-updates) - [Common Mistakes](#common-mistakes) - [Review Checklist](#review-checklist) - [References](#references) ## 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,