rust-professional-usage

What problem does it solve?

It prevents professional Rust mistakes—like unsafe without a written contract, panic/unwrap in library code, weak error modeling, and concurrency or async runtime errors—that otherwise surface as security risks, production incidents, and performance regressions.

Core Features & Use Cases

• Ownership, lifetimes, and borrowing discipline: encourages borrow-first design and deliberate use of cloning (including when Arc/Cow is appropriate).
• Typed error handling and panic boundaries: standardizes Result<T, E> with library-appropriate typed errors (thiserror) and application-level ergonomics (anyhow) while avoiding panic in libraries.
• Safety and concurrency guardrails: requires documented // SAFETY: invariants for unsafe, enforces singular async runtime choice, and stresses lock-scope rules to avoid deadlocks or await-in-lock patterns.
• Professional review checklist: provides review baselines across toolchain, formatting, linting, auditing, testing (including loom/miri where relevant), and performance measurement.

Quick Start

Use the rust-professional-usage skill to review or refactor your Rust change by asking an AI to check ownership/lifetimes, ensure typed Result error modeling, verify unsafe blocks have explicit // SAFETY: contracts, confirm tokio runtime singularity, and flag any unwrap/expect/panic usage in library code.