rust-async-concurrency
Design and review Rust async and concurrent ownership, tasks, cancellation, channels, queues, backpressure, overload, synchronization, parallelism, and shutdown. Use when work crosses tasks, threads, runtimes, pools, or suspension points. Do not impose an async runtime on synchronous libraries without repository approval.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-15
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- rust-async-concurrency
- description
- Design and review Rust async and concurrent ownership, tasks, cancellation, channels, queues, backpressure, overload, synchronization, parallelism, and shutdown. Use when work crosses tasks, threads, runtimes, pools, or suspension points. Do not impose an async runtime on synchronous libraries without repository approval.
02 资源文件 3
- 参考文档agents/openai.yaml262 B
- 参考文档references/concurrency.md15.0 KB
- 其他skill.toml1.5 KB
03 SKILL.md 正文
Engineer Async and Concurrent Rust
Establish ownership and rates
- Read
$rust-core, runtime and target policy, producer and consumer rates, queue capacities, retained bytes, latency assumptions, overload behavior, cancellation points, and shutdown ownership. - Read concurrency contracts.
- For each spawned work class, name the owner and handle, admission stop, shutdown signal, drain or discard decision, resource return, bounded join, timeout escalation, result and panic observer, and any approved detachment.
Design
Prefer returning a future, stream, or driver for the caller to own. Keep optional runtimes and Rayon pools application-owned. Specify queue semantics before selecting a primitive; centralize composite drop, coalescing, recycling, metadata, and shutdown behavior behind a narrow domain type.
Trace every select, timeout, abort, cancellation, or future race through the
losing operation and partial side effects. Avoid locks across suspension,
callbacks, blocking work, or uncontrolled operations.
Route correctness schedules to $rust-testing, rates and cutoffs to
$rust-performance, unsafe synchronization to $rust-unsafe-ffi, stream-loss
meaning to $rust-dsp, and framing recovery to $rust-protocol.
Verify
Test clean, busy, overloaded, cancelled, panicking, and missed-deadline paths. Use Loom, deterministic models, soak, or load tests when appropriate.
Output
Report the ownership graph, queue budget, cancellation safety, shutdown result, runtime requirements, and observed evidence.
04 同仓库更多 Skills
rust-unsafe-ffi
Design and review unsafe Rust, safe wrappers, manual Send or Sync, ABI boundaries, foreign ownership, callbacks, and FFI build integration. Use whenever unsafe code or a foreign interface is introduced, changed, or relied upon. Do not use unsafe merely to bypass borrow checking or for unmeasured optimization.
rust-testing
Select, implement, and assess Rust unit, integration, documentation, property, fuzz, snapshot, concurrency, unsafe, protocol, benchmark, and verification evidence. Use whenever behavior changes or claims need proof. Do not run every tool mechanically when the repository or risk makes it inapplicable.
rust-skill-maintenance
Maintain this modular Rust skills system, including canonical content, manifests, references, profiles, generated adapters, migrations, examples, evaluations, releases, and compatibility. Use when changing the skills repository itself. Do not hand-edit generated adapters.
rust-review
Review Rust diffs, commits, branches, and designs for actionable correctness, soundness, security, compatibility, concurrency, protocol, performance, testing, and maintainability risks. Use for review or pre-merge assessment. Do not modify code unless separately requested.
rust-repository-onboarding
Inspect, interview, profile, configure, and install the modular Rust engineering skills into a repository. Use when adopting or refreshing these skills, generating repository-specific Rust rules, or creating validation workflows. Never finalize policy before repository inspection and user approval.
rust-protocol
Engineer and review binary protocols, wire formats, builders, encoders, parsers, framing, stateful messages, bit ordering, integrity, correction, malformed input, and conformance. Use for protocol or serializer code. Do not apply protocol rules to unrelated in-memory models.