clean-rustlisted

# Clean Rust Rust-specific conventions for writing, reviewing, and refactoring. The core rules below always apply. Load the one reference file matching the task's domain; don't load them all. If the `clean-code` skill is installed, its language-agnostic principles (function size, naming hygiene, comment discipline) still apply. Where generic advice conflicts with Rust idiom, this skill wins. Classic examples: "prefer exceptions over error codes" maps to `Result`, never panics; "replace switch with polymorphism" maps to exhaustive `match`, which in Rust is a feature, not a smell. | Task touches | File | |---|---| | Error types, propagation helpers, failure semantics, retries | `references/error-handling.md` | | async/await, tokio, `select!`, channels, spawned child processes | `references/async.md` | | Threads, atomics, lock ordering, drop order | `references/concurrency.md` | | Process-global mutable state (env vars, global overrides) across threads | `references/edition-2024.md` | | Public API shape, builders, newtypes, typestate, serde | `references/api-design.md` | | Any `unsafe` block, FFI, raw pointers, exported symbols | `references/unsafe.md` | | Writing tests or debugging test infrastructure | `references/testing.md` | | Hot paths, allocations, string building, hasher choice | `references/performance.md` | | Benchmarks, criterion, `#[bench]` | `references/performance.md` | | Secret files on disk, keys and tokens at rest | `references/security.md` | | Logging, traci