coding-guidelines

Rust naming, formatting, and best-practice guidelines covering 50 core rules. Claude knows Rust conventions well. These are the non-obvious Rust-specific rules. - Covers naming conventions (no get_ prefix, iterator patterns, conversion methods), data types (newtypes, slice patterns, pre-allocation), and string handling (prefer bytes for ASCII, use Cow when appropriate) - Error handling guidance includes ? propagation over try!() , meaningful lifetime names, and lock ordering for concurrency safety - Includes deprecation mappings (e.g., lazy_static! to OnceLock , failure to thiserror ) and quick reference for formatting, documentation, and linting standards - Designed as a reference for code review and style decisions in Rust projects