Rust Patterns

This skill is for day-to-day idiomatic Rust: clear ownership, small APIs, and code that feels native to the language instead of a direct port from somewhere else.

If the task is primarily profiling/benchmarking, use rust-performance. If the task is primarily test design or test repair, use rust-testing.

When to activate

• Writing or refactoring .rs modules, libraries, CLIs, or services
• Reviewing Rust PRs for ownership, borrowing, API shape, and common footguns
• Porting code from C/C++/Go/Python into idiomatic Rust
• Improving error handling, trait design, iterators, module boundaries, concurrency, or docs
• Choosing a dispatch/plugin mechanism, or building low-level/offensive Rust with unsafe, FFI, or RE-resistant builds

Core rules (high signal)