concurrency▌

You MUST use this skill for ANY concurrency, async/await, threading, or Swift 6 concurrency work.

Persona: You are a Go concurrency engineer. You assume every goroutine is a liability until proven necessary — correctness and leak-freedom come before performance.

Normative: When you spawn goroutines, make it clear when or whether they exit.

Navigate .NET concurrency from async/await through Channels to Akka.NET based on your specific problem. \n \n Start with async/await for I/O-bound work; escalate only when you hit a concrete limitation that simpler tools can't address cleanly \n Use Parallel.ForEachAsync for CPU-bound parallelism, Channel<T> for producer/consumer decoupling with backpressure, and Reactive Extensions for UI event composition \n Akka.NET Actors handle stateful entity management, state machines with Become() ,

Resolve Swift 6.2 concurrency errors and adopt data-race-safe async patterns. \n \n Diagnose and fix actor isolation, Sendable conformance, and strict concurrency compiler diagnostics with a structured triage workflow \n Apply SE-0466 default MainActor isolation, SE-0461 nonisolated(nonsending), @concurrent functions, and Task.immediate for minimal behavior changes \n Design actor-based architectures, structured concurrency with TaskGroup and async let, and proper task cancellation patterns \n M

Background JSON parsing and state management for jank-free Flutter UI rendering. \n \n Provides decision tree for choosing between manual serialization ( dart:convert ) and code generation ( json_serializable ) based on model complexity \n Supports three concurrency strategies: main-thread async/await for small payloads, short-lived Isolate.run() for heavy one-off computations, and long-lived isolates with ReceivePort / SendPort for continuous two-way communication \n Includes platform-aware fal

Single-threaded by default with explicit background offloading via @concurrent and isolated protocol conformances. \n \n Async functions stay on the calling actor by default, eliminating implicit background offloading that caused data-race errors in Swift 6.1 and earlier \n Isolated conformances allow MainActor types to safely conform to non-isolated protocols without unsafe workarounds \n @concurrent attribute explicitly offloads CPU-intensive work to background threads; requires nonisolated ty

Diagnose data races, migrate to async/await, and resolve Swift 6 concurrency issues with structured guidance. \n \n Analyzes project settings (language mode, strict concurrency level, default isolation) before proposing fixes to ensure recommendations match your build configuration \n Covers all major concurrency diagnostics: main actor isolation, actor conformance, Sendable violations, and SwiftLint warnings with smallest-safe-fix strategies \n Provides Quick Fix Mode for localized, single-file

ln-628-concurrency-auditor

Layer 1: Language Mechanics