agentleFS
spatiespatie/bloom/.claude/skills/swift-concurrency-pro/SKILL.md

swift-concurrency-pro

Skill52 starsChanged 50 days agoMITView on GitHub

Write and review Bloom Swift concurrency code for actor isolation, task lifetime, cancellation and stream correctness.

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use swift-architecture-skill, swiftdata-pro and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • molayabSkill

    swift-architecture-skill

    Swift architecture patterns and playbooks for MVVM, TCA, Clean Architecture, and more.

    Also in 4 projects that use this

  • twostrawsSkill

    swiftdata-pro

    Writes, reviews, and improves SwiftData code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use SwiftData.

    Also in 4 projects that use this

  • Erikote04Skill

    swift-api-design-guidelines-skill

    Write, review, or improve Swift APIs using Swift API Design Guidelines for naming, argument labels, documentation comments, terminology, and general conventions. Use when designing new APIs, refactoring existing interfaces, or reviewing API clarity and fluency.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check Package.swift and the actual target's compiler flags before inferring isolation.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Swift concurrency in Bloom

Check Package.swift and the actual target's compiler flags before inferring isolation. Bloom uses Swift 6 language mode with a Swift 6.2 minimum toolchain; that alone does not enable default MainActor isolation or NonisolatedNonsendingByDefault.

Preserve the intended task lifetime. Structured concurrency fits work owned by a caller; unstructured tasks also have legitimate uses for UI actions and app-owned background services. Audit their ownership, cancellation and errors rather than replacing them mechanically.

In reviews, report reproducible defects with file locations and effects. Make requested edits directly. Do not silence sendability errors without establishing how shared state is protected.

Load only the references needed for the task:

  • Hotspots: search targets for a concurrency review.
  • Swift 6.2 settings: isolation defaults and newer APIs.
  • Actors: reentrancy and isolation boundaries.
  • Structured tasks: task groups, errors and concurrency limits.
  • Unstructured tasks: inheritance and ownership.
  • Cancellation: cooperative cancellation and teardown.
  • Streams: buffering, termination and consumer lifetime.
  • Bridging: continuations and sendability guarantees.
  • Interop: GCD, locks, delegates and Combine.
  • Bug patterns: recurring failure modes.
  • Diagnostics: compiler errors and boundary choices.
  • Testing: deterministic concurrency checks and the shared testing guide.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.