rshankras/concurrency-patterns
Swift concurrency patterns including Swift 6.2 approachable concurrency, structured concurrency, actors, continuations, and migration. Use when reviewing or building async code, fixing data race errors, or migrating to Swift 6.
npx skills add https://github.com/rshankras/claude-code-apple-skills --skill concurrency-patterns
Comprehensive guide for Swift concurrency covering async/await, structured concurrency, actors, and the Swift 6.2 "Approachable Concurrency" features. Focuses on patterns that prevent data races and common mistakes that cause crashes.
What concurrency problem are you solving?
│
├─ Swift 6 compiler errors / migration
│ └─ migration-guide.md
│
├─ Swift 6.2 new features (@concurrent, isolated conformances)
│ └─ swift62-concurrency.md
│
├─ Running work in parallel (async let, TaskGroup)
│ └─ structured-concurrency.md
│
├─ Thread safety for shared mutable state
│ └─ actors-and-isolation.md
│
├─ Bridging old APIs (delegates, callbacks) to async/await
│ └─ continuations-bridging.md
│
├─ Hangs, slow parallelism, thread-pool problems, profiling
│ └─ concurrency-internals.md
│
└─ General async/await patterns
└─ See macos/coding-best-practices/modern-concurrency.md for basics
| Pattern | When to Use | Reference |
|---------|-------------|-----------|
| async let | Fixed number of parallel operations | structured-concurrency.md |
| withTaskGroup | Dynamic number of parallel operations | structured-concurrency.md |
| withDiscardingTaskGroup | Fire-and-forget parallel operations | structured-concurrency.md |
| .task { } modifier | Load data when view appears | structured-concurrency.md |
| .task(id:) modifier | Re-load when a value changes | structured-concurrency.md |
| actor | Shared mutable state protection | actors-and-isolation.md |
| @MainActor | UI-bound state and updates | actors-and-isolation.md |
| @concurrent | Explicitly offload to background (6.2) | swift62-concurrency.md |
| Isolated conformances | @MainActor type conforming to protocol (6.2) | swift62-concurrency.md |
| withCheckedContinuation | Bridge callback API to async | continuations-bridging.md |
| AsyncStream | Bridge delegate/notification API to async sequence | continuations-bridging.md |
| @TaskLocal | Context (IDs, tracing) down the task tree | structured-concurrency.md |
| Atomic / Mutex | Sendable wrappers for synchronous hot paths (Swift 6) | actors-and-isolation.md |
| Custom actor executors | Bridge existing DispatchSerialQueue synchronization | concurrency-internals.md |
| Swift Concurrency Instrument | Diagnose hangs, actor contention, continuation leaks | concurrency-internals.md |
| Strict concurrency migration | Incremental Swift 6 adoption | migration-guide.md |
Read the user's code or error messages to determine:
Based on the problem, read from this directory:
swift62-concurrency.md — Swift 6.2 approachable concurrency features, Apple's adoption doctrine, Swift 6.3/6.4 additionsstructured-concurrency.md — async let, TaskGroup, .task modifier lifecycle, task-locals, cancellation semanticsactors-and-isolation.md — Actor patterns, reentrancy, @MainActor, Sendable, Atomic/Mutexconcurrency-internals.md — cooperative pool, unsafe primitives, actor scheduling, Swift Concurrency Instrumentcontinuations-bridging.md — withCheckedContinuation, AsyncStream, built-in async sequences, legacy bridgingmigration-guide.md — Incremental Swift 6 strict concurrency adoption (WWDC24 doctrine)@MainActor (use await for long operations)Sendable conformance correct for types crossing isolation boundariesTask.isCancelled or Task.checkCancellation())Task {} where structured concurrency (.task, TaskGroup) would workwithCheckedContinuation called exactly once (not zero, not twice).task(id:) used instead of manual onChange + cancel patternsmacos/coding-best-practices/modern-concurrency.mdgenerators/networking-layer/networking-patterns.mdmacos/swiftdata-architecture/repository-pattern.mdgenerators/auth-flow/auth-patterns.md~/Downloads/docs/Swift-Concurrency-Updates.md — read if present; skip silently if absent.Take rshankras/concurrency-patterns from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.