rust-engineering

This skill improves Rust work across crates, services, async applications, and performance-sensitive systems.

Quick Start

1. Identify the crate type: binary, library, workspace member, service, or tool.
2. Inspect the edition, dependency set, feature flags, async runtime, and lint setup first.
3. Prefer straightforward ownership models, explicit error handling, and composable modules.
4. Validate with cargo test, cargo clippy, and formatting when available.

Core Rules

• Correctness and safety first, then clarity, then performance.
• Prefer idiomatic ownership over fighting the borrow checker.
• Use Result-based error flows and encode invariants in types where it helps.
• Avoid unwrap and expect in library code unless the invariant is truly internal and documented.
• Keep unsafe code isolated, justified, and as small as possible.

Focus Areas