Axiom Swift Concurrency

What it does

This skill provides guidance and support for developing concurrent Swift code using Swift 6's concurrency features. It assists in transitioning from single-threaded to concurrent programming models, debugging concurrency errors like data races and Sendable warnings, and choosing the appropriate concurrency patterns such as async/await, @MainActor, actors, or @concurrent. The skill emphasizes a shift in thinking towards isolation domains rather than thread management.

When to use it

• Starting a new project and deciding on a concurrency strategy.
• Debugging Swift 6 concurrency errors (actor isolation, data races, Sendable warnings).
• Implementing @MainActor classes or async functions.
• When UI responsiveness is impacted by CPU-intensive work or high-latency operations.

Key capabilities

• Guidance on transitioning from single-threaded to concurrent Swift code.
• Debugging support for concurrency errors (data races, Sendable warnings).
• Advice on choosing between @MainActor, nonisolated, @concurrent, and actors.
• Explanation of the differences between async/await and background thread execution.
• Best practices for structured concurrency using async let and TaskGroup.
• Guidance on bridging legacy APIs that lack async alternatives.

Example prompts

• "How do I resolve a 'Sending 'self' risks causing data races' error in Swift 6?"
• "What’s the difference between @MainActor and @concurrent?"
• "I have an image processing task freezing my UI; how should I handle it using Swift concurrency?"

Tips & gotchas

• This skill is specifically for Swift 6 (iOS 17+ / Xcode 16+) and its concurrency features. It's not suitable for general Swift syntax or SwiftUI-specific patterns.
• Remember that async does not automatically mean background execution; use @concurrent to force work off the calling actor when needed.
• Prioritize structured concurrency (using async let and TaskGroup) over unstructured tasks whenever possible.