Coding Guidelines

This gives Claude 50 core Rust conventions that go beyond what it already knows from training. It's meant for the non-obvious stuff: no get_ prefix on getters, when to use as_ versus to_ versus into_, why G_CONFIG for statics but no prefix for consts, and which crates have been deprecated by newer stdlib features (like OnceLock replacing lazy_static in 1.70). The tables are dense reference material, not tutorial content. Invoke this when you're doing code review, arguing about naming conventions, or wondering if there's a more idiomatic way to do something. It won't teach you Rust, but it will save you from bikeshedding and outdated patterns.

skills.sh installs: 4.2K
GitHub stars: 1.6K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add actionbook/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)