swift-concurrency

Resolve Swift concurrency compiler errors and adopt Swift 6.2 approachable concurrency.

155|22|Updated Feb 24, 2026

Search Tags:#concurrency #swift 6 #swift #async/await #actors #sendable #structured concurrency

Ready to run

npx skills add https://github.com/omarshahine/HomeClaw --skill swift-concurrency-omarshahine

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swift-concurrency
Source: https://github.com/omarshahine/HomeClaw/tree/main/.agents/skills/swift-concurrency
Command: npx skills add https://github.com/omarshahine/HomeClaw --skill swift-concurrency-omarshahine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers write robust, data-race-free Swift code by leveraging modern concurrency features like actors, async/await, and structured concurrency, ensuring applications are performant and reliable.

Core Features & Use Cases

Resolve Concurrency Errors: Fixes Sendable conformance issues, actor isolation warnings, and strict concurrency diagnostics.
Adopt Swift 6 Concurrency: Guides users in implementing features like default MainActor isolation, @concurrent, and nonisolated(nonsending).
Design Actor Architectures: Assists in building safe, concurrent systems using actors, TaskGroup, and proper cancellation.
Use Case: A developer is struggling with compiler errors related to Sendable conformance in a complex data processing pipeline. This Skill provides targeted guidance and code examples to resolve these issues and ensure thread safety.

Quick Start

Use the swift-concurrency skill to resolve Sendable conformance errors in your project.

Frequently Asked Questions about swift-concurrency

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

FAQPage Schema

How do I fix Sendable conformance errors in Swift?▼

To fix Sendable conformance errors in Swift, ensure your custom types are safe to pass across concurrent boundaries by adopting Swift 6 strict concurrency diagnostics, utilizing actors for state isolation, or properly migrating using @preconcurrency.

What is default MainActor isolation in Swift 6.2?▼

Default MainActor isolation in Swift 6.2 is an approachable concurrency feature (SE-0466) that automatically isolates code to the MainActor, reducing data races while simplifying migration to strict concurrency by minimizing explicit annotations.

How do I design actor-based architectures for async code?▼

To design actor-based architectures for async code, use actors to safely encapsulate mutable state, leverage structured concurrency with TaskGroup for hierarchical operations, and implement proper cancellation to offload background work safely.

When should I use @concurrent or nonisolated(nonsending) in Swift?▼

Use @concurrent or nonisolated(nonsending) in Swift when adopting Swift 6.2 approachable concurrency to explicitly define functions that run outside actor isolation without triggering strict concurrency diagnostics or data race warnings.

How do I migrate from @preconcurrency to full Swift 6 strict concurrency?▼

Migrate from @preconcurrency to full Swift 6 strict concurrency by progressively resolving strict concurrency diagnostics, adopting default MainActor isolation, ensuring Sendable conformance, and replacing legacy async patterns with structured concurrency.