m07-concurrency

To fix a Rust deadlock, you must analyze lock ordering and thread ownership. This Skill guides safe sharing and thread-safety decisions, enforcing patterns for Mutex locking and deadlock avoidance across multi-threaded and async Rust code.

You should choose between Arc, Mutex, and channels based on thread ownership and data sharing needs. This Skill provides a layered reasoning framework to help you select the right concurrency primitives for safe, scalable apps.

To enforce Send and Sync bounds in async Rust, you must reason from domain constraints down to language mechanics. This Skill analyzes tokio and futures workloads to ensure your thread-safety guarantees prevent data races.

Yes, this concurrency guidance applies to both CPU-bound and I/O-bound workloads. It offers practical patterns and domain-aware best practices for async runtimes like tokio and async-std in web services and CLI tools.

The best way to resolve Rust thread-safety issues is through layer-based reasoning from domain to design to mechanics. This Skill analyzes your code snippet to enforce Send/Sync guarantees and identify safe sharing patterns.