How do I install the Rust Dev skill?

Run npx skillmds@latest add tomevault-io/rust-dev in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Rust Dev safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Rust Dev?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Rust Dev free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Rust Dev?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Rust Dev by tomevault-io — Agent Skill

Name: Rust Dev
Author: tomevault-io

Rust Dev

This skill should be used when working with Rust code, reviewing Rust code, managing Rust dependencies, creating Rust projects, or fixing Rust compilation errors. It provides strict coding standards (especially FAIL FAST error handling), workspace architecture guidance, dependency management automation, and common Rust patterns. Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

Rust Development

Core Rules

Edition 2024: Always edition = "2024" in Cargo.toml
FAIL FAST: Every error MUST propagate with ? or return Err. Logging is NOT handling. See error-handling.md
Dependency versions: Use x.x format (e.g., serde = "1.0"). Find latest with python3 scripts/check_crate_version.py <crate>
Workspace architecture: Root Cargo.toml defines workspace only. Separate crates for lib/cli/client
Error types: thiserror (with backtrace) for libraries, anyhow for binaries/tests
CLI-first config: Never bypass CLI args. Use from_cli_args(), never Default that reads env
No env::set_var in tests: Pass config through function parameters
Async: Use tokio consistently
Visibility: Private (default) > pub(crate) > pub
No magic numbers: Use const or CLI args

Adding Dependencies

Run python3 scripts/check_crate_version.py <crate-name> to find latest version
Add to [workspace.dependencies] in root Cargo.toml with x.x format
Reference in member crates: serde = { workspace = true }

Common deps: thiserror = "2.0", anyhow = "1.0", tokio = { version = "1", features = ["full"] }, serde = { version = "1.0", features = ["derive"] }, clap = { version = "4.5", features = ["derive"] }

Creating New Projects

Use the template in assets/workspace-template/:

project/
├── Cargo.toml              # Workspace root, no code
├── project/                # Library crate (thiserror)
│   ├── Cargo.toml
│   └── src/lib.rs
└── project-cli/            # Binary crate (anyhow + clap)
    ├── Cargo.toml
    └── src/main.rs

Module Organization

Split modules when file exceeds ~500 lines or tests take 50%+ of file. See module-organization.md for patterns.

Error Handling

The most critical standard. See error-handling.md for full rules and examples.

Quick check: If you see if let Err or match ... Err without return Err or ?, it's a bug.

References

error-handling.md — FAIL FAST rules, thiserror/anyhow patterns, error chain preservation
module-organization.md — When/how to split modules, test extraction
dependency-guide.md — Workspace deps, feature flags, common crates

Scripts

scripts/check_crate_version.py — Query crates.io for latest dependency versions

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: rust-devdescription: This skill should be used when working with Rust code, reviewing Rust code, managing Rust dependencies, creating Rust projects, or fixing Rust compilation errors. It provides strict coding standards (especially FAIL FAST error handling), workspace architecture guidance, dependency management automation, and common Rust patterns. Use when this capability is needed.---# Rust Development## Core Rules1. **Edition 2024**: Always `edition = "2024"` in Cargo.toml2. **FAIL FAST**: Every error MUST propagate with `?` or `return Err`. Logging is NOT handling. See [error-handling.md](references/error-handling.md)3. **Dependency versions**: Use `x.x` format (e.g., `serde = "1.0"`). Find latest with `python3 scripts/check_crate_version.py <crate>`4. **Workspace architecture**: Root Cargo.toml defines workspace only. Separate crates for lib/cli/client5. **Error types**: `thiserror` (with backtrace) for libraries, `anyhow` for binaries/tests6. **CLI-first config**: Never bypass CLI args. Use `from_cli_args()`, never `Default` that reads env7. **No `env::set_var` in tests**: Pass config through function parameters8. **Async**: Use tokio consistently9. **Visibility**: Private (default) > `pub(crate)` > `pub`10. **No magic numbers**: Use `const` or CLI args## Adding Dependencies1. Run `python3 scripts/check_crate_version.py <crate-name>` to find latest version2. Add to `[workspace.dependencies]` in root Cargo.toml with `x.x` format3. Reference in member crates: `serde = { workspace = true }`Common deps: `thiserror = "2.0"`, `anyhow = "1.0"`, `tokio = { version = "1", features = ["full"] }`, `serde = { version = "1.0", features = ["derive"] }`, `clap = { version = "4.5", features = ["derive"] }`## Creating New ProjectsUse the template in `assets/workspace-template/`:```project/├── Cargo.toml # Workspace root, no code├── project/ # Library crate (thiserror)│ ├── Cargo.toml│ └── src/lib.rs└── project-cli/ # Binary crate (anyhow + clap) ├── Cargo.toml └── src/main.rs```## Module OrganizationSplit modules when file exceeds ~500 lines or tests take 50%+ of file. See [module-organization.md](references/module-organization.md) for patterns.## Error HandlingThe most critical standard. See [error-handling.md](references/error-handling.md) for full rules and examples.**Quick check:** If you see `if let Err` or `match ... Err` without `return Err` or `?`, it's a bug.## References- [error-handling.md](references/error-handling.md) — FAIL FAST rules, thiserror/anyhow patterns, error chain preservation- [module-organization.md](references/module-organization.md) — When/how to split modules, test extraction- [dependency-guide.md](references/dependency-guide.md) — Workspace deps, feature flags, common crates## Scripts- `scripts/check_crate_version.py` — Query crates.io for latest dependency versions---> Converted and distributed by [TomeVault](https://tomevault.io/claim/onsails) — claim your Tome and manage your conversions.

Frequently asked questions