Rust Best Practices

Apply these guidelines when writing, reviewing, refactoring, testing or debugging Rust code.

Working Approach

• Read the affected code, tests, Cargo.toml, toolchain pin and CI commands first. Respect the project's edition, MSRV, feature combinations and conventions.
• If the affected crate uses Bevy, read Bevy practices before applying generic borrowing, import or lint advice to system functions.
• Keep application code direct: concrete types, simple control flow and no speculative traits or builders. Libraries with external callers need deliberate public contracts.
• Model the domain with Rust's ownership, enums, traits and Result; do not translate inheritance or exception patterns mechanically from another language.
• During refactoring, preserve public signatures, error variants, output ordering and behavior unless changing them is in scope. Explain necessary contract changes; do not rename getters or replace existing parameters merely to satisfy a style preference.
• Read-only reviews produce findings, not edits. Stay within the requested change; installing tools, upgrading dependencies or publishing is not implied by this skill.