What problem does it solve? Rust code that compiles but reads like ported Java or C++ is hard to review and maintain. This Skill provides a reference catalog of naming conventions, idiomatic constructs, and common anti-patterns so you can write Rust that the ecosystem recognizes as native and catch code smells during review. ## Core Features & Use Cases - Naming Conventions: Applies the Rust API Guidelines for types, functions, conversions (as_/to_/into_), iterators, and constructors. - Idiomatic Construct Catalog: Covers From/TryFrom conversions, Default + struct-update, iterator chains, concise control flow (let ... else, matches!), derive ordering, and minimal visibility. - Anti-Pattern Detection: Flags smells like unwrap() on reachable paths, &Vec<T> parameters, stringly-typed data, premature Arc<Mutex<T>>, and Deref used to fake inheritance, each with the fix. - Use Case: While reviewing a pull request, you spot fn process(data: &Vec<String>) and a wildcard match on a domain enum. Use this Skill to identify both as anti-patterns and apply the slice-parameter and exhaustive-match fixes. ## Quick Start Review my Rust function for idiomatic style and flag any anti-patterns like unwrap usage, &Vec parameters, or stringly-typed arguments.
