It also covers matching an existing project's Cargo.toml conventions before introducing a
competing crate, and the version-verification discipline (never trust a remembered patch
number; confirm current versions on crates.io/Context7/Exa).
Out of scope: once a crate is chosen, its detailed API usage belongs to the matching domain
skill (rust-web-backend, rust-async-concurrency, rust-error-handling) or direct docs
verification (docs.rs/crates.io → Context7 → Exa).
Rust Ecosystem & Crates
Agent Workflow (MANDATORY)
Before ANY crate selection, spawn 3 agents in parallel, one Agent call each with a name:
- fuse-ai-pilot:explore-codebase - Read existing
Cargo.toml to match established choices
- fuse-ai-pilot:research-expert - Confirm the CURRENT version + maintenance status on crates.io via Context7/Exa
- mcp__context7__query-docs - Pull the chosen crate's current API before writing code
After implementation, run fuse-ai-pilot:sniper for validation.
Overview — the decision map
| Domain |
De-facto standard (2026) |
Reach for it when |
| Serialization |
serde (+ serde_json) |
Any (de)serialization; derive Serialize/Deserialize |
| CLI parsing |
clap (derive API) |
Argument parsing, subcommands, help generation |
| Async runtime |
tokio |
Almost all async I/O; the ecosystem default |
| Web framework |
axum |
HTTP servers on tokio + tower middleware |
| HTTP client |
reqwest |
Outbound HTTP, JSON, TLS |
| Database |
sqlx / sea-orm / diesel |
See db-and-async.md for the choice |
| Error (libraries) |
thiserror |
Typed error enums in a library's public API |
| Error (apps) |
anyhow |
Ergonomic Result with context in binaries |
| Observability |
tracing (+ tracing-subscriber) |
Structured, async-aware logs and spans |
Critical Rules
- ALWAYS verify the current version before writing a
Cargo.toml - versions move faster than this skill. Confirm on crates.io or via Context7; never paste a remembered patch number.
serde 2.0 is NOT stable - it is under discussion. Depend on serde = "1" today; do not write 2.0.
thiserror for libraries, anyhow for applications - never expose anyhow::Error in a library's public API.
- One async runtime - standardize on
tokio; mixing runtimes causes executor conflicts.
- Match existing choices first - read the project's
Cargo.toml before introducing a competing crate.
Architecture
Cargo.toml
├── [dependencies]
│ ├── serde / serde_json # data
│ ├── tokio (features = [...]) # runtime
│ ├── axum / reqwest # web in/out
│ ├── sqlx | sea-orm | diesel # persistence (pick one)
│ ├── thiserror | anyhow # errors (lib vs app)
│ └── tracing / tracing-subscriber
→ See cargo-toml-stack.md for a complete manifest
Reference Guide
Concepts
| Topic |
Reference |
When to Consult |
| Decision map |
crate-decision-map.md |
Choosing per domain, error strategy, observability |
| DB & async |
db-and-async.md |
sqlx vs sea-orm vs diesel, tokio + axum wiring |
Templates
| Template |
When to Use |
| cargo-toml-stack.md |
Scaffolding a web-service manifest |
Quick Reference
Error handling split
// Library: typed, matchable errors.
#[derive(thiserror::Error, Debug)]
pub enum StoreError {
#[error("not found: {0}")]
NotFound(String),
}
// Application: contextual, any error.
use anyhow::Context;
let cfg = std::fs::read_to_string(path).context("reading config")?;
→ See crate-decision-map.md for the full rationale
Best Practices
DO
- Verify each crate's current version on crates.io before committing it
- Standardize on
tokio and enable only the features you use
- Use
thiserror in libraries, anyhow in binaries
- Prefer the crate the project already uses over a "better" alternative
DON'T
- Write
serde = "2" — it is not stable
- Hardcode a remembered patch version without checking
- Expose
anyhow::Error from a library API
- Mix async runtimes in one binary
1---2name: rust-ecosystem-crates3description: Use when choosing crates for a Rust project — serialization, CLI, async runtime, web, database, HTTP client, error handling, observability. Not for API usage details of an already-chosen crate.4versions:5 serde: "1"6 tokio: "1"7 clap: "4"8user-invocable: false9references: references/crate-decision-map.md, references/db-and-async.md, references/templates/cargo-toml-stack.md10related-skills: rust-tooling-cicd, solid-rust11metadata:12 source: https://skillmd.com/skills/fusengine/rust-ecosystem-crates13---1415<objective>16This skill provides a domain-to-crate decision map of the de-facto 2026 Rust ecosystem17standards — serde for serialization, clap for CLI parsing, tokio for async, axum for web,18sqlx/sea-orm/diesel for database access, thiserror/anyhow for error handling split by19library vs application, and tracing for observability — plus the selection criteria behind20each choice.2122It also covers matching an existing project's Cargo.toml conventions before introducing a23competing crate, and the version-verification discipline (never trust a remembered patch24number; confirm current versions on crates.io/Context7/Exa).2526Out of scope: once a crate is chosen, its detailed API usage belongs to the matching domain27skill (rust-web-backend, rust-async-concurrency, rust-error-handling) or direct docs28verification (docs.rs/crates.io → Context7 → Exa).29</objective>3031# Rust Ecosystem & Crates3233## Agent Workflow (MANDATORY)3435Before ANY crate selection, spawn 3 agents in parallel, one `Agent` call each with a `name`:36371. **fuse-ai-pilot:explore-codebase** - Read existing `Cargo.toml` to match established choices382. **fuse-ai-pilot:research-expert** - Confirm the CURRENT version + maintenance status on crates.io via Context7/Exa393. **mcp__context7__query-docs** - Pull the chosen crate's current API before writing code4041After implementation, run **fuse-ai-pilot:sniper** for validation.4243---4445## Overview — the decision map4647| Domain | De-facto standard (2026) | Reach for it when |48|--------|--------------------------|-------------------|49| **Serialization** | `serde` (+ `serde_json`) | Any (de)serialization; derive `Serialize`/`Deserialize` |50| **CLI parsing** | `clap` (derive API) | Argument parsing, subcommands, help generation |51| **Async runtime** | `tokio` | Almost all async I/O; the ecosystem default |52| **Web framework** | `axum` | HTTP servers on tokio + tower middleware |53| **HTTP client** | `reqwest` | Outbound HTTP, JSON, TLS |54| **Database** | `sqlx` / `sea-orm` / `diesel` | See db-and-async.md for the choice |55| **Error (libraries)** | `thiserror` | Typed error enums in a library's public API |56| **Error (apps)** | `anyhow` | Ergonomic `Result` with context in binaries |57| **Observability** | `tracing` (+ `tracing-subscriber`) | Structured, async-aware logs and spans |5859---6061## Critical Rules62631. **ALWAYS verify the current version before writing a `Cargo.toml`** - versions move faster than this skill. Confirm on crates.io or via Context7; never paste a remembered patch number.642. **`serde 2.0` is NOT stable** - it is under discussion. Depend on `serde = "1"` today; do not write `2.0`.653. **`thiserror` for libraries, `anyhow` for applications** - never expose `anyhow::Error` in a library's public API.664. **One async runtime** - standardize on `tokio`; mixing runtimes causes executor conflicts.675. **Match existing choices first** - read the project's `Cargo.toml` before introducing a competing crate.6869---7071## Architecture7273```74Cargo.toml75├── [dependencies]76│ ├── serde / serde_json # data77│ ├── tokio (features = [...]) # runtime78│ ├── axum / reqwest # web in/out79│ ├── sqlx | sea-orm | diesel # persistence (pick one)80│ ├── thiserror | anyhow # errors (lib vs app)81│ └── tracing / tracing-subscriber82```8384→ See [cargo-toml-stack.md](references/templates/cargo-toml-stack.md) for a complete manifest8586---8788## Reference Guide8990### Concepts9192| Topic | Reference | When to Consult |93|-------|-----------|-----------------|94| **Decision map** | [crate-decision-map.md](references/crate-decision-map.md) | Choosing per domain, error strategy, observability |95| **DB & async** | [db-and-async.md](references/db-and-async.md) | sqlx vs sea-orm vs diesel, tokio + axum wiring |9697### Templates9899| Template | When to Use |100|----------|-------------|101| [cargo-toml-stack.md](references/templates/cargo-toml-stack.md) | Scaffolding a web-service manifest |102103---104105## Quick Reference106107### Error handling split108109```rust110// Library: typed, matchable errors.111#[derive(thiserror::Error, Debug)]112pub enum StoreError {113 #[error("not found: {0}")]114 NotFound(String),115}116117// Application: contextual, any error.118use anyhow::Context;119let cfg = std::fs::read_to_string(path).context("reading config")?;120```121122→ See [crate-decision-map.md](references/crate-decision-map.md) for the full rationale123124---125126## Best Practices127128### DO129- Verify each crate's current version on crates.io before committing it130- Standardize on `tokio` and enable only the features you use131- Use `thiserror` in libraries, `anyhow` in binaries132- Prefer the crate the project already uses over a "better" alternative133134### DON'T135- Write `serde = "2"` — it is not stable136- Hardcode a remembered patch version without checking137- Expose `anyhow::Error` from a library API138- Mix async runtimes in one binary