Axiom Concurrency logo

Axiom Concurrency

CommunityPopular
CharlesWiltgen
axiom-concurrency

Use when writing ANY async code, actors, or threads in an Apple-platform app, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.

Overview

PublisherCharlesWiltgen
RepositoryAxiom
Skill nameaxiom-concurrency
Stars
1.2K
Forks
86
Bundled files
7
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 7 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by CharlesWiltgen on GitHub. Read the source before you install it.

Installation

Install the Axiom Concurrency AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/CharlesWiltgen/Axiom/tree/main/axiom-codex/skills/axiom-concurrency
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/CharlesWiltgen/Axiom.git /tmp/Axiom
mkdir -p .claude/skills
cp -r /tmp/Axiom/axiom-codex/skills/axiom-concurrency .claude/skills/axiom-concurrency
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Axiom Concurrency in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Axiom Concurrency on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Axiom Concurrency is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Concurrency

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

Auditors are skills here. Where this router says "Launch some-auditor agent", invoke the matching Codex skill instead — same procedure, no Claude Code agent required.

Available: axiom-audit-concurrency.

The ones that shell out — builds, tests, simulators, crash symbolication — need shell access to run.

Quick Reference

Symptom / TaskReference
async/await patterns, @MainActor, actorsSee skills/swift-concurrency.md
Data race errors, Sendable conformanceSee skills/swift-concurrency.md
Swift 6 migration, @concurrent attributeSee skills/swift-concurrency.md
Actor definition, reentrancy, global actorsSee skills/swift-concurrency-ref.md
Task/TaskGroup/cancellation APISee skills/swift-concurrency-ref.md
AsyncStream, continuationsSee skills/swift-concurrency-ref.md
DispatchQueue → actor migrationSee skills/swift-concurrency-ref.md
Mutex (iOS 18+), OSAllocatedUnfairLockSee skills/synchronization.md
Atomic types, lock vs actor decisionSee skills/synchronization.md
MainActor.assumeIsolatedSee skills/assume-isolated.md
@preconcurrency protocol conformancesSee skills/assume-isolated.md
Legacy delegate callbacksSee skills/assume-isolated.md
Warning-free build crashes with _dispatch_assert_queue_failSee skills/isolation-inheritance-diag.md
Crash signature _swift_task_checkIsolatedSwiftSee skills/isolation-inheritance-diag.md
Core Data context.perform runtime crash inside @MainActor classSee skills/isolation-inheritance-diag.md
Combine .map/.sink crash from receive(on:) placementSee skills/isolation-inheritance-diag.md
Delegate method crash from isolation inheritance (CLLocationManager, NSDocument, AVAudioPlayerDelegate, WKNavigationDelegate, PHPhotoLibraryChangeObserver)See skills/isolation-inheritance-diag.md
PhotoKit performChanges block traps on PhotoKit's queueSee skills/isolation-inheritance-diag.md
Actor reentrancy / stale state across awaitSee skills/isolation-inheritance-diag.md
Swift Concurrency Instruments templateSee skills/concurrency-profiling.md
Actor contention diagnosisSee skills/concurrency-profiling.md
Thread pool exhaustionSee skills/concurrency-profiling.md

Decision Tree

dot
digraph concurrency {
    start [label="Concurrency task" shape=ellipse];
    what [label="What do you need?" shape=diamond];

    start -> what;
    what -> "skills/swift-concurrency.md" [label="async/await, actors,\nSendable, data races,\nSwift 6 migration"];
    what -> "skills/swift-concurrency-ref.md" [label="API syntax lookup\n(TaskGroup, AsyncStream,\ncontinuations, migration)"];
    what -> "skills/synchronization.md" [label="Mutex, locks,\natomic types"];
    what -> "skills/assume-isolated.md" [label="assumeIsolated,\n@preconcurrency"];
    what -> "skills/isolation-inheritance-diag.md" [label="warning-free build crashes\n_dispatch_assert_queue_fail\n_swift_task_checkIsolatedSwift"];
    what -> "skills/concurrency-profiling.md" [label="profile async perf,\nactor contention"];
}
  1. Data races / actor isolation / @MainActor / Sendable / Swift 6 migration? → skills/swift-concurrency.md 1a. Need specific API syntax (actor definition, TaskGroup, AsyncStream, continuations)? → skills/swift-concurrency-ref.md 1b. NotificationCenter observer, userInfo casting, or Sendable errors unpacking a notification? → skills/swift-concurrency-ref.md (Typed Notifications — MainActorMessage/AsyncMessage, iOS 26+)
  2. Writing async/await code? → skills/swift-concurrency.md
  3. assumeIsolated / @preconcurrency? → skills/assume-isolated.md 3a. Warning-free Swift 6 build that crashes in production with _dispatch_assert_queue_fail or _swift_task_checkIsolatedSwift? → skills/isolation-inheritance-diag.md
  4. Mutex / lock / synchronization? → skills/synchronization.md
  5. Profile async performance / actor contention? → skills/concurrency-profiling.md
  6. Value type / ARC / generic optimization? → See axiom-performance (skills/swift-performance.md)
  7. borrowing / consuming / ~Copyable? → See axiom-swift (skills/ownership-conventions.md)
  8. Combine / @Published / AnyCancellable / reactive streams? → See axiom-uikit (skills/combine-patterns.md)
  9. Want automated concurrency scan? → concurrency-auditor (Agent)
Concurrency in practice
  • HealthKit queries with Swift Concurrency (canonical bridging example) → See axiom-health (skills/queries.md)

Conflict Resolution

concurrency vs axiom-performance: When app freezes or feels slow:

  1. Try concurrency FIRST — Main thread blocking is the #1 cause of UI freezes. Check for synchronous work on @MainActor before profiling.
  2. Only use axiom-performance if concurrency fixes don't help — Profile after ruling out obvious blocking.
  3. To pin a specific freeze to app code, see the Hang Window Workflow in axiom-performance (skills/hang-diagnostics.md) — re-scope xcprof analyze to the hang window with --start-ms/--end-ms --user-binary to surface the app-owned frame on the main thread.

concurrency vs axiom-build: When seeing Swift 6 concurrency errors:

  • Use concurrency, NOT axiom-build — Concurrency errors are CODE issues, not environment issues.

concurrency vs axiom-data: When concurrency errors involve Core Data or SwiftData:

  • Core Data threading (NSManagedObjectContext thread confinement) → use axiom-data first
  • SwiftData + @MainActor ModelContext → use concurrency
  • General "background saves losing data" → use axiom-data first
  • GRDB Sendable patterns (struct records, databaseSelection as computed property, Swift 6 conformance) → See axiom-data (skills/grdb-performance.md) §8

Critical Patterns

Swift Concurrency (skills/swift-concurrency.md):

  • Progressive journey: single-threaded → async → concurrent → actors
  • @concurrent attribute for forced background execution
  • Isolated conformances, main actor mode
  • 12 copy-paste patterns including delegate value capture, weak self in Tasks
  • Comprehensive decision tree for 7 common error messages

API Reference (skills/swift-concurrency-ref.md):

  • Actor definition, reentrancy, global actors, nonisolated
  • Sendable patterns, @unchecked Sendable, sending parameter
  • Task/TaskGroup/cancellation, async let, withDiscardingTaskGroup
  • AsyncStream, continuations, buffering policies
  • Isolation patterns (#isolation, @preconcurrency, nonisolated(unsafe))
  • DispatchQueue/DispatchGroup/completion handler migration

Synchronization (skills/synchronization.md):

  • Mutex (iOS 18+), OSAllocatedUnfairLock (iOS 16+), Atomic types
  • Lock vs actor decision tree
  • Danger patterns: locks across await, semaphores in async context

Profiling (skills/concurrency-profiling.md):

  • Swift Concurrency Instruments template
  • Diagnosing main thread blocking, actor contention, thread pool exhaustion
  • Safe vs unsafe primitives for cooperative pool

Runtime Isolation Crashes (skills/isolation-inheritance-diag.md):

  • _dispatch_assert_queue_fail and _swift_task_checkIsolatedSwift signatures
  • Closure isolation inheritance (Core Data perform, Combine .map, NotificationCenter .sink)
  • Delegate method isolation inheritance (CLLocationManager, NSDocument, AVAudioPlayerDelegate, WKNavigationDelegate)
  • MainActor.assumeIsolated misuse
  • Actor reentrancy state staleness

Automated Scanning

Concurrency audit → axiom-audit-concurrency (5-phase semantic audit: maps isolation architecture, detects 8 anti-patterns, reasons about missing concurrency patterns, correlates compound risks, scores Swift 6.4 readiness)

Anti-Rationalization

ThoughtReality
"Just add @MainActor and it'll work"@MainActor has isolation inheritance rules. skills/swift-concurrency.md covers all patterns.
"I'll use nonisolated(unsafe) to silence the warning"Silencing warnings hides data races. skills/swift-concurrency.md shows the safe pattern.
"It's just one async call"Even single async calls have cancellation and isolation implications.
"I know how actors work"Actor reentrancy and isolation rules changed in Swift 6.2.
"I'll fix the Sendable warnings later"Sendable violations cause runtime crashes. Fix them now.
"My Swift 6 build has zero warnings, so isolation is correct"Static checking can't see SDK callbacks. Runtime checks crash anyway. skills/isolation-inheritance-diag.md.
"I'll wrap the crash in MainActor.assumeIsolated"assumeIsolated is a runtime trap, not a silencer. Wrong assumption = crash.
"Combine is dead, just use async/await"Combine has no deprecation notice. Rewriting working pipelines wastes time. See See axiom-uikit (skills/combine-patterns.md).
"I'll use @unchecked Sendable to silence this"You're hiding a data race from the compiler. It will crash in production.
"This async function runs on a background thread"Check its isolation, don't assume. A @MainActor async function runs entirely on the main actor, and nonisolated async runs on the caller's actor under NonisolatedNonsendingByDefault (Swift 6.2+; new Xcode projects set SWIFT_APPROACHABLE_CONCURRENCY = YES, the setting's own default is NO, and SwiftPM does not enable it) — those are the main-thread freezes. Without that setting nonisolated async hops to the global executor. @concurrent forces off-actor work either way.

Example Invocations

User: "I'm getting 'data race' errors in Swift 6" → Read: skills/swift-concurrency.md

User: "How do I use @MainActor correctly?" → Read: skills/swift-concurrency.md

User: "How do I create a TaskGroup?" → Read: skills/swift-concurrency-ref.md

User: "What's the AsyncStream API?" → Read: skills/swift-concurrency-ref.md

User: "How do I use assumeIsolated?" → Read: skills/assume-isolated.md

User: "Should I use Mutex or actor?" → Read: skills/synchronization.md

User: "My async code is slow, how do I profile it?" → Read: skills/concurrency-profiling.md

User: "My warning-free Swift 6 build crashes in production with _dispatch_assert_queue_fail" → Read: skills/isolation-inheritance-diag.md

User: "Core Data context.perform crashes inside an @MainActor view model" → Read: skills/isolation-inheritance-diag.md

User: "CLLocationManager delegate method is crashing with _swift_task_checkIsolatedSwift" → Read: skills/isolation-inheritance-diag.md

User: "My app is slow due to unnecessary copying" → See axiom-performance (skills/swift-performance.md)

User: "Check my code for Swift 6 concurrency issues" → Invoke: concurrency-auditor agent

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Axiom Concurrency AI skill do?

Use when writing ANY async code, actors, or threads in an Apple-platform app, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.

Why use Axiom Concurrency on TypingMind?

Because you install it once and use it with any model. Axiom Concurrency is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Axiom Concurrency in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/CharlesWiltgen/Axiom/tree/main/axiom-codex/skills/axiom-concurrency. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Axiom Concurrency?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Axiom Concurrency?

As many as you like. As long as a model supports skills, you can use Axiom Concurrency with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Axiom Concurrency AI skill free?

Yes. It is published on GitHub by CharlesWiltgen under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇