When should I use Mutex vs RwLock?

This skill suggests using Mutex for write-heavy shared state and RwLock for read-heavy scenarios, providing clear implementation patterns for both using Arc for thread-safe reference counting.

Can it distinguish between CPU-bound and I/O-bound work?

Yes, it provides a decision flowchart to help you choose between threads (std::thread/rayon) for CPU tasks and async (tokio) for I/O tasks to prevent blocking the executor.

How does this skill help with Rust compiler errors?

It identifies common concurrency errors like E0277 (Send/Sync) and provides specific design questions to help you choose the right fix, such as whether a type should actually cross threads, rather than just suggesting a quick patch.

Does it help with async-specific pitfalls?

Absolutely. It identifies anti-patterns like holding a MutexGuard across an await point, using thread::sleep in an async context, or ignoring deadlock risks in complex locking logic.

Rust Concurrency & Async Mastery

Name: Rust Concurrency & Async Mastery
Author: alphadoiy

byalphadoiy

•

開発者ツール

Optimizes Rust code performance and safety by providing expert guidance on concurrency primitives, async/await patterns, and thread-safety markers.

This skill empowers Claude to navigate the complexities of Rust's concurrency model, from low-level thread management to high-level asynchronous programming with Tokio. It provides a structured decision-making framework for choosing between CPU-bound parallelism and I/O-bound concurrency, helps resolve 'Send' and 'Sync' trait errors, and implements patterns to prevent deadlocks and race conditions. By tracing architectural constraints through domain-specific contexts—such as Web APIs or CLI tools—it ensures that your application's data sharing model is both performant and memory-safe according to Rust's strict ownership rules.

主な機能

01Provides domain-specific concurrency strategies for Web, CLI, and Cloud-Native architectures

02Distinguishes between CPU-bound parallelism and I/O-bound async tasks for optimal resource usage

03Identifies and fixes async anti-patterns like holding MutexGuards across await points

042 GitHub stars

05Recommends optimal synchronization primitives including Arc, Mutex, RwLock, and Atomics

06Resolves complex Send/Sync trait errors and E0277 compiler messages with design-first solutions

ユースケース

01Refactoring single-threaded code to use multi-threaded parallelism with Rayon or std::thread

02Implementing thread-safe shared state in high-concurrency web APIs or terminal dashboards

03Debugging deadlocks and performance bottlenecks in asynchronous Tokio runtimes

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add alphadoiy/timer m07-concurrency

For use in Claude.ai and ChatGPT