coding-guidelines

This skill is a condensed Rust code-style and best-practices reference distilled into roughly 50 core rules. It solves a narrow but common problem: when writing or reviewing Rust, it is easy to miss the non-obvious, Rust-specific conventions (naming, ownership-flavored conversions, iterator naming, error propagation) that separate idiomatic code from code that merely compiles. The skill surfaces those rules on demand so an assistant can apply them during code review or authoring.

The content is organized as compact reference tables covering naming (no `get_` prefix, `iter`/`iter_mut`/`into_iter`, `as_`/`to_`/`into_` conversion prefixes), data types and newtypes, string handling, error handling (`?` propagation, `expect` over `unwrap`), memory and lifetimes, concurrency and lock ordering, async guidance, and macros. It also includes a deprecated-to-preferred migration table (for example `lazy_static!` toward `OnceLock`, `try!()` toward the `?` operator) and a Clippy-lint-to-fix mapping. It points to an upstream source (the Chinese-language Rust Coding Guidelines site) for the full 500+ rule set, so it is intentionally a curated subset rather than an exhaustive linter.

It is aimed at Rust developers, reviewers, and AI coding assistants performing code review or style enforcement, including bilingual (English/Chinese) users given the keyword coverage. Typical use is answering "how should I name this?" or "what is the idiomatic pattern here?" during everyday Rust work. It does no code execution and simply provides guidance.