What problem does it solve? Choosing the right crate from Rust's large ecosystem is error-prone: developers pick outdated versions, mix incompatible async runtimes, or leak anyhow errors from library APIs. This Skill provides a decision map of the de-facto standard crates per domain so selections are consistent, current, and idiomatic. ## Core Features & Use Cases - Domain-to-crate decision map: Covers serde for serialization, clap for CLI parsing, tokio for async runtime, axum for web, reqwest for HTTP clients, sqlx/sea-orm/diesel for databases, thiserror/anyhow for errors, and tracing for observability. - Selection criteria and guardrails: Explains the library-vs-application error handling split, the sqlx vs sea-orm vs diesel trade-offs, and rules like never writing serde = "2" and never mixing async runtimes. - Ready-to-adapt manifest template: Includes a complete Cargo.toml and main.rs for an async web service with feature flags scoped to what is actually needed. - Use Case: When starting a new Rust web service, consult the decision map to pick axum + tokio + sqlx, verify current versions on crates.io, and scaffold the manifest from the provided template. ## Quick Start Ask the agent to recommend crates for a new async Rust web service with PostgreSQL and have it verify current versions before writing the Cargo.toml.
