AGENT SKILL

rust-concurrency-primitives

Design and review thread-based Rust concurrency with explicit ownership, sharing, and synchronization choices. Use when writing, refactoring, or reviewing threads, scoped threads, channels, Arc, Mutex, RwLock, Condvar, atomics, OnceLock, LazyLock, Send, Sync, deadlocks, or shared state.

License 许可
MIT
最近更新
2026-06-26
Stars
★ 0
Forks
0

01 前言 Front Matter

name
rust-concurrency-primitives
license
MIT
metadata
{ "tags": "rust,concurrency,threads,synchronization,atomics", "version": "0.1.0", "category": "Rust", "displayName": "Rust Concurrency Primitives" }
description
Design and review thread-based Rust concurrency with explicit ownership, sharing, and synchronization choices. Use when writing, refactoring, or reviewing threads, scoped threads, channels, Arc, Mutex, RwLock, Condvar, atomics, OnceLock, LazyLock, Send, Sync, deadlocks, or shared state.
compatibility
Codex, Claude Code, and other Agent Skills-compatible clients.

02 资源文件 2

03 SKILL.md 正文

Rust Concurrency Primitives

Use this skill to design thread-based Rust concurrency with explicit ownership, sharing, and synchronization. Prefer the simplest primitive that matches the coordination requirement before adding shared mutable state.

Core Workflow

  1. Classify the work: independent fork-join, producer/consumer pipeline, shared state, one-time initialization, or low-level atomic coordination.
  2. Prefer owned data per thread. Add shared ownership only when data must be observed or mutated by multiple threads.
  3. Use std::thread::scope when child threads can borrow stack data and must finish before the function returns.
  4. Use channels for ownership transfer and pipelines. Use Arc<Mutex<T>> or Arc<RwLock<T>> only when shared state is the clearer model.
  5. Keep lock scopes short and never call user-controlled or blocking code while holding a lock unless that is the invariant being protected.
  6. Use OnceLock or LazyLock for thread-safe one-time initialization instead of ad hoc global mutable state.
  7. Treat atomics as a specialized tool. Use SeqCst by default until a weaker ordering is justified and documented.

Primitive Selection

Read references/threading-shared-state.md before introducing a new shared state primitive or reviewing deadlock-prone code.

Need Primitive
Borrow local data into short-lived threads std::thread::scope
Transfer work or results std::sync::mpsc or project channel crate
Shared read/write state Arc<Mutex<T>>
Many readers, rare writers Arc<RwLock<T>>
Wait for condition changes Condvar with Mutex
One-time global initialization LazyLock or OnceLock
Counters, flags, lock-free coordination std::sync::atomic

Safety And Review Rules

  • Require Send for values crossing thread boundaries and Sync for shared references used from multiple threads.
  • Decide whether poisoning should propagate panic or recover with PoisonError::into_inner.
  • Establish a lock ordering when more than one lock can be acquired.
  • Prefer Arc::clone(&value) over value.clone() when the cloned value is an ownership handle and readability matters.
  • Use Rayon for data parallel iteration when the problem is pure CPU data parallelism and the project already accepts that dependency.

Tests

  • Add deterministic tests around final state, message counts, and shutdown.
  • Use barriers, channels, or scoped threads to coordinate tests; avoid sleeps.
  • Add at least one test for panic, dropped sender/receiver, or cancellation behavior when the code depends on it.

04 同仓库更多 Skills

ConcertoNotes
ConcertoNotes/codex-plugins

android-emulator-qa

Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

supabase-postgres-best-practices

Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

sentry

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

render-workflows

Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

render-web-services

Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.

★ 0
ConcertoNotes
ConcertoNotes/codex-plugins

render-static-sites

Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.

★ 0