What problem does it solve? Writing Rust that is readable, maintainable, and consistent across public APIs and internal code requires juggling many guidelines, lint configurations, and dependency decisions. This Skill routes each concrete design decision to the right authoritative reference and enforces a strict Clippy profile so Rust changes meet a uniform quality bar. ## Core Features & Use Cases - Decision-based reference routing: Maps each design question (naming, ownership, error design, builders, FFI, async, performance) to one primary guide drawn from the Rust API Guidelines, Microsoft Pragmatic Rust Guidelines, and Rust Design Patterns. - Strict Clippy validation: Ships a strict-clippy.sh runner with curated lint levels and clippy.toml thresholds, plus a policy for fixing, expecting, or suppressing findings. - Dependency selection guidance: Evaluates crates by total maintenance cost with categorized candidate tables for common code, data, async, procedural macros, and tests. - Use Case: When refactoring a Rust crate's error handling, the Skill routes the error-type contract to the API guidelines, checks whether thiserror fits, implements the change, and validates it with the strict Clippy runner. ## Quick Start Use the write-idiomatic-rust skill to review and refactor the error handling in my Rust crate and run the strict Clippy check.
