coding-standards

Standard Rust coding conventions require snake_case for modules and variables, PascalCase for types and traits, and SCREAMING_SNAKE_CASE for constants. Applying these rules ensures consistent style and structure across Rust crates during code reviews.

To audit a Rust project for coding standard violations, run this skill against the src/ directory to analyze naming, module layout, error handling, and documentation. It produces a concise checklist detailing deviations and suggested fixes.

Yes, you can use this skill to accelerate Rust onboarding by helping new team members align with established practices. It enforces team-wide coding conventions, reducing friction and ensuring consistent in-code documentation.

The best way to enforce error handling standards in Rust crates is to apply explicit coding guidelines during code analysis and refactoring. This ensures consistent module layout and error handling patterns are checked across the codebase.

Yes, this Rust style guide checks in-code documentation as part of its code review and audit process. It implements explicit guidelines for documentation to ensure comprehensive standards are maintained across all modules.