coding-guidelines

Name: coding-guidelines
Availability: InStock
Author: OMIX

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

1|Updated Apr 13, 2026

Search Tags:#linting #rust #clippy #naming #rustfmt #code-style

Ready to run

npx skills add https://github.com/OMIXEC/Mobile-dev-skills --skill coding-guidelines-omixec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coding-guidelines
Source: https://github.com/OMIXEC/Mobile-dev-skills/tree/main/skills/coding-guidelines
Command: npx skills add https://github.com/OMIXEC/Mobile-dev-skills --skill coding-guidelines-omixec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides concise, opinionated Rust coding style guidance and actionable lint recommendations to reduce inconsistent code, clippy noise, and review friction across teams.

Core Features & Use Cases

Style rules summary: Clear conventions for naming, formatting, lifetimes, and documentation to make code more readable and maintainable.
Lint mapping and remediation: Mappings from common Clippy lints to concrete fixes and modernization suggestions (for example, using ? instead of try! and preferring OnceLock over lazy_static).
Practical application: Use during code reviews, refactors, or when establishing project-level style guides to enforce idiomatic and safe Rust patterns.

Quick Start

Ask the coding-guidelines skill to review my Rust file and list naming, formatting, and clippy fixes with explanations.

Frequently Asked Questions about coding-guidelines

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

FAQPage Schema

How do I fix common Rust clippy lints during code reviews?▼

To fix common Rust clippy lints, apply concrete remediation mappings that replace deprecated patterns like try! with ? and lazy_static with OnceLock. This enforces idiomatic Rust code and resolves review friction across team projects.

What are the best practices for Rust naming and formatting conventions?▼

Rust naming and formatting best practices involve following clear conventions for lifetimes, variables, and documentation to improve readability. Using rustfmt ensures consistent code style, making source code more maintainable across libraries and applications.

How do I enforce Rust async and error handling guidelines in my project?▼

To enforce Rust async and error handling guidelines, establish a project-level style guide that defines safe concurrency patterns and error propagation rules. This ensures consistent handling of asynchronous operations and safe error management across the codebase.

Does this Rust style guidance work for both libraries and applications?▼

Yes, this Rust style guidance works for both libraries and applications. It provides concise, opinionated coding conventions applicable to various source code scenarios, including refactoring, code reviews, and establishing project-level style enforcement.

When should I modernize my Rust codebase to replace lazy_static with OnceLock?▼

You should modernize your Rust codebase to replace lazy_static with OnceLock when addressing clippy lint warnings during refactoring. Mapping legacy patterns to modern standard library equivalents reduces dependency overhead and aligns with current idiomatic Rust practices.