coding-guidelines

Standardize Rust naming, formatting, and linting conventions across codebases.

1.4k|110|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/actionbook/rust-skills --skill coding-guidelines-actionbook
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/actionbook/rust-skills/tree/main/skills/coding-guidelines
Command: npx skills add https://github.com/actionbook/rust-skills --skill coding-guidelines-actionbook

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized set of Rust coding guidelines to help teams enforce consistent style, naming, formatting, and linting across projects.

Core Features & Use Cases

  • Naming conventions: snake_case for identifiers, CamelCase for types, and consistent prefixes/suffixes.
  • Formatting and linting guidance: recommendations for rustfmt and clippy usage to catch common issues early.
  • Code-review checklists: reusable checks to speed up reviews and maintain quality.
  • Use Case: When onboarding a new Rust project, apply these guidelines to align contributor habits and reduce review time.

Quick Start

Refer to the Rust coding guidelines in the repository and apply the rules to your codebase. You can consult the in-repo references for detailed rule descriptions and examples.

Frequently Asked Questions about coding-guidelines

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Rust coding conventions across my development team?

Standardize Rust coding conventions by applying centralized guidelines for naming, formatting, and linting. This ensures consistent style across projects and reduces code review time by aligning contributor habits.

What naming conventions should I use for Rust types and identifiers?

Rust naming conventions dictate snake_case for identifiers and CamelCase for types. Applying consistent prefixes and suffixes across your codebase ensures readability and aligns with standard Rust practices.

How do rustfmt and clippy help enforce Rust coding guidelines?

Rustfmt and clippy enforce Rust coding guidelines by automating formatting and catching common lint issues early. Integrating them into your workflow maintains code quality and aligns with best practices.

Can I use these Rust coding guidelines for automated code reviews?

You can use these Rust coding guidelines for automated code reviews by applying reusable checklists. These checks speed up reviews, verify naming and formatting, and maintain quality during onboarding.

What is the best way to onboard new contributors to a Rust project?

The best way to onboard new contributors to a Rust project is applying centralized coding guidelines. This aligns contributor habits with naming, rustfmt, and clippy rules, reducing review time and ensuring quality.