Coding Guidelines
actionbook/rust-skillsWriting Rust code that is clean and consistent is important. This guide shares 50 core rules for Rust coding style and best practices. It covers naming, formatting, and common patterns. You will learn how to name functions and types, handle errors, and avoid deprecated features. Use these rules to make your code easier to read and review.
Developers who work on Rust projects can benefit from these guidelines. The rules come from real experience and official recommendations. They help you avoid common mistakes and follow the community standards. Whether you are new to Rust or an expert, these tips will improve your code quality.
The guide also includes a quick reference for naming, formatting, and documentation. It shows which old tools to replace with newer ones. Use this skill when you need advice on Rust code style or best practices.
Add Coding Guidelines skill to your workflow
Global
mkdir -p ~/.claude/skills/coding-guidelinesProject
mkdir -p .claude/skills/coding-guidelinesSource Repository
More Code Review & Quality Claude Code Skills
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues