What problem does it solve? Writing Rust that merely compiles is not enough—code that overuses unwrap(), clones to silence the borrow checker, or blocks async executors leads to panics, wasted allocations, and subtle bugs in production. This Skill provides a concrete rulebook of idiomatic Rust patterns so code is safe, performant, and maintainable from the start. ## Core Features & Use Cases - Ownership & Error Handling: Enforces borrowing over cloning, Result/? propagation, thiserror for libraries, and anyhow for applications. - Type-Driven Design: Covers enums with exhaustive matching, the newtype pattern, builder pattern, and generics vs. trait objects to make illegal states unrepresentable. - Concurrency & Tooling: Guides safe shared state with Arc<Mutex<T>>, channels, Tokio async patterns, and essential commands like cargo clippy and cargo audit. - Use Case: When reviewing a pull request that calls .unwrap() in a config loader or uses std::thread::sleep inside an async function, apply this Skill to refactor it into ?-propagated errors with context and non-blocking tokio::time::sleep. ## Quick Start Review my Rust code and refactor it to follow idiomatic patterns for error handling, ownership, and concurrency.
