rust-async-concurrencylisted

## Outcome Produce async Rust whose concurrency is explicitly bounded, whose tasks and resources have clear owners, whose cancellation and shutdown behavior is observable, and whose verification matches the target repository rather than an assumed Cargo layout. ## Compatibility Portable across Claude Code, Codex, and OpenCode. Follow the target repository's pinned Rust toolchain, edition, MSRV, runtime, features, and CI policy; Edition 2024 examples require Rust 1.85 or newer. The templates are adaptable snippets and may require already-approved Tokio, Tokio-util, or futures features; the `TaskTracker` template specifically requires Tokio-util's `rt` feature. Network research is optional, but without it mark version-sensitive API claims unverified. Native-client compatibility remains unverified until a validated report records the client version and exact source SHA. ## Use this skill when - Choosing between direct `.await`, `join!`, `select!`, streams, `JoinSet`, or owner tasks. - Bounding fan-out, queues, worker capacity, or access to a finite resource. - Fixing blocking calls, locks held across `.await`, detached tasks, or clone-heavy ownership. - Designing cancellation, graceful shutdown, time budgets, `LocalSet`, or a sync/async bridge. ## Do not use this skill when - HTTP/gRPC semantics, retryability, request deadlines, or connection pools dominate; use `rust-networking`. - The primary task is test placement or test-suite design; use `rust-testing-strategy`. -