What documentation sources does this skill use?

The skill is based on the Microsoft Rust Guidelines, the official Rust API Guidelines, and 'The Rust Programming Language' book.

Can this skill help with trait implementations?

Yes, it provides specific implementation patterns for common traits (Clone, Debug, Default), conversion traits (From, TryFrom, AsRef), and collection-specific traits (FromIterator, Extend).

Does this skill require specific Rust tools to be installed?

Yes, all code generated or modified using this skill must pass 'cargo clippy' and be formatted with 'cargo +nightly fmt' before submission.

How does it handle error management in Rust code?

It enforces the use of the std::error::Error trait, recommends 'thiserror' for libraries and 'anyhow' for applications, and mandates propagation via the '?' operator instead of 'unwrap()'.

Does it support safe usage of 'unsafe' code?

The skill prioritizes minimizing 'unsafe' code and requires all unsafe blocks to be isolated and accompanied by documented safety invariants.

Rust Development Best Practices

Name: Rust Development Best Practices
Author: cosmonic-labs

bycosmonic-labs

•

API Development

Enforces professional Rust development standards including naming conventions, type safety, and error handling patterns based on official community guidelines.

About

The Rust Development skill empowers Claude to act as a senior Rust architect, ensuring all code changes adhere to the highest industry standards for safety, performance, and maintainability. It covers essential areas such as strict naming conventions (RFC 430), idiomatic type safety patterns like Newtypes and Builders, and robust error handling using industry-standard libraries like thiserror and anyhow. By integrating guidelines from the official Rust API and Microsoft standards, it helps developers build production-ready Rust applications while maintaining consistent documentation and formatting requirements through mandatory clippy and fmt checks.

Key Features

Implements idiomatic type safety patterns using Newtypes, Enums, and the Builder pattern.
12 GitHub stars
Enforces strict naming conventions for modules, types, traits, and functions based on RFC 430.
Standardizes robust error handling using thiserror, anyhow, and early-return patterns.
Provides comprehensive guidance for implementing common, conversion, and collection traits.
Ensures high-quality documentation with required examples, panics, and safety sections.

Use Cases

Designing public-facing Rust APIs and libraries with consistent trait implementations and documentation.
Refactoring existing Rust codebases to meet modern idiomatic standards and guidelines.
Automating code reviews to ensure compliance with clippy, nightly formatting, and safety invariants.

About

Key Features

Implements idiomatic type safety patterns using Newtypes, Enums, and the Builder pattern.
12 GitHub stars
Enforces strict naming conventions for modules, types, traits, and functions based on RFC 430.
Standardizes robust error handling using thiserror, anyhow, and early-return patterns.
Provides comprehensive guidance for implementing common, conversion, and collection traits.
Ensures high-quality documentation with required examples, panics, and safety sections.

Use Cases

Designing public-facing Rust APIs and libraries with consistent trait implementations and documentation.
Refactoring existing Rust codebases to meet modern idiomatic standards and guidelines.
Automating code reviews to ensure compliance with clippy, nightly formatting, and safety invariants.