Rust quality — universal discipline for any Rust crate

This skill makes the model write idiomatic, well-tested, lint-clean Rust by default — not just code that compiles. It applies to libraries, binaries, sync code, async/tokio, no_std, embedded, wasm, and GPU host code. (For GPU kernel work, also load rust-gpu-discipline.)

Scope check before you start

Before writing or reviewing Rust, identify:

• Crate kind: library (lib.rs) or binary (main.rs) — error-handling discipline differs.
• Sync or async: presence of tokio, async-std, or async fn in the surface area.
• unsafe posture: does the crate use unsafe? If so, miri is mandatory.
• MSRV: read rust-version in Cargo.toml. Don't use newer features.
• Existing lint config: read Cargo.toml [lints] table and any #![…] crate attributes in lib.rs / main.rs before adding new ones.

If any of the above is unclear, read the manifest and the crate root file. Do not guess.

1. API design