Skip to content
Back to skills

Swift Concurrency 6 2

ASecurity

Use when adopting Swift 6.2 Approachable Concurrency, MainActor isolation, or @concurrent offloading. Triggers on \"swift-concurrency-6-2\", \"swift concurrency 6 2\".

  • 2 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 19, 2026
ai-agentsswiftperformance

Security analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned September 19, 2026

npx -y skills add majinmagros/magros.ai-skills --skill swift-concurrency-6-2 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Swift Concurrency 6 2?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Swift Concurrency 6 2
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majinmagros-swift-concurrency-6-2/badge)](https://www.skillsdirectory.com/skills/majinmagros-swift-concurrency-6-2)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: swift-concurrency-6-2
description: "Use when adopting Swift 6.2 Approachable Concurrency, MainActor isolation, or @concurrent offloading. Triggers on \"swift-concurrency-6-2\", \"swift concurrency 6 2\"."
metadata:
  origin: ECC
---

# Swift 6.2 Approachable Concurrency

Single-threaded by default; async stays on the caller, `@concurrent` opts into background. Detalhes em `references/`.

## When to Activate

- Migrating Swift 5.x or 6.0/6.1 projects to Swift 6.2
- Resolving data-race safety compiler errors
- Designing MainActor-based app architecture
- Offloading CPU-intensive work to background threads
- Implementing protocol conformances on MainActor-isolated types
- Enabling Approachable Concurrency build settings in Xcode 26

## Core Principles

1. **Single-threaded default** — async stays on calling actor, no implicit offload
2. **Isolated conformances** — `@MainActor` types conform without workarounds
3. **`@concurrent` is opt-in** — background only as deliberate performance choice
4. **Inference mode** — MainActor by default for app targets, less boilerplate
5. **Migrate incrementally** — one build setting at a time, profile before offload

## Example

```swift
@MainActor
final class StickerModel {
    let photoProcessor = PhotoProcessor()
    func extractSticker(_ item: PhotosPickerItem) async throws -> Sticker? {
        guard let data = try await item.loadTransferable(type: Data.self) else { return nil }
        return await photoProcessor.extractSticker(data: data, with: item.itemIdentifier)
    }
}
```

## References

- `references/problem-migration.md` — implicit-offload problem, design decisions, migration steps
- `references/isolated-conformances.md` — isolated conformances, globals/statics, inference mode
- `references/concurrent-background.md` — `@concurrent` pattern with SE-0466/SE-0461 warning
- `references/practices-antipatterns.md` — best practices, anti-patterns, when to use

## Checklist

- [ ] Approachable Concurrency settings enabled (SE-0466, SE-0461) where needed
- [ ] Globals/statics protected by MainActor or inference mode
- [ ] `@concurrent` only on profiled CPU-intensive paths with await call sites
- [ ] No `nonisolated` suppression or legacy DispatchQueue without reason

Files in this skill

  • SKILL.md2.2 KB
  • references/concurrent-background.md1.3 KB
  • references/isolated-conformances.md2 KB
  • references/practices-antipatterns.md1.6 KB
  • references/problem-migration.md2.2 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…