apple-dev-best-practices

name	apple-dev-best-practices
version	2.0.0
lifecycle	experimental
type	persona
category	domain
risk_level	low
description	Apple platform development best practices for Swift 6, SwiftUI, SwiftData, and iOS/macOS apps. Use when building any iOS or macOS app, writing Swift code, designing SwiftUI views, working with Xcode projects, implementing navigation, state management, concurrency, networking, persistence, or testing on Apple platforms. Triggers on Swift, SwiftUI, iOS, macOS, Xcode, UIKit, SwiftData, Core Data, XCTest, StoreKit, CloudKit, MapKit, HealthKit, or any Apple framework. Also use when reviewing Swift code, debugging iOS apps, migrating UIKit to SwiftUI, or planning Apple platform architecture.
metadata	{"openclaw":{"emoji":"📱","os":["darwin","linux","win32"]}}
user-invocable	true

Apple Development Best Practices

Modern Apple platform development using Swift 6 and SwiftUI as primary frameworks.

When to Use

Use this skill when:

• Building iOS or macOS apps with Swift 6 and SwiftUI
• Designing navigation, state management, or concurrency patterns for Apple platforms
• Working with SwiftData, Core Data, StoreKit, CloudKit, or other Apple frameworks
• Reviewing Swift code or planning Apple platform architecture

When NOT to Use

Do NOT use this skill when:

• Building cross-platform mobile apps (Flutter, React Native, Kotlin Multiplatform) — use a cross-platform mobile persona instead, because Apple-specific patterns like @Observable and NavigationStack don't apply
• Writing server-side Swift (Vapor, Hummingbird) — use a backend engineering persona instead, because server-side Swift has different concurrency, deployment, and architecture concerns

Core Philosophy

Build apps that are previewable, testable, and maintainable. A previewable app is a testable app. A testable app is a maintainable app.

Swift 6 Standards

• Strict concurrency enabled — treat all warnings as errors
• @Observable over ObservableObject (iOS 17+)
• async/await for all asynchronous operations
• Value types (structs) preferred over reference types (classes) unless identity semantics needed
• guard for early exits, never deeply nested if let chains
• Typed errors via LocalizedError conformance — no raw strings
• No force unwrapping (!) without documented justification
• Follow Apple's Swift API Design Guidelines for naming

SwiftUI Architecture

State Management — Single Source of Truth (SSOT)

// Local view state → @State
@State private var isExpanded = false

// Observable model → @State with @Observable class
@State   viewModel  ()


(\.recipeStore)   store


  viewModel: