skillfed

axiom-concurrency

axiom-concurrency equips AI coding assistants with expert-level Swift 6 concurrency knowledge to eliminate data races and isolation violations. This skill covers modern async/await patterns, actor isolation, and sendability constraints—essential for building robust Apple OS applications. Prevent crashes and memory issues before they reach users.

axiom-concurrency provides expert-level guidance for eliminating Swift 6 data race errors and isolation violations. The skill teaches you how to identify where concurrent code accesses shared state unsafely, apply actor isolation to protect mutable state, and use Sendable constraints to enforce compile-time safety. By resolving these errors early, you prevent runtime crashes and memory corruption in production Apple OS applications.

AI-generated summary based on this skill's SKILL.md

1,095 81 MIT updated by CharlesWiltgen

Install

CharlesWiltgen/Axiom/axiom-concurrency · repository language: Go

CLI (skillfed)coming soon
git clone https://github.com/CharlesWiltgen/Axiom
cp -r Axiom/axiom-codex/skills/axiom-concurrency ~/.claude/skills/axiom-concurrency

Frequently asked questions

AI-generated answers based on this skill's SKILL.md and metadata

What does axiom-concurrency help resolve with Swift 6 data race errors?

axiom-concurrency provides expert-level guidance for eliminating Swift 6 data race errors and isolation violations. The skill teaches you how to identify where concurrent code accesses shared state unsafely, apply actor isolation to protect mutable state, and use Sendable constraints to enforce compile-time safety. By resolving these errors early, you prevent runtime crashes and memory corruption in production Apple OS applications.

How do I use async await in Swift with axiom-concurrency?

axiom-concurrency covers modern async/await patterns for writing concurrent code in Swift. The skill explains how to structure asynchronous functions, chain async operations without callbacks, and use TaskGroup and withDiscardingTaskGroup for parallel work. You'll learn when to apply MainActor for UI updates, how to handle cancellation, and best practices for avoiding main-thread blocking that degrades app responsiveness.

What is MainActor Sendable in Swift 6 and how does axiom-concurrency address it?

axiom-concurrency explains MainActor and Sendable constraints—critical for Swift 6 isolation safety. MainActor ensures code runs on the main thread for UI operations; Sendable marks types safe to pass between isolation domains. The skill teaches you to apply these annotations correctly, diagnose isolation inheritance mismatches that cause runtime crashes, and migrate legacy code that uses DispatchQueue callbacks to modern actor patterns.

How can I migrate from DispatchQueue and callbacks to Swift Concurrency?

axiom-concurrency guides you through replacing DispatchQueue-based code with Swift Concurrency actors and async/await. The skill covers converting callback-based APIs to async functions, wrapping legacy dispatch patterns in actors to maintain isolation safety, and debugging crashes from isolation mismatches during migration. You'll learn strategies for incremental adoption so existing code and new concurrent code coexist safely.

Does axiom-concurrency help debug Swift concurrency crashes and performance?

Yes. axiom-concurrency covers debugging runtime crashes from isolation violations, actor reentrancy issues, and AsyncStream continuation problems. The skill also addresses performance diagnosis—profiling actor contention, detecting thread pool exhaustion, and using Instruments to measure async overhead. You'll learn to diagnose issues like CLLocationManager delegate isolation crashes and CoreData MainActor blocking.

What patterns does axiom-concurrency teach for actor reentrancy and isolation?

axiom-concurrency explains actor reentrancy—when async code suspends and allows other tasks to interleave—and how to design actors that handle this safely. The skill covers nonisolated unsafe patterns for performance-critical code, mutex vs. actor trade-offs on iOS 18, and best practices for structuring actor methods to avoid deadlocks and contention. You'll understand when isolation is necessary and when it can be relaxed safely.

SKILL.md

rendered from the published skill — quoted content, verbatim

Concurrency

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

<!-- AXIOM_AUDITOR_INLINE_BEGIN — auto-maintained by scripts/build-inlined-auditors.ts; do not hand-edit --> > Not on Claude Code? Where this router says "Launch some-auditor agent", read that auditor's file in this suite and follow it inline — the same procedure, needing only file search and read. > > Available here: skills/concurrency-auditor.md. > > Agents that need Bash — builds, tests, simulators, crash symbolication — stay Claude Code-only; there is no inline equivalent for those. <!-- AXIOM_AUDITOR_INLINE_END -->

Quick Reference

Symptom / Task Reference
async/await patterns, @MainActor, actors See skills/swift-concurrency.md
Data race errors, Sendable conformance See skills/swift-concurrency.md
Swift 6 migration, @concurrent attribute See skills/swift-concurrency.md

(truncated - see the full file via the links below)

Read as markdown · JSON record · Browse the source repository

File tree — 8 files
axiom-codex/skills/axiom-concurrency/SKILL.md
axiom-codex/skills/axiom-concurrency/agents/openai.yaml
axiom-codex/skills/axiom-concurrency/skills/assume-isolated.md
axiom-codex/skills/axiom-concurrency/skills/concurrency-profiling.md
axiom-codex/skills/axiom-concurrency/skills/isolation-inheritance-diag.md
axiom-codex/skills/axiom-concurrency/skills/swift-concurrency-ref.md
axiom-codex/skills/axiom-concurrency/skills/swift-concurrency.md
axiom-codex/skills/axiom-concurrency/skills/synchronization.md

Related skills

Tags

thread-safety isolation-architecture async-patterns runtime-crashes performance-profiling sdk-callbacks data-race-detection migration-guide cooperative-threading