Swift6 concurrency
Skill wei18/apple-dev-skills/apple-dev-skills/skills/swift6-concurrency
Default to Swift 6 language mode with complete concurrency checking from the first line of code; treat all in-house types as needing Sendable; isolate third-party deps that lag with @preconcurrency. Invoke when starting a new Swift Apple-platform project, writing Package.swift, picking the Swift language mode in Xcode build settings, or when asked "should I turn on strict concurrency?".From its SKILL.md
npx -y skills add wei18/apple-dev-skills --skill swift6-concurrencyAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 18 stars18 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.0 KB, 582 tokens by cl100k_base, as published. Nobody here has run it
Swift 6 / Strict Concurrency
When to invoke
- Starting a new Swift iOS / macOS App project and deciding the language mode.
- Writing
Package.swiftand settingswiftLanguageModes/SWIFT_STRICT_CONCURRENCY. - Adding a new third-party dependency and hitting concurrency warnings / errors.
- User asks "how do I configure Swift 6 / complete concurrency / Sendable / actor /
@preconcurrency".
Default decisions
- Swift 6 language mode + complete concurrency checking, applied from the first line of code.
- All in-house types are treated as needing
Sendableby default; any type shared across actors must declare it explicitly (struct Foo: Sendableorfinal class Foo: Sendable— the latter only valid when all stored properties are Sendable and the class is non-inheritable; for classes with mutable state, preferactor Fooor@unchecked Sendablewith manual synchronisation). - Protocols that cross actor boundaries (DI injection points) are always declared
Sendable, with methodsasync throws. - For third-party deps that don't support Swift 6 complete checking, in order of preference:
@preconcurrency import Xto isolate the import- Switch packages
- Defer adoption
Rationale
- A greenfield project has no legacy code to migrate, so the pain of complete checking gets amortised — solved once per actor / Sendable as you write — rather than as a one-shot big-bang migration later.
- Swift 6 is the long-term direction of the language; early adoption avoids technical debt.
- Complete checking catches data races at compile time, more than minimal / targeted can.
Deviation considerations
- Migrating existing Swift 5 code: switch to minimal or targeted concurrency checking and upgrade in stages; ramp up one file / module at a time, allowing
@preconcurrencyduring transition. - Significant third-party lag: if a critical dep doesn't support it, drop the whole project to targeted and patch module by module.
- Teaching / demo projects: if the goal is to demonstrate older API behaviour, keeping Swift 5 mode is fine.
Related skills
apple-platform-targets: Xcode 16+ is the first toolchain that formally supports Swift 6 language mode; consider this alongside deployment target decisions.swiftpm-modularization:swiftLanguageModes: [.v6]sets the default for the whole package; individual targets can opt down withswiftSettings: [.swiftLanguageMode(.v5)](available since swift-tools-version 6.0) — useful when migrating a legacy dependency without blocking the rest of the package.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.