| name | rust-orchestrator |
| description | Route a Rust task to the right skill — idiomatic patterns (ownership, errors, traits, concurrency, crate layout) versus testing (unit, integration, async, property-based, mocking, coverage, TDD). USE WHEN a user is writing, reviewing, refactoring, or testing Rust but hasn't named the specific concern. |
| cluster | rust |
| version | 1.0.0 |
Rust Orchestrator
The single entry skill for Rust work. It locates the task on the write ↔ verify axis
and delegates to one of two specialist spokes. The cross-cutting model both spokes share —
the library-vs-application error strategy (thiserror vs anyhow), the type-driven design
stance, and the standard cargo toolchain — lives in rust-core; read it before choosing an
error type or shaping a public API.
Cluster map (intent → spoke)
rust-patterns — idiomatic production code. Ownership & borrowing, Result/? error
propagation, enums + exhaustive matching, traits/generics, Arc<Mutex<T>> and async
concurrency, builder/newtype patterns, and domain-organized crate/module layout.rust-testing — verification. TDD RED-GREEN-REFACTOR, #[cfg(test)] unit tests,
tests/ integration binaries, #[tokio::test] async tests, parameterization,
property tests, trait mocking, doc tests, Criterion benches, and
coverage gates.
