coding-guidelines

Standard Rust naming conventions require snake_case for functions and variables, and CamelCase for types. This skill enforces these specific naming rules to help you keep identifiers consistent across small examples and large crates.

To apply rustfmt and Clippy recommendations, you can use this skill to receive standard-compliant formatting and linting guidance. It references specific rules to help you clean up code and align with established Rust best practices during reviews.

Yes, you can use this for Rust code reviews on large crates. The skill is designed to provide concise, standard-compliant feedback for Rust projects ranging from small examples to large crates, making it suitable for team reviews and educational sessions.

The best way to check if your Rust code follows standard guidelines is to apply this skill to your snippet. It cross-references your code with rustfmt, Clippy, and the Rust coding guidelines zh source to identify style and linting deviations.

Yes, this skill directly references the Rust coding guidelines zh source provided at rust-coding-guidelines.github.io. It encodes the rules from this documentation to enforce decisions across naming, formatting, and linting.