skills.rest
jmduea
jmdueaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

coding-guidelines

Provide Rust coding style and best-practice advice for code review queries.

Updated Feb 12, 2026
Search Tags:#best practices#coding style#rust#clippy#lint#naming
One-click install
npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill coding-guidelines-jmduea
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/jmduea/emotiv-cortex-rs/tree/main/.github/skills/coding-guidelines
Command: npx skills add https://github.com/jmduea/emotiv-cortex-rs --skill coding-guidelines-jmduea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the guesswork and inconsistency when Rust developers need clear guidance on naming, formatting, linting, and overall code style best practices.

Core Features & Use Cases

  • Comprehensive Rules: Offers 50 core Rust coding rules covering naming, data types, strings, error handling, memory, concurrency, async, and macros.
  • Clippy Mapping: Provides a concise mapping of common Clippy lints to actionable fixes.
  • Deprecated → Better: Highlights modern replacements for outdated patterns.
  • Use Case: When reviewing code or refactoring, a developer can query the skill for the appropriate convention, such as the correct prefix for static variables or the preferred iterator method.

Quick Start

Ask the coding‑guidelines skill for the proper naming convention of a Rust getter function.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema
What are the Rust naming conventions for static variables and getter functions?▼

Rust naming conventions for static variables and getter functions follow specific prefix rules. The coding guidelines provide definitive answers on correct prefixes and naming formats, ensuring code review consistency.

How do I fix common Clippy lints in my Rust code?▼

Fix Clippy lints in Rust code by applying actionable mappings from common lint warnings to corrected patterns. The guidelines map deprecated Rust patterns to modern replacements for refactoring outdated code.

What are the best practices for Rust error handling and async concurrency?▼

Best practices for Rust error handling and async concurrency are covered by 50 core rules. These rules span data types, strings, memory, concurrency, and macros to guide developers through code review queries.

Does this Rust coding style guidance apply to source code contexts without running external tools?▼

Yes, this Rust coding style guidance applies directly within source code contexts without external execution. It references 50 core rules and Clippy lint mappings internally to provide best-practice advice.

What is the preferred Rust iterator method to replace deprecated patterns?▼

The preferred Rust iterator method replaces deprecated patterns using modern alternatives highlighted by the coding guidelines. Refactoring code reviews query these conventions to find the correct iterator approach.

Related Skills

Explore More Software Engineering Skills→
OMIXECOMIXEC
1

coding-guidelines

Provide Rust code style and best practices guidance for libraries and applications.

Community
Intermediate
y1feng200156y1feng200156
33

rust-lint

Automate Rust code quality checks and formatting with Clippy and Rustfmt.

Community
Intermediate
peancharoenpeancharoen

speckit.checker

Run static analysis tools to detect linting, type, and security issues across source code.

Community
Advanced
deandumdeandum
3

style

Enforce language-agnostic coding style and conventions across a codebase.

Community
Intermediate