Coding Guidelines

The coding-guidelines skill provides developers with Rust-specific code style standards and best practices, covering naming conventions, data types, error handling, memory management, concurrency, and async patterns. It serves Rust programmers who need guidance on naming conventions, code formatting, and adherence to Rust idioms during code review and development. The skill solves the problem of inconsistent code style and suboptimal practices by offering a centralized reference to the 50 core rules from the official Rust Coding Guidelines.

skills.sh installs: 1.2K
GitHub stars: 1.3K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add zhanghandong/rust-skills --skill coding-guidelines --agent claude-code

Installs into .claude/skills of the current project.

Files

Rust Coding Guidelines (50 Core Rules)

Naming (Rust-Specific)

Rule	Guideline
No `get_` prefix	`fn name()` not `fn get_name()`
Iterator convention	`iter()` / `iter_mut()` / `into_iter()`
Conversion naming	`as_` (cheap &), `to_` (expensive), `into_` (ownership)
Static var prefix	`G_CONFIG` for `static`, no prefix for `const`

Data Types

Rule	Guideline
Use newtypes	`struct Email(String)` for domain semantics
Prefer slice patterns	`if let [first, .., last] = slice`
Pre-allocate	`Vec::with_capacity()`, `String::with_capacity()`
Avoid Vec abuse	Use arrays for fixed sizes

Strings

Rule	Guideline
Prefer bytes	`s.bytes()` over `s.chars()` when ASCII
Use `Cow<str>`	When might modify borrowed data
Use `format!`	Over string concatenation with `+`
Avoid nested iteration	`contains()` on string is O(n*m)