rust-best-practices

Rust ownership and borrowing best practices involve establishing clear guidelines for managing memory safely without a garbage collector. This skill codifies rules from Apollo GraphQL's handbook to help teams write idiomatic, safe, and maintainable code.

Error handling with Result types in Rust is guided by established best practices to ensure error safety and maintainability. This skill provides codified guidelines derived from Apollo GraphQL's handbook to enforce proper Result type usage across your codebase.

Writing idiomatic Rust code for large codebases requires enforcing code quality, error safety, and maintainability across reviews and onboarding. This skill applies Apollo GraphQL's Rust Best Practices Handbook to maintain consistency across new and existing Rust projects.

Yes, this Rust best practices guide covers comprehensive testing and documentation practices. It supports writing tests and documentation that align with established Rust best practices to improve readability and safety during codebase audits.

You can use these Rust guidelines as a reference during code reviews, refactoring, and platform upgrades. The skill serves to maintain consistency and reduce review time and onboarding friction across your Rust projects.

You need a codified set of Rust best practices when starting a new Rust project or auditing an existing codebase to improve readability and safety. It reduces review time and onboarding friction by providing clear guidelines for ownership, borrowing, and error handling.