What problem does it solve? Swift 6.1 and earlier implicitly offload async functions to background threads, causing data-race compiler errors even in seemingly safe code. This Skill provides the patterns to adopt Swift 6.2's Approachable Concurrency model, where code stays single-threaded by default and concurrency is introduced explicitly. ## Core Features & Use Cases - Data-Race Error Resolution: Fix "Sending risks causing data races" errors by keeping async functions on the calling actor instead of implicit background offloading. - Isolated Conformances: Implement protocol conformances on MainActor-isolated types safely using @MainActor conformance syntax. - Explicit Background Offloading: Use @concurrent on nonisolated types to move CPU-intensive work like image processing to the concurrent thread pool. - Use Case: When migrating an app to Xcode 26, enable MainActor default inference so view models and global singletons like StickerLibrary.shared become implicitly MainActor-isolated without manual annotations, then offload only hot paths with @concurrent. ## Quick Start Ask the AI to migrate my Swift class to Swift 6.2 concurrency and fix the data-race errors in my async image processing code.