Rust Best Practices
Skill Verified ActiveGuide for writing idiomatic Rust code based on Apollo GraphQL's best practices handbook. Use this skill when: (1) writing new Rust code or functions, (2) reviewing or refactoring existing Rust code, (3) deciding between borrowing vs cloning or ownership patterns, (4) implementing error handling with Result types, (5) optimizing Rust code for performance, (6) writing tests or documentation for Rust projects.
To guide developers in writing idiomatic, performant, and robust Rust code by adhering to established best practices.
Features
- Idiomatic Rust coding styles
- Performance optimization techniques
- Robust error handling with Result types
- Effective testing strategies
- Guidelines for generics and dispatch
- Best practices for documentation and comments
Use Cases
- Writing new Rust code or functions
- Reviewing or refactoring existing Rust code
- Deciding between borrowing vs cloning or ownership patterns
- Implementing error handling with Result types
- Optimizing Rust code for performance
- Writing tests or documentation for Rust projects
Non-Goals
- Providing a full Rust language tutorial
- Automating Rust code writing directly
- Replacing static analysis tools like clippy (though it references them)
Installation
First, add the marketplace
/plugin marketplace add apollographql/skills/plugin install skills@apollo-marketplaceQuality Score
VerifiedTrust Signals
Similar Extensions
Dart Matcher Best Practices
100Best practices for using `expect` and `package:matcher`. Focuses on readable assertions, proper matcher selection, and avoiding common pitfalls.
Supabase Postgres Best Practices
99Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
Cleanup Defensive
99Remove pointless try/catch blocks and defensive guards that hide errors or add no value. Preserves catches at true system boundaries (HTTP handlers, CLI entry, message consumers). Use when the user asks to remove try/catch, fix error hiding, clean up defensive code, or stop swallowing errors. Example queries — "remove pointless try/catch", "we're swallowing errors", "stop hiding bugs in catch blocks", "clean up the defensive code".
Neon Postgres
100Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
Sdk Dx
100Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: "SDK design", "developer experience", "API design", "SDK DX", "error messages", "type safety", "IDE integration", "SDK versioning", "migration guides", "client library design", "making SDKs feel native", "SDK best practices"
Csharp Async
100Get best practices for C# async programming