swift-concurrency

Resolve Swift concurrency compiler errors with Swift 6.2 approachable concurrency features.

3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/andrew-d/claude-skills --skill swift-concurrency-andrew-d
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: swift-concurrency
Source: https://github.com/andrew-d/claude-skills/tree/main/plugins/swift-ios-skills--swift-core-skills/skills/swift-concurrency
Command: npx skills add https://github.com/andrew-d/claude-skills --skill swift-concurrency-andrew-d

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you resolve Swift concurrency compiler errors, adopt modern concurrency features like Swift 6.2's approachable concurrency, and write robust, data-race-safe asynchronous code.

Core Features & Use Cases

  • Error Resolution: Fix Sendable conformance errors, actor isolation warnings, and strict concurrency diagnostics.
  • Modern Adoption: Implement default MainActor isolation, @concurrent, nonisolated(nonsending), and Task.immediate.
  • Architecture Design: Build actor-based systems, leverage structured concurrency with TaskGroup, and manage background tasks effectively.
  • Use Case: You're encountering "Sending 'self.someObject' risks causing data races" errors in your Swift code. This Skill guides you through applying the correct actor isolation or Sendable conformance to resolve these issues and ensure thread safety.

Quick Start

Use the swift-concurrency skill to resolve Sendable conformance errors in the provided code snippet.

Frequently Asked Questions about swift-concurrency

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix "Sending risks causing data races" errors in Swift?

Resolve Swift concurrency compiler errors by applying Swift 6.2 approachable concurrency features like default MainActor isolation, @concurrent, and nonisolated(nonsending) to ensure data-race-safe code.

How do I adopt Swift 6.2 default MainActor isolation and nonisolated(nonsending)?

Adopt Swift 6.2 approachable concurrency by applying default MainActor isolation to infer execution contexts, using @concurrent for background work, and nonisolated(nonsending) to prevent unwanted task emissions.

What is the best way to implement structured concurrency with TaskGroup in Swift?

The best way to implement structured concurrency in Swift is by using TaskGroup to manage concurrent operations hierarchically, ensuring cancellation propagation and error handling for robust asynchronous code.

When do I need to add Sendable conformance to Swift types?

You need to add Sendable conformance to Swift types when passing instances across actor boundaries or concurrent tasks to satisfy strict concurrency diagnostics and guarantee thread-safe data access.

Does Swift 6.2 approachable concurrency help resolve strict concurrency warnings?

Yes, Swift 6.2 approachable concurrency resolves strict concurrency warnings by applying default MainActor isolation and nonisolated(nonsending) annotations to simplify actor isolation diagnostics.