How do I install coding-guidelines?

Run `npx skills add https://github.com/zhanghandong/rust-skills --skill coding-guidelines` in your terminal. You need to have run `npx skills init` once in your project first.

Which agent frameworks does coding-guidelines support?

coding-guidelines works with any agent framework supported by the Skills registry, including Claude Code, Cursor, GitHub Copilot, Cline, Codex, and Gemini CLI.

Is coding-guidelines free to use?

Yes. coding-guidelines is free to install and use. It is available from the open explainx.ai skill registry published by zhanghandong.

Where can I read ratings and reviews for coding-guidelines?

Community ratings and review text appear on this explainx.ai skill page below the description. Reviews use a 1–5 scale and may include short written feedback from signed-in members.

Frontend

coding-guidelines▌

zhanghandong/rust-skills · updated Apr 8, 2026

$npx skills add https://github.com/zhanghandong/rust-skills --skill coding-guidelines

0 commentsdiscussion

summary

Rust naming, formatting, and best-practice guidelines covering 50 core rules.

›Covers naming conventions (no get_ prefix, iterator patterns, conversion methods), data types (newtypes, slice patterns, pre-allocation), and string handling (prefer bytes for ASCII, use Cow<str> when appropriate)
›Error handling guidance includes ? propagation over try!() , meaningful lifetime names, and lock ordering for concurrency safety
›Includes deprecation mappings (e.g., lazy_static! to OnceLock

skill.md

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)

Error Handling

Rule	Guideline
Use `?` propagation	Not `try!()` macro
`expect()` over `unwrap()`	When value guaranteed
Assertions for invariants	`assert!` at function entry

Memory

Rule	Guideline
Meaningful lifetimes	`'src`, `'ctx` not just `'a`
`try_borrow()` for RefCell	Avoid panic
Shadowing for transformation	`let x = x.parse()?`

Concurrency

Rule	Guideline
Identify lock ordering	Prevent deadlocks
Atomics for primitives	Not Mutex for bool/usize
Choose memory order carefully	Relaxed/Acquire/Release/SeqCst

Async

Rule	Guideline
Sync for CPU-bound	Async is for I/O
Don't hold locks across await	Use scoped guards

Macros

Rule	Guideline
Avoid unless necessary	Prefer functions/generics
Follow Rust syntax	Macro input should look like Rust

Deprecated → Better

Deprecated	Better	Since
`lazy_static!`	`std::sync::OnceLock`	1.70
`once_cell::Lazy`	`std::sync::LazyLock`	1.80
`std::sync::mpsc`	`crossbeam::channel`	-
`std::sync::Mutex`	`parking_lot::Mutex`	-
`failure`/`error-chain`	`thiserror`/`anyhow`	-
`try!()`	`?` operator	2018

Quick Reference

Naming: snake_case (fn/var), CamelCase (type), SCREAMING_CASE (const)
Format: rustfmt (just use it)
Docs: /// for public items, //! for module docs
Lint: #![warn(clippy::all)]

Claude knows Rust conventions well. These are the non-obvious Rust-specific rules.

Discussion

Product Hunt–style comments (not star reviews)

No comments yet — start the thread.

general reviews

Ratings

4.5★★★★★74 reviews

★★★★★Yusuf Mensah· Dec 20, 2024
I recommend coding-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
★★★★★Zara Huang· Dec 20, 2024
Useful defaults in coding-guidelines — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
★★★★★Shikha Mishra· Dec 16, 2024
coding-guidelines has been reliable in day-to-day use. Documentation quality is above average for community skills.
★★★★★Zara Khan· Dec 12, 2024
Keeps context tight: coding-guidelines is the kind of skill you can hand to a new teammate without a long onboarding doc.
★★★★★Ren Gupta· Dec 12, 2024
I recommend coding-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
★★★★★Evelyn Ndlovu· Dec 8, 2024
Solid pick for teams standardizing on skills: coding-guidelines is focused, and the summary matches what you get after install.
★★★★★Emma Thomas· Dec 8, 2024
coding-guidelines has been reliable in day-to-day use. Documentation quality is above average for community skills.
★★★★★Sakshi Patil· Nov 27, 2024
Solid pick for teams standardizing on skills: coding-guidelines is focused, and the summary matches what you get after install.
★★★★★Evelyn Abebe· Nov 27, 2024
Keeps context tight: coding-guidelines is the kind of skill you can hand to a new teammate without a long onboarding doc.
★★★★★Ishan Martin· Nov 23, 2024
I recommend coding-guidelines for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

showing 1-10 of 74

1 / 8