What problem does it solve? Writing and reviewing Rust code often leads to common mistakes like unnecessary cloning, unwrap() panics, wildcard match arms, and blocking calls in async contexts. This Skill provides a structured reference of idiomatic Rust patterns so code follows ownership, error handling, and concurrency best practices from the start. ## Core Features & Use Cases - Ownership and Error Handling Patterns: Enforces borrowing over cloning, Result/? propagation, thiserror for libraries, and anyhow for applications. - Type-Safe Design Guidance: Covers enums for state modeling, exhaustive matching, newtype wrappers, builder patterns, and minimal pub visibility. - Concurrency and Async Patterns: Provides Arc<Mutex<T>>, bounded channels, and Tokio async patterns with timeouts and task spawning. - Use Case: When reviewing a Rust pull request that uses unwrap() in library code and clones data to satisfy the borrow checker, use this Skill to rewrite it with typed errors and proper borrowing. ## Quick Start Review my Rust module for idiomatic patterns and suggest fixes for error handling and ownership issues.