swift-concurrency-expert

Étoiles8

Forks2

Mis à jour5 février 2026 à 06:28

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Source

dimfeld

dimfeld/llmutils

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

3 fichiers

SKILL.md

readonly

name	swift-concurrency-expert
description	Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

Swift Concurrency Expert

Attribution: copied from @Dimillian’s Dimillian/Skills (2025-12-31).

Overview

Review and fix Swift Concurrency issues in Swift 6.2+ codebases by applying actor isolation, Sendable safety, and modern concurrency patterns with minimal behavior changes.

Workflow

1. Triage the issue

Capture the exact compiler diagnostics and the offending symbol(s).
Identify the current actor context (@MainActor, actor, nonisolated) and whether a default actor isolation mode is enabled.
Confirm whether the code is UI-bound or intended to run off the main actor.

2. Apply the smallest safe fix

Prefer edits that preserve existing behavior while satisfying data-race safety.

Common fixes:

UI-bound types: annotate the type or relevant members with @MainActor.
Protocol conformance on main actor types: make the conformance isolated (e.g., extension Foo: @MainActor SomeProtocol).
Global/static state: protect with @MainActor or move into an actor.
Background work: move expensive work into a @concurrent async function on a nonisolated type or use an actor to guard mutable state.
Sendable errors: prefer immutable/value types; add Sendable conformance only when correct; avoid @unchecked Sendable unless you can prove thread safety.

Reference material

See references/swift-6-2-concurrency.md for Swift 6.2 changes, patterns, and examples.
See references/swiftui-concurrency-tour-wwdc.md for SwiftUI-specific concurrency guidance.

Plus depuis ce dépôt

même dépôt

using-tim

dimfeld/llmutils

Manages project plans with tim. Use whenever the user mentions tim, asks to "generate plan 123" (or any number), "work on plan 123", or when you are working on a tim task.

2026-07-078

svelte-core-bestpractices

dimfeld/llmutils

Guidance on writing fast, robust, modern Svelte code. Load this skill whenever in a Svelte project and asked to write/edit or analyze a Svelte component or module. Covers reactivity, event handling, styling, integration with libraries and more.

2026-04-038

swiftui-liquid-glass

dimfeld/llmutils

Implement, review, or improve SwiftUI features using the iOS 26+ Liquid Glass API. Use when asked to adopt Liquid Glass in new SwiftUI UI, refactor an existing feature to Liquid Glass, or review Liquid Glass usage for correctness, performance, and design alignment.

2026-02-058

swiftui-performance-audit

dimfeld/llmutils

Audit and improve SwiftUI runtime performance from code review and architecture. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps, and to provide guidance for user-run Instruments profiling when code review alone is insufficient.

2026-02-058

swiftui-view-refactor

dimfeld/llmutils

Refactor and review SwiftUI view files for consistent structure, dependency injection, and Observation usage. Use when asked to clean up a SwiftUI view’s layout/ordering, handle view models safely (non-optional when possible), or standardize how dependencies and @Observable state are initialized and passed.

2026-02-058

name	swift-concurrency-expert
description	Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file.

Swift Concurrency Expert

Attribution: copied from @Dimillian’s Dimillian/Skills (2025-12-31).

Overview

Review and fix Swift Concurrency issues in Swift 6.2+ codebases by applying actor isolation, Sendable safety, and modern concurrency patterns with minimal behavior changes.

Workflow

1. Triage the issue

Capture the exact compiler diagnostics and the offending symbol(s).
Identify the current actor context (@MainActor, actor, nonisolated) and whether a default actor isolation mode is enabled.
Confirm whether the code is UI-bound or intended to run off the main actor.

2. Apply the smallest safe fix

Prefer edits that preserve existing behavior while satisfying data-race safety.

Common fixes:

UI-bound types: annotate the type or relevant members with @MainActor.
Protocol conformance on main actor types: make the conformance isolated (e.g., extension Foo: @MainActor SomeProtocol).
Global/static state: protect with @MainActor or move into an actor.
Background work: move expensive work into a @concurrent async function on a nonisolated type or use an actor to guard mutable state.
Sendable errors: prefer immutable/value types; add Sendable conformance only when correct; avoid @unchecked Sendable unless you can prove thread safety.

Reference material

See references/swift-6-2-concurrency.md for Swift 6.2 changes, patterns, and examples.
See references/swiftui-concurrency-tour-wwdc.md for SwiftUI-specific concurrency guidance.