rust-patterns

Identify and enforce idiomatic Rust patterns for safety and performance.

Updated Mar 25, 2026

Search Tags:#ownership #concurrency #patterns #rust #idioms #error-handling #traits

Ready to run

npx skills add https://github.com/SOLEROM/cldlab --skill rust-patterns-solerom

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-patterns
Source: https://github.com/SOLEROM/cldlab/tree/main/ecc/ref_claude/skills/rust-patterns
Command: npx skills add https://github.com/SOLEROM/cldlab --skill rust-patterns-solerom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes idiomatic Rust conventions to prevent memory safety issues, enable zero-cost abstractions, and improve code quality across projects.

Core Features & Use Cases

Ownership and borrowing patterns to avoid data races and unnecessary clones.
Error handling guidelines using thiserror and anyhow for libraries and applications.
Enums, pattern matching, traits, and generics for safe, modular abstractions and scalable code.
Safe concurrency with Arc<Mutex<T>> and channels to build concurrent systems.

Quick Start

Audit your Rust module to apply ownership, error handling, and concurrency idioms in your codebase.

Frequently Asked Questions about rust-patterns

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

FAQPage Schema

How do I enforce idiomatic Rust patterns for ownership and borrowing?▼

Idiomatic Rust patterns enforce ownership and borrowing rules to prevent data races and eliminate unnecessary clones. Apply borrowing guidelines during code reviews or refactoring to ensure memory safety and zero-cost abstractions across modules.

What is the best way to handle errors in Rust libraries versus applications?▼

Error handling in Rust libraries should use thiserror for structured, typed errors, while applications benefit from anyhow for flexible context propagation. Enforcing Result and Option handling ensures robust error management across the codebase.

How do I build safe concurrency in Rust without causing data races?▼

Safe concurrency in Rust is built using Arc<Mutex<T>> for shared state and channels for message passing. Apply these concurrency idioms to build concurrent systems that prevent data races through strict ownership rules.

When do I need traits and generics for modular abstractions in Rust?▼

Traits and generics are needed in Rust when designing safe, modular abstractions for scalable code. Use enums and pattern matching alongside trait design to enforce minimal public surfaces and enable zero-cost abstractions.

Does this Rust patterns guidance work for both new code and refactoring existing modules?▼

Rust patterns guidance works for new code, code reviews, and refactoring existing modules. Audit your Rust module to apply ownership, error handling, and concurrency idioms to improve safety and performance.