Can it help with library and crate selection?

Absolutely. It suggests modern crate alternatives, such as using anyhow or thiserror instead of older libraries like failure or error-chain.

Does it handle complex concurrency and async rules?

Yes, it provides specific guidelines for lock ordering, using atomics for primitives, and avoiding holding locks across await points in asynchronous code.

How does this skill improve my Rust code quality?

It ensures Claude follows idiomatic patterns like using newtypes for domain semantics, efficient memory management techniques, and standard naming conventions that align with the official Rust ecosystem.

Does it support the latest stable Rust features?

Yes, it specifically includes guidance for modern stable features like OnceLock (1.70+) and LazyLock (1.80+), replacing older external dependencies.

Rust Coding Guidelines

Name: Rust Coding Guidelines
Author: actionbook

byactionbook

•

596

Developer Tools

Enforces idiomatic Rust patterns, naming conventions, and modern best practices during code generation and review.

About

The Rust Coding Guidelines skill equips Claude with 50 core rules for writing high-quality, idiomatic Rust code based on established industry standards. It covers essential topics including Rust-specific naming conventions, memory safety patterns, efficient string handling, and modern error propagation. By referencing up-to-date crate recommendations—such as transitioning from lazy_static to OnceLock—this skill ensures that AI-generated code remains performant, safe, and aligned with the latest stable Rust standards, making it an indispensable tool for both greenfield development and legacy refactoring.

Key Features

Provides best practices for safe concurrency and scoped async I/O management.
Enforces Rust-specific naming conventions for iterators, conversions, and statics.
Optimizes memory usage through newtypes, slice patterns, and pre-allocation strategies.
Guides modern error handling using the '?' operator and contemporary error crates.
Recommends modern alternatives to deprecated crates like lazy_static and failure.
596 GitHub stars

Use Cases

Refactoring legacy Rust code to utilize modern 1.80+ syntax and standard library features.
Performing automated code reviews to ensure adherence to idiomatic Rust style and performance.
Generating high-performance, memory-safe code snippets for systems programming tasks.

About

Key Features

Provides best practices for safe concurrency and scoped async I/O management.
Enforces Rust-specific naming conventions for iterators, conversions, and statics.
Optimizes memory usage through newtypes, slice patterns, and pre-allocation strategies.
Guides modern error handling using the '?' operator and contemporary error crates.
Recommends modern alternatives to deprecated crates like lazy_static and failure.
596 GitHub stars

Use Cases

Refactoring legacy Rust code to utilize modern 1.80+ syntax and standard library features.
Performing automated code reviews to ensure adherence to idiomatic Rust style and performance.
Generating high-performance, memory-safe code snippets for systems programming tasks.