You MUST use this skill for ANY concurrency, async/await, threading, or Swift 6 concurrency work.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionaxiom-ios-concurrencyExecute the skills CLI command in your project's root directory to begin installation:
Fetches axiom-ios-concurrency from charleswiltgen/axiom and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate axiom-ios-concurrency. Access via /axiom-ios-concurrency in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
767
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
767
stars
You MUST use this skill for ANY concurrency, async/await, threading, or Swift 6 concurrency work.
Use this router when:
ios-concurrency vs ios-performance: When app freezes or feels slow:
ios-concurrency vs ios-build: When seeing Swift 6 concurrency errors:
ios-concurrency vs ios-data: When concurrency errors involve Core Data or SwiftData:
Rationale: A 2-second freeze during data loading is almost always await on main thread or missing background dispatch. Domain knowledge solves this faster than Time Profiler. Core Data threading violations need Core Data-specific fixes, not generic concurrency patterns.
Swift 6 concurrency patterns → /skill axiom-swift-concurrency
Swift concurrency API reference → /skill axiom-swift-concurrency-ref
Swift performance → /skill axiom-swift-performance
Synchronous actor access → /skill axiom-assume-isolated
Thread-safe primitives → /skill axiom-synchronization
Parameter ownership → /skill axiom-ownership-conventions
Concurrency profiling → /skill axiom-concurrency-profiling
Combine reactive patterns → /skill axiom-combine-patterns
Concurrency audit → Launch concurrency-auditor agent or /axiom:audit concurrency (Swift 6 strict concurrency violations, unsafe Task captures, missing @MainActor, Sendable violations, actor isolation problems)
| Thought | Reality |
|---|---|
| "Just add @MainActor and it'll work" | @MainActor has isolation inheritance rules. swift-concurrency covers all patterns. |
| "I'll use nonisolated(unsafe) to silence the warning" | Silencing warnings hides data races. swift-concurrency shows the safe pattern. |
| "It's just one async call" | Even single async calls have cancellation and isolation implications. swift-concurrency covers them. |
| "I know how actors work" | Actor reentrancy and isolation rules changed in Swift 6.2. swift-concurrency is current. |
| "I'll fix the Sendable warnings later" | Sendable violations cause runtime crashes. swift-concurrency fixes them correctly now. |
| "Combine is dead, just use async/await" | Combine has no deprecation notice. Rewriting working pipelines wastes time and introduces bugs. combine-patterns covers incremental migration. |
Swift 6 Concurrency (swift-concurrency):
Swift Performance (swift-performance):
User: "I'm getting 'data race' errors in Swift 6"
→ Invoke: /skill axiom-swift-concurrency
User: "How do I use @MainActor correctly?"
→ Invoke: /skill axiom-swift-concurrency
User: "My app is slow due to unnecessary copying"
→ Invoke: /skill axiom-swift-performance
User: "Should I use async/await for this network call?"
→ Invoke: /skill axiom-swift-concurrency
User: "How do I use assumeIsolated?"
→ Invoke: /skill axiom-assume-isolated
User: "My delegate callback runs on main thread, how do I access MainActor state?"
→ Invoke: /skill axiom-assume-isolated
User: "Should I use Mutex or actor?"
→ Invoke: /skill axiom-synchronization
User: "What's the difference between os_unfair_lock and OSAllocatedUnfairLock?"
→ Invoke: /skill axiom-synchronization
User: "What does borrowing do in Swift?"
→ Invoke: /skill axiom-ownership-conventions
User: "How do I use ~Copyable types?"
→ Invoke: /skill axiom-ownership-conventions
User: "My async code is slow, how do I profile it?"
→ Invoke: /skill axiom-concurrency-profiling
User: "I think I have actor contention, how do I diagnose it?"
→ Invoke: /skill axiom-concurrency-profiling
User: "My Core Data saves lose data from background tasks"
→ Route to: ios-data router (Core Data threading is framework-specific)
User: "How do I create a TaskGroup?"
→ Invoke: /skill axiom-swift-concurrency-ref
User: "What's the AsyncStream API?"
→ Invoke: /skill axiom-swift-concurrency-ref
User: "How do I create a custom global actor?"
→ Invoke: /skill axiom-swift-concurrency-ref
User: "How do I convert a completion handler to async?"
→ Invoke: /skill axiom-swift-concurrency-ref
User: "What are the actor reentrancy rules?"
→ Invoke: /skill axiom-swift-concurrency-ref
User: "My Combine pipeline silently stopped producing values"
→ Invoke: /skill axiom-combine-patterns
User: "Should I use Combine or async/await for this data flow?"
→ Invoke: /skill axiom-combine-patterns
User: "How do I bridge a Combine publisher into async/await code?"
→ Invoke: /skill axiom-combine-patterns
User: "AnyCancellable is leaking memory"
→ Invoke: /skill axiom-combine-patterns
User: "Check my code for Swift 6 concurrency issues"
→ Invoke: concurrency-auditor agent
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
axiom-ios-concurrency reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in axiom-ios-concurrency — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for axiom-ios-concurrency matched our evaluation — installs cleanly and behaves as described in the markdown.
axiom-ios-concurrency has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: axiom-ios-concurrency is focused, and the summary matches what you get after install.
We added axiom-ios-concurrency from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend axiom-ios-concurrency for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for axiom-ios-concurrency matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in axiom-ios-concurrency — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend axiom-ios-concurrency for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 30