Ios Dev

Prisma-Labs-Dev/apple-skills/skills/ios-dev

by Prisma-Labs-Dev498626005e65783ebe8570a103b2335cf397768cNo licenseListed Oct 9, 2026Updated Oct 9, 2026

Start here for any iOS or SwiftUI task. Coordinates best-practice guides, correctness checks, and full Apple API references. Use before navigating to other Apple skills — for building, reviewing, refactoring, or debugging iOS apps.

Instructions onlySoftware Development
AI-generated overview

Entry-point guide for iOS and SwiftUI work that routes tasks to Apple guides, API references and a correctness checklist.

What it does
Acts as a starting point for iOS and SwiftUI tasks by routing each topic (state, navigation, layout, testing, concurrency, persistence and others) to a specific guide or grepable Apple API reference. It also provides a correctness checklist of hard rules for reviewing code, plus workflows for reviewing, improving and building features. It produces routing decisions, review findings and guidance rather than code or files.
When to use it
Use before starting any iOS or SwiftUI task, such as building a new feature, reviewing or refactoring existing app code, or debugging SwiftUI behavior. It is meant to be consulted first so the right Apple guide or API reference is loaded for the topic at hand.
Requirements
No scripts; instructions only. It references other Apple skills and framework reference documents that must be available in the agent's skill collection.

iOS Development

Start here. This skill coordinates the Apple skills collection — it tells you which skill to use and when, so you get opinionated guidance and full API references together.

Operating Rules

  • SwiftUI and UIKit are both first-class — pick whichever fits the task. UIKit is a valid choice whenever it gives more control or flexibility; when bridging the two, watch state sync, lifecycle, and animation/environment boundaries.
  • Do not enforce specific architectures (MVVM, VIPER, MV, TCA, etc.) — encourage separating business logic from views without mandating how
  • Hold a high bar for UI craft: apps should feel current-generation — fluid, design-forward, alive. Sweat the tiny details. Custom components, novel interactions, and custom Metal shaders are all in-bounds when they serve the experience; system defaults are a floor, not a ceiling.
  • Do not prescribe how that craft is delivered — no house style, no "Apple-approved" gatekeeping, no aesthetic checklists. Design direction is your own judgment call, made per app. The hig and ios-liquid-glass skills document what the system provides; they are references, not style mandates. When the task is designing a screen or making it look good, there is no doc to route to — design from your own taste; grep references only when you need API mechanics or a factual minimum (e.g. hit-target sizes).
  • Present performance optimizations as suggestions backed by reasoning, not blanket requirements
  • When you need exact API details, grep the framework reference skills — they contain full Apple documentation

Task Workflows

Review existing code

  1. Read the code and identify which topics apply
  2. Run the Correctness Checklist below — violations are bugs
  3. Use the Topic Router to load the relevant guide for each topic
  4. For API correctness, grep the matching framework reference skill

Improve existing code

  1. Run the correctness checklist first
  2. For performance issues: use guide-swiftui-performance-audit
  3. For navigation, state, or pattern questions: use Apple's swiftui-specialist (shipped with Xcode 27; exported to the user skills dir), then the swiftui API reference
  4. For API details: grep the matching framework reference skill

Build a new feature

  1. Design data flow first — identify owned vs. injected state
  2. For UI patterns and app wiring: use Apple's swiftui-specialist, then the swiftui API reference
  3. For API details: grep the matching framework reference skill
  4. Structure views for optimal diffing — extract subviews early
  5. Run the correctness checklist before finishing

Topic Router

The Guide column has opinionated, short pattern guides. The API Reference column has full Apple documentation as grepable Markdown — use apple-docs-index to find which framework has what.

TopicGuideAPI Reference
State managementswiftui-specialist (Apple, Xcode 27)swiftui (state.md, binding.md, observation.md, environment.md)
View composition—swiftui (view-protocol.md)
Performanceguide-swiftui-performance-audit—
Navigationswiftui-specialist (Apple, Xcode 27)swiftui (navigationstack.md, navigationsplitview.md, navigationlink.md)
Sheets & modalsswiftui-specialist (Apple, Xcode 27)swiftui (sheet.md, inspector.md, alert.md, confirmationdialog.md)
Lists & ForEachswiftui-specialist (Apple, Xcode 27)swiftui (list.md)
ScrollViewswiftui-specialist (Apple, Xcode 27)swiftui (scrollview.md)
Forms & input—swiftui (form.md, textfield.md, picker.md, toggle.md, slider.md)
Chartsguide-swiftui-chartsswiftui (chart.md, charts-overview.md)
Animationsswiftui-specialist (Apple, Xcode 27)swiftui (swiftui-overview.md)
Layoutswiftui-specialist (Apple, Xcode 27)swiftui (geometryreader.md, grid.md, hstack.md, vstack.md, zstack.md, spacer.md)
TabViewswiftui-specialist (Apple, Xcode 27)swiftui (tabview.md)
Liquid Glass—ios-liquid-glass
Accessibilityswiftui-specialist (Apple, Xcode 27)hig (a11y/ergonomic facts)
macOS appsguide-macos-spm-packagingswiftui, uikit
Data persistenceguide-swiftdataswiftdata
Testingguide-swift-testingswift-testing, xcuitest
Concurrencyguide-swift-concurrencyswift-concurrency
In-app purchases—storekit
Maps—mapkit
Health data—healthkit
Notifications—usernotifications
App Intents / Siriapp-intents-specialist, app-intents-whats-new-27 (Apple, Xcode 27)—
Widgets—widgetkit
App Store metadataapple-aso—
Finding docsapple-docs-index—

Correctness Checklist

These are hard rules — violations are always bugs:

  • @State properties are private
  • @Binding only where a child needs to mutate parent state
  • Values passed in are never declared as @State — they silently ignore updates
  • Use @State with @Observable classes — not @StateObject or ObservableObject
  • Use @Bindable for injected observables that need bindings
  • ForEach uses stable identity — never .indices on dynamic content
  • Each ForEach element produces a constant number of views
  • .animation(_:value:) always includes the value: parameter
  • @FocusState properties are private
  • @Observable classes are @MainActor — Swift 6 strict concurrency requires it
  • Property wrappers (@AppStorage, @SceneStorage, @Query) inside @Observable classes are marked @ObservationIgnored — they conflict with the macro and cause compiler errors
  • No business logic in body — use .task, .onChange, or methods
  • No AnyView unless truly unavoidable — fix with better composition

Related Skills

System API reference:

  • /ios-liquid-glass — Liquid Glass API reference

Workflow guides:

  • /swiftui-specialist — Apple's SwiftUI best practices (Xcode 27): structure, data flow, environment, ForEach identity, localization, soft deprecations
  • /swiftui-whats-new-27 — iOS 27 SwiftUI changes (@State macro, @ContentBuilder, reorderable, toolbar overflow)
  • /guide-swiftui-charts — Marks, axes, selection, styling, accessibility
  • /guide-swiftui-performance-audit — Diagnose and fix performance issues
  • /guide-swift-testing — Swift Testing patterns, async tests, common agent mistakes
  • /guide-swift-concurrency — Concurrency patterns, actors, diagnostics, bug patterns
  • /guide-swiftdata — SwiftData patterns, predicates, CloudKit constraints
  • /guide-macos-spm-packaging — Build macOS apps with SwiftPM

Utilities:

  • /apple-docs-index — Find the right Apple documentation
  • /apple-aso — App Store Optimization

Source and attribution

Source:Prisma-Labs-Dev/apple-skillsinskills/ios-devat commit4986260

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal