iOS App Workflow
Coordinate an end-to-end iOS delivery without loading unrelated framework guidance or silently changing the product contract.
Contents
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 Specialist Skills
Load only skills needed for the current slice:
| Concern |
Route to |
| State ownership, view composition, previews, file boundaries |
swiftui-patterns |
| Layout, lists, forms, search, overlays |
swiftui-layout-components |
| Cross-size adaptation, clipping, overlap, safe areas, keyboard layout |
swiftui-responsive-layout |
| Navigation, sheets, tabs, deep links |
swiftui-navigation |
| Motion and transitions |
swiftui-animation |
| Liquid Glass and iOS 26 visual APIs |
swiftui-liquid-glass |
| Architecture choice or migration |
swift-architecture |
| Isolation and async mechanics |
swift-concurrency |
| Persistence |
swiftdata or core-data, according to the existing stack |
| Accessibility |
ios-accessibility |
| Unit tests |
swift-testing |
| Build, launch, screenshots, and runtime verification |
ios-simulator |
Add framework-specific skills only when the feature actually uses those frameworks.
Delivery Contract
Write down or infer conservatively:
- required user flows and data behavior
- visual direction and supported appearances/sizes
- persistence and migration expectations
- accessibility and motion requirements
- offline/network/error behavior where relevant
- minimum verification needed to call the work complete
If the request is a refactor, preserve layout, navigation, state ownership semantics, identity, accessibility, animation/side-effect timing, persistence, and public API unless a change is explicitly requested.
Structure and Naming
Follow coherent existing conventions. For a growing SwiftUI app, prefer feature-first folders with small shared layers such as App, DesignSystem, Models, Services, and Features/<Feature>.
The app entry point should use the product name; screens and components should use domain-plus-role names. Match each file to its primary type. Avoid generic names like ContentView, MainView, Helper, or Manager when a concrete role is known.
Extract a dedicated view for meaningful branching/layout, local lifecycle or gesture state, narrow dependencies, or independent preview value. Do not split every tiny fragment, and do not treat extensions or // MARK: headings as actual boundaries.
Implementation
Work in vertical slices that leave the target buildable after meaningful boundaries:
- establish app/feature wiring and model boundaries
- implement the primary happy path
- add persistence, errors, empty/loading states, and secondary actions in scope
- add accessibility and motion adaptations with the UI, not as an afterthought
- add tests and deterministic previews for behavior that can regress
Keep business rules and reusable effects out of layout code. Preserve user changes in a dirty worktree and avoid unrelated cleanup.
Verification
Use the smallest evidence set that proves the requested outcome:
- build the affected target with the actual scheme/destination
- run relevant unit tests
- render deterministic previews where useful
- install and launch on an explicit Simulator UDID
- exercise primary actions, failure/empty states, and persistence across relaunch when applicable
- verify important accessibility labels/actions, Dynamic Type, and Reduce Motion behavior
- capture screenshots or focused logs when visual/runtime proof matters
Simulator verification is not proof for device-only hardware or production APNs behavior. Read Delivery Checklist for mode-specific proof.
Completion
Report the result first, then changed structure, verification performed, and any real limitation. Do not commit, push, publish, change signing, or mutate external systems unless the user authorized that action.
iOS 27 Updates
- Xcode 27 ships Swift 6.4 and the iOS 27 SDK, installs only on Apple silicon Macs, and requires macOS Tahoe 26.6 or later. The ld64 linker is removed; Swift Build is the default SwiftPM backend.
- Building with the 27 SDK: adopt the scene-based life cycle, include a launch screen key, expect the
@State macro and PreviewProvider deprecation (see swiftui-patterns).
- Xcode 27 adds coding-agent integration (Anthropic, Google, OpenAI), MCP and Agent Client Protocol plugins, and
xcrun mcp-server (enable with sudo xcrun mcp-server enable).
- Device Hub replaces ad hoc device and simulator interaction, with network pairing for iPhone, iPad, and Apple Watch on 27 and later.
Sources: https://sosumi.ai/documentation/xcode-release-notes/xcode-27-release-notes
Common Mistakes
- Verifying solely on the iOS Simulator when the feature involves Bluetooth, camera, or push notifications.
- Delaying release-configuration builds and archive testing until the final submission step.
- Overwriting existing project conventions or folder structures without following established patterns.
- Loading every available skill into context rather than choosing only the relevant specialists.
- Performing destructive git operations or modifying external signing credentials without approval.
Review Checklist
References
- Mode-specific delivery and verification checklist
1---2name: ios-app-workflow3description: "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."4metadata:5 source: https://skillmd.com/skills/thiennc-tesoglobal/ios-app-workflow6---78# iOS App Workflow910Coordinate an end-to-end iOS delivery without loading unrelated framework guidance or silently changing the product contract.1112## Contents1314- [Trigger Boundary](#trigger-boundary)15- [Project Preflight](#project-preflight)16- [Select Specialist Skills](#select-specialist-skills)17- [Delivery Contract](#delivery-contract)18- [Structure and Naming](#structure-and-naming)19- [Implementation](#implementation)20- [Verification](#verification)21- [Completion](#completion)22- [iOS 27 Updates](#ios-27-updates)23- [Common Mistakes](#common-mistakes)24- [Review Checklist](#review-checklist)25- [References](#references)2627## Trigger Boundary2829Use 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.3031Do not load all installed iOS skills. Select the smallest set that covers the requested behavior and actual project stack.3233If a routed specialist skill is unavailable, continue from project evidence and primary documentation rather than blocking the delivery.3435## Project Preflight3637Before implementation, inspect what is locally discoverable:3839- workspace/project, schemes, targets, supported platforms, and bundle identifier40- deployment target, Xcode/SDK, Swift language and concurrency settings41- existing architecture, folder conventions, naming, dependencies, and persistence42- test targets, previews, accessibility conventions, assets, and local agent instructions43- Git status and user-owned changes that must be preserved4445Keep 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.4647## Select Specialist Skills4849Load only skills needed for the current slice:5051| Concern | Route to |52|---|---|53| State ownership, view composition, previews, file boundaries | `swiftui-patterns` |54| Layout, lists, forms, search, overlays | `swiftui-layout-components` |55| Cross-size adaptation, clipping, overlap, safe areas, keyboard layout | `swiftui-responsive-layout` |56| Navigation, sheets, tabs, deep links | `swiftui-navigation` |57| Motion and transitions | `swiftui-animation` |58| Liquid Glass and iOS 26 visual APIs | `swiftui-liquid-glass` |59| Architecture choice or migration | `swift-architecture` |60| Isolation and async mechanics | `swift-concurrency` |61| Persistence | `swiftdata` or `core-data`, according to the existing stack |62| Accessibility | `ios-accessibility` |63| Unit tests | `swift-testing` |64| Build, launch, screenshots, and runtime verification | `ios-simulator` |6566Add framework-specific skills only when the feature actually uses those frameworks.6768## Delivery Contract6970Write down or infer conservatively:7172- required user flows and data behavior73- visual direction and supported appearances/sizes74- persistence and migration expectations75- accessibility and motion requirements76- offline/network/error behavior where relevant77- minimum verification needed to call the work complete7879If the request is a refactor, preserve layout, navigation, state ownership semantics, identity, accessibility, animation/side-effect timing, persistence, and public API unless a change is explicitly requested.8081## Structure and Naming8283Follow coherent existing conventions. For a growing SwiftUI app, prefer feature-first folders with small shared layers such as `App`, `DesignSystem`, `Models`, `Services`, and `Features/<Feature>`.8485The app entry point should use the product name; screens and components should use domain-plus-role names. Match each file to its primary type. Avoid generic names like `ContentView`, `MainView`, `Helper`, or `Manager` when a concrete role is known.8687Extract a dedicated view for meaningful branching/layout, local lifecycle or gesture state, narrow dependencies, or independent preview value. Do not split every tiny fragment, and do not treat extensions or `// MARK:` headings as actual boundaries.8889## Implementation9091Work in vertical slices that leave the target buildable after meaningful boundaries:92931. establish app/feature wiring and model boundaries942. implement the primary happy path953. add persistence, errors, empty/loading states, and secondary actions in scope964. add accessibility and motion adaptations with the UI, not as an afterthought975. add tests and deterministic previews for behavior that can regress9899Keep business rules and reusable effects out of layout code. Preserve user changes in a dirty worktree and avoid unrelated cleanup.100101## Verification102103Use the smallest evidence set that proves the requested outcome:104105- build the affected target with the actual scheme/destination106- run relevant unit tests107- render deterministic previews where useful108- install and launch on an explicit Simulator UDID109- exercise primary actions, failure/empty states, and persistence across relaunch when applicable110- verify important accessibility labels/actions, Dynamic Type, and Reduce Motion behavior111- capture screenshots or focused logs when visual/runtime proof matters112113Simulator verification is not proof for device-only hardware or production APNs behavior. Read [Delivery Checklist](references/delivery-checklist.md) for mode-specific proof.114115## Completion116117Report the result first, then changed structure, verification performed, and any real limitation. Do not commit, push, publish, change signing, or mutate external systems unless the user authorized that action.118119## iOS 27 Updates120121- Xcode 27 ships Swift 6.4 and the iOS 27 SDK, installs only on Apple silicon Macs, and requires macOS Tahoe 26.6 or later. The ld64 linker is removed; Swift Build is the default SwiftPM backend.122- Building with the 27 SDK: adopt the scene-based life cycle, include a launch screen key, expect the `@State` macro and `PreviewProvider` deprecation (see `swiftui-patterns`).123- Xcode 27 adds coding-agent integration (Anthropic, Google, OpenAI), MCP and Agent Client Protocol plugins, and `xcrun mcp-server` (enable with `sudo xcrun mcp-server enable`).124- Device Hub replaces ad hoc device and simulator interaction, with network pairing for iPhone, iPad, and Apple Watch on 27 and later.125126Sources: https://sosumi.ai/documentation/xcode-release-notes/xcode-27-release-notes127128## Common Mistakes129130- Verifying solely on the iOS Simulator when the feature involves Bluetooth, camera, or push notifications.131- Delaying release-configuration builds and archive testing until the final submission step.132- Overwriting existing project conventions or folder structures without following established patterns.133- Loading every available skill into context rather than choosing only the relevant specialists.134- Performing destructive git operations or modifying external signing credentials without approval.135136## Review Checklist137138- [ ] Only relevant specialist skills were loaded139- [ ] Existing deployment target, architecture, and user changes were preserved140- [ ] Names and file boundaries reflect product/domain roles141- [ ] Primary flow plus in-scope empty/error/persistence behavior is implemented142- [ ] Accessibility and Reduce Motion are handled proportionally143- [ ] A real target builds and relevant tests pass144- [ ] Simulator/device claims match the evidence collected145- [ ] No external mutation exceeded user authorization146147## References148149- [Mode-specific delivery and verification checklist](references/delivery-checklist.md)