rc-rust

# Rust Best Practices Unified Rust guidelines covering coding style, ownership, error handling, async patterns, traits, testing, performance, linting, and documentation. Apply when writing or reviewing Rust code. ## Pair with This skill owns Rust *the language*. The stack's layers live elsewhere — reach for them instead of duplicating their guidance here: - `rc-axum` — HTTP routing, extractors, Tower middleware, `IntoResponse` error mapping, WebSockets - `rc-sqlx` — `PgPool`, query macros, transactions, migrations, `#[sqlx::test]` - `rc-sveltekit` — the SSR front end that consumes these APIs - `rc-fullstack-axum-svelte` — the router when a change spans more than one layer - `rc-final-verify` — after `cargo fmt`/`clippy`/`test` come back green ## When to Apply - Writing new Rust code or designing APIs - Reviewing or refactoring existing Rust code - Implementing async systems with Tokio - Designing error hierarchies with thiserror/anyhow - Choosing between borrowing, cloning, or ownership transfer - Setting up tests, benchmarks, or snapshot testing - Configuring clippy lints and workspace settings - Optimizing Rust code for performance ## Reference Guide Load detailed guidance based on context. Read the relevant file when the topic arises: | Topic | Reference | Load When | |-------|-----------|-----------| | Coding Style | `references/coding-style.md` | Naming, imports, iterators, comments, string handling, macros | | Error Handling | `references/error-handling.md` | R...