coding-guidelines

Standardize Rust code style with naming, formatting, and linting guidelines.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/kkingsbe/tempest --skill coding-guidelines-kkingsbe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/kkingsbe/tempest/tree/main/skills/coding-guidelines
Command: npx skills add https://github.com/kkingsbe/tempest --skill coding-guidelines-kkingsbe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This guide helps Rust teams achieve consistent, idiomatic code by outlining naming conventions, formatting rules, lints, and review practices.

Core Features & Use Cases

  • Naming conventions for variables, functions, types, and modules to promote clarity and maintainability.
  • Formatting and style guidance using rustfmt and clippy recommendations to catch common mistakes.
  • Code-review checklists and best practices for documenting changes and ensuring code quality across projects.

Quick Start

Consult these guidelines when starting a new Rust module to apply standardized naming, formatting, and linting.

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 code style across my development team?

Standardizing Rust code style requires applying consistent naming conventions, formatting rules via rustfmt, clippy lints, and structured review checklists to improve readability and maintainability across projects.

What naming conventions should I use for Rust modules and functions?

Rust naming conventions for variables, functions, types, and modules promote clarity and maintainability, ensuring standardized idiomatic code across varying project sizes.

How do I set up rustfmt and clippy for a new Rust module?

Setting up rustfmt and clippy involves applying their formatting and style recommendations to catch common mistakes, using these tools as the foundation for your project's code quality checks.

What should be included in a Rust code review checklist?

A Rust code review checklist should include best practices for documenting changes, verifying naming conventions, checking rustfmt and clippy compliance, and ensuring overall code quality across projects.

Can these Rust coding guidelines be applied to projects of any size?

Yes, these Rust coding guidelines apply to projects of varying sizes, focusing on standardizing naming, formatting, comments, and tooling requirements to support consistent discovery and maintainability.