Swift 6.2 finally fixes the implicit background offloading problem that caused data races in earlier versions. Now async functions stay on the calling actor by default, so your MainActor code actually stays on the main thread unless you explicitly mark something @concurrent. The isolated conformance feature is the real unlock here: MainActor types can conform to protocols without compiler errors or unsafe workarounds. If you're migrating from 5.x or dealing with Sendable errors in 6.0/6.1, this is the new mental model. Enable MainActor default inference for app targets and only reach for @concurrent when profiling shows you actually need background execution.
npx -y skills add affaan-m/everything-claude-code --skill swift-concurrency-6-2 --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
sickn33/antigravity-awesome-skills
wshobson/agents
kotlin/kotlin-agent-skills