rust-best-practices
This skill provides a set of guidelines and best practices for writing idiomatic, performant, and safe Rust code based on the Apollo GraphQL handbook.
Is rust-best-practices safe to install?
Review the source first: our audit of rust-best-practices's source files found 2 shell commands, 0 external URLs, file reads and writes (high risk). Every command and URL listed appears verbatim in the skill's source. The skill executes shell commands including cargo clippy, which interacts with the local file system and project environment.
How we audit skills: our security review methodology.
Who is this skill for?
Rust developers who want to align their code with Apollo GraphQL's engineering standards.
What can you do with it?
- Writing new Rust code or functions
- Reviewing or refactoring existing Rust code
- Deciding between borrowing and cloning or ownership patterns
- Implementing error handling with Result types
- Optimizing Rust code for performance
- Writing tests or documentation for Rust projects
How good is this skill?
Quality score: 5/10. The skill provides clear, actionable technical guidelines and specific CLI commands for maintaining code quality in Rust projects.
What does the skill file contain?
# Rust Best Practices Apply these guidelines when writing or reviewing Rust code. Based on Apollo GraphQL's [Rust Best Practices Handbook](https://github.com/apollographql/rust-best-practices). ## Best Practices Reference Before reviewing, familiarize yourself with Apollo's Rust best practices. Read ALL relevant chapters in the same turn in parallel. Reference these files when providing feedback: - [Chapter 1 - Coding Styles and Idioms](references/chapter_01.md): Borrowing vs cloning, Copy trait, Option/Result handling, iterators, comments - [Chapter 2 - Clippy and Linting](references/chap...
Frequently asked questions
What Rust versions does this skill support?
The skill supports Rust 1.70 and newer.
How should I handle errors in my Rust code?
Return Result types for fallible operations, avoid panic in production, use thiserror for libraries, use anyhow for binaries, and use the ? operator for propagation.
What is the recommended approach for linting?
Run cargo clippy with the --all-targets, --all-features, and --locked flags, and use the -D warnings flag to treat lints as errors.
Related skills
golang-code-style
33.3KGo developers and AI coding agents performing code reviews or writing new Go code
This skill provides a comprehensive set of Go code style conventions focused on clarity, maintainability, and idiomatic patterns. It covers variable declarations, control flow, function design, file organization, and string handling, serving as a guide for human-judgment-based code reviews that complement automated linters.
mcp-apps-builder
16.1KDevelopers building MCP servers with the mcp-use framework
A framework-specific guide for building, testing, and deploying MCP servers using the mcp-use library. It provides architectural patterns, security best practices, and CLI instructions for developers.
react-email
6.0KDevelopers building transactional or marketing emails who want to use React components and Tailwind CSS for styling
React Email provides a framework for building and sending HTML emails using React components. It includes a development server for previewing templates, a library of email-specific components, and an embeddable visual editor.
shopify-customer
5.0KShopify developers building applications that interact with the Customer Account API
The shopify-customer skill assists developers in writing GraphQL queries and mutations for the Shopify Customer Account API. It enforces a mandatory workflow requiring documentation search and code validation via provided scripts before returning results.