coding-guidelines

Provide Rust naming, formatting, and linting guidelines for code reviews.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/lywa1998/self-host-claude-marketplace --skill coding-guidelines-lywa1998
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/lywa1998/self-host-claude-marketplace/tree/main/plugins/rust-skills/skills/coding-guidelines
Command: npx skills add https://github.com/lywa1998/self-host-claude-marketplace --skill coding-guidelines-lywa1998

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rust code style and best-practices guidance is consolidated to help maintain consistent naming, formatting, and linting across projects.

Core Features & Use Cases

  • Naming conventions: guidance on variable, function, and type naming to improve readability and maintainability.
  • Formatting and style: recommendations for using rustfmt and consistent code layout.
  • Lint and review guidance: how to apply Clippy rules and structure effective code reviews.
  • Use Case: When reviewing Rust code, quickly decide on naming, formatting, and linting decisions for a given snippet or module.

Quick Start

Ask for Rust coding guidelines for a given project or code snippet and request specific style recommendations.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema
What are the standard Rust naming conventions for variables, functions, and types?

Standard Rust naming conventions dictate using snake_case for variables and functions, and UpperCamelCase for types and structs to improve code readability and maintainability across your project.

How do I apply rustfmt to enforce consistent Rust code formatting?

You apply rustfmt to enforce consistent Rust code formatting by running the tool to automatically parse and reformat code layout according to standard style recommendations during development.

How do I use Clippy rules to guide Rust code reviews?

You use Clippy rules to guide Rust code reviews by running the linter to catch common mistakes and enforce conventions, then applying the resulting lint guidance to structure effective feedback on snippets and modules.

Can I get specific Rust style recommendations for a given code snippet?

Yes, you can request specific Rust style recommendations for a given code snippet to quickly decide on naming, formatting, and linting decisions during code reviews or pair programming sessions.

When do I need to check Rust coding guidelines during development?

You need to check Rust coding guidelines during code reviews, pair programming, and documentation tasks whenever Rust conventions for naming, formatting, or linting are in question.