rust-design-rules

Enforce clippy policy and forbid unsafe code in Rust crates by applying design rules that restrict unsafe blocks at crate roots except for explicit hardware access, while running clippy checks during code reviews and CI pipelines.

Rust coding standards for module documentation checks require explicit module-level documentation with specific compliance sections, ensuring every file details its purpose and adherence to project rules before passing review.

Standardize Rust coding practices across a large project by enforcing rules for clippy policies, citation formatting, system state read prohibition, and performance-aware construction patterns during code writing, reviews, and xtask commands.

This Rust design rule set discourages FFI and enforces a strict system state read prohibition, preventing components from directly reading global state and requiring safer alternative patterns for data access.

The best Rust patterns for safe initialization and string splitting involve using OnceLock for thread-safe lazy initialization and splitn for controlled string segmentation, avoiding unsafe code while maintaining performance.