← LeaderboardThe Skill Leaderboard

concurrency-patterns

Skill file skills/swift/concurrency-patterns/SKILL.md in rshankras/claude-code-apple-skills. Read the publisher’s upstream source.

Description could not be read from the source metadata.

Published by rshankras ↗rshankras/claude-code-apple-skills

Try your first task

concurrency-patterns

Start a fresh conversation. Replace the highlighted placeholders.

Use concurrency-patterns to review [Swift code or compiler errors] for [concurrency problem], recommend a Swift 6-compatible design, and provide focused code changes that address races, isolation, cancellation, or UI-safety issues.

Required inputs

  • [Swift code or compiler errors]
  • [concurrency problem]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: concurrency-patternsdescription: 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.allowed-tools: [Read, Glob, Grep]last_verified: 2026-07-16review_by: 2027-06-22os_version: iOS 27 / macOS 27

Swift 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.

When This Skill Activates

  • User has data race errors or actor isolation compiler errors
  • User is migrating to Swift 6 strict concurrency
  • User asks about async/await, actors, Sendable, TaskGroup, or MainActor
  • User needs to bridge legacy completion-handler APIs to async/await
  • User is working with Swift 6.2 features (@concurrent, isolated conformances)
  • User has concurrency bugs (actor reentrancy, task cancellation, UI freezes)

Decision Tree

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

Quick Reference

PatternWhen to UseReference
async letFixed number of parallel operationsstructured-concurrency.md
withTaskGroupDynamic number of parallel operationsstructured-concurrency.md
withDiscardingTaskGroupFire-and-forget parallel operationsstructured-concurrency.md
.task { } modifierLoad data when view appearsstructured-concurrency.md
.task(id:) modifierRe-load when a value changesstructured-concurrency.md
actorShared mutable state protectionactors-and-isolation.md
@MainActorUI-bound state and updatesactors-and-isolation.md
@concurrentExplicitly offload to background (6.2)swift62-concurrency.md
Isolated conformances@MainActor type conforming to protocol (6.2)swift62-concurrency.md
withCheckedContinuationBridge callback API to asynccontinuations-bridging.md
AsyncStreamBridge delegate/notification API to async sequencecontinuations-bridging.md
@TaskLocalContext (IDs, tracing) down the task treestructured-concurrency.md
Atomic / MutexSendable wrappers for synchronous hot paths (Swift 6)actors-and-isolation.md
Custom actor executorsBridge existing DispatchSerialQueue synchronizationconcurrency-internals.md
Swift Concurrency InstrumentDiagnose hangs, actor contention, continuation leaksconcurrency-internals.md
Strict concurrency migrationIncremental Swift 6 adoptionmigration-guide.md

Process

1. Identify the Problem

Read the user's code or error messages to determine:

  • Is this a compiler error (strict concurrency) or a runtime issue (data race, crash)?
  • What Swift version and concurrency checking level are they using?
  • Are they migrating existing code or writing new code?

2. Load Relevant Reference Files

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 additions
  • structured-concurrency.md — async let, TaskGroup, .task modifier lifecycle, task-locals, cancellation semantics
  • actors-and-isolation.md — Actor patterns, reentrancy, @MainActor, Sendable, Atomic/Mutex
  • concurrency-internals.md — cooperative pool, unsafe primitives, actor scheduling, Swift Concurrency Instrument
  • continuations-bridging.md — withCheckedContinuation, AsyncStream, built-in async sequences, legacy bridging
  • migration-guide.md — Incremental Swift 6 strict concurrency adoption (WWDC24 doctrine)

3. Review Checklist

  • No blocking calls on @MainActor (use await for long operations)
  • Shared mutable state protected by an actor (not locks or DispatchQueue)
  • Sendable conformance correct for types crossing isolation boundaries
  • Task cancellation handled (check Task.isCancelled or Task.checkCancellation())
  • No unstructured Task {} where structured concurrency (.task, TaskGroup) would work
  • Actor reentrancy considered at suspension points
  • withCheckedContinuation called exactly once (not zero, not twice)
  • .task(id:) used instead of manual onChange + cancel patterns

4. Cross-Reference

  • For async/await basics and actor fundamentals, see macos/coding-best-practices/modern-concurrency.md
  • For networking concurrency patterns, see generators/networking-layer/networking-patterns.md
  • For SwiftData concurrency (@ModelActor), see macos/swiftdata-architecture/repository-pattern.md
  • For auth token refresh with actors, see generators/auth-flow/auth-patterns.md

References

concurrency-patterns by rshankras · The Skill Leaderboard