guide-swift-concurrency
Swift concurrency patterns — actors, structured concurrency, cancellation, async streams, GCD migration, strict-concurrency diagnostics, common bug patterns. Use when writing, reviewing, or debugging concurrent Swift code.
- License 许可
- MIT
- 最近更新
- 2026-06-15
- Stars
- ★ 2
- Forks
- 1
01 前言 Front Matter
- name
- guide-swift-concurrency
- type
- guide
- origin
- https://github.com/twostraws/Swift-Concurrency-Agent-Skill
- license
- MIT
- description
- Swift concurrency patterns — actors, structured concurrency, cancellation, async streams, GCD migration, strict-concurrency diagnostics, common bug patterns. Use when writing, reviewing, or debugging concurrent Swift code.
02 资源文件 12
- 参考文档references/actors.md5.3 KB
- 参考文档references/async-streams.md2.1 KB
- 参考文档references/bridging.md2.9 KB
- 参考文档references/bug-patterns.md4.1 KB
- 参考文档references/cancellation.md3.6 KB
- 参考文档references/diagnostics.md4.4 KB
- 参考文档references/hotspots.md2.3 KB
- 参考文档references/interop.md3.6 KB
- 参考文档references/new-features.md7.7 KB
- 参考文档references/structured.md3.0 KB
- 参考文档references/testing.md8.1 KB
- 参考文档references/unstructured.md2.4 KB
03 SKILL.md 正文
Guide Skill — This is an expert workflow/pattern guide, not API reference documentation. Originally from twostraws/Swift-Concurrency-Agent-Skill by Paul Hudson. MIT License.
Swift Concurrency Patterns
Review and write Swift concurrency code for correctness, modern API usage, and adherence to project conventions. Report only genuine problems — do not nitpick or invent issues.
Core Instructions
- Target Swift 6.2 or later with strict concurrency checking.
- Prefer structured concurrency (task groups) over unstructured (
Task {}). - Prefer Swift concurrency over GCD for new code. GCD is still acceptable in low-level code, framework interop, or performance-critical synchronous work.
- Do not suggest
@unchecked Sendableto fix compiler errors — prefer actors, value types, orsendingparameters.
Review Process
- Scan for known-dangerous patterns using
references/hotspots.md. - Check for Swift 6.2 concurrency behavior using
references/new-features.md. - Validate actor usage for reentrancy and isolation using
references/actors.md. - Ensure structured concurrency is preferred using
references/structured.md. - Check unstructured task usage using
references/unstructured.md. - Verify cancellation handling using
references/cancellation.md. - Validate async stream and continuation usage using
references/async-streams.md. - Check bridging code between sync and async using
references/bridging.md. - Review legacy concurrency migrations using
references/interop.md. - Cross-check against common failure modes using
references/bug-patterns.md. - If strict-concurrency errors exist, map diagnostics to fixes using
references/diagnostics.md. - If reviewing tests, check async test patterns using
references/testing.md.
If doing partial work, load only the relevant reference files.
References
| Topic | Reference |
|---|---|
| Grep targets for code review — known-dangerous patterns | references/hotspots.md |
Swift 6.2: default isolation, @concurrent, Task.immediate, isolated deinit |
references/new-features.md |
| Actor reentrancy, global actor inference, isolation patterns | references/actors.md |
Task groups, async let, withDiscardingTaskGroup, concurrency limits |
references/structured.md |
Task vs Task.detached, when Task {} is a code smell |
references/unstructured.md |
Cooperative cancellation, withTaskCancellationHandler, broken patterns |
references/cancellation.md |
AsyncStream.makeStream(of:), continuation lifecycle, back-pressure |
references/async-streams.md |
Checked continuations, wrapping delegates, @unchecked Sendable |
references/bridging.md |
| GCD migration, Combine to AsyncSequence, completion handlers, locks | references/interop.md |
| Common concurrency failure modes LLMs produce and their fixes | references/bug-patterns.md |
| Strict-concurrency compiler errors mapped to likely fixes | references/diagnostics.md |
| Async test patterns, race detection, avoiding timing-based tests | references/testing.md |
04 同仓库更多 Skills
solana-dev
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering wallet connection, Anchor/Pinocchio programs, Codama client generation, LiteSVM/Mollusk/Surfpool testing, and security checklists. Integrates with the Solana MCP server for live documentation search. Prefers framework-kit (@solana/client + @solana/react-hooks) for UI, wallet-standard-first connection (incl. ConnectorKit), @solana/kit for client/RPC code, and @solana/web3-compat for legacy boundaries.
generating-trading-signals
Generate trading signals using technical indicators (RSI, MACD, Bollinger Bands, etc.). Combines multiple indicators into composite signals with confidence scores. Use when analyzing assets for trading opportunities or checking technical indicators. Trigger with phrases like "get trading signals", "check indicators", "analyze for entry", "scan for opportunities", "generate buy/sell signals", or "technical analysis".
prediction-monitor
Prediction Monitor - Auto-activating skill for ML Deployment. Triggers on: prediction monitor, prediction monitor Part of the ML Deployment skill category.
strategy-advisor
High-level strategic thinking and business decision guidance for planning and direction-setting. Use when: making strategic decisions, evaluating business options, setting direction, analyzing trade-offs, or when user mentions strategy, business planning, competitive analysis, or long-term planning.
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review RevenueCat/Adapty/Apphud/Superwall setup, calculate LTV/ROAS, or build paywall implementation.
figma
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.