rust-development

Guide idiomatic Rust development across multi-crate cargo workspaces.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/terraphim/terraphim-skills --skill rust-development-terraphim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-development
Source: https://github.com/terraphim/terraphim-skills/tree/main/skills/rust-development
Command: npx skills add https://github.com/terraphim/terraphim-skills --skill rust-development-terraphim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps Rust developers write idiomatic, safe, and performant Rust code that adheres to proven patterns and a correctness-first mindset.

Core Features & Use Cases

  • Correctness-First Workflow: Emphasizes building, testing, and benchmarking in a disciplined loop to prevent regressions.
  • Modular Architecture Guidance: Recommends workspace organization with clear module boundaries and crate boundaries to keep concerns separate.
  • Rust Ecosystem Best Practices: Encourages safe error handling, zero-cost abstractions, and ergonomic API design with guidance on common Rust patterns.

Quick Start

Describe a basic starter approach: set up a cargo workspace, enable clippy and rustfmt, and apply the provided patterns to a sample project.

Frequently Asked Questions about rust-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I structure a Rust project with multiple crates using cargo workspaces?

Cargo workspaces organize Rust projects by defining clear crate and module boundaries to keep concerns separate. This modular architecture ensures sustainable development across multi-crate environments while maintaining strict correctness.

What are idiomatic Rust patterns for safe error handling?

Idiomatic Rust error handling applies safe patterns and robust mechanisms to prevent runtime failures. A correctness-first workflow ensures error handling remains ergonomic while leveraging zero-cost abstractions for high-performance execution.

Does this Rust workflow require specific linting or formatting tools?

The Rust workflow recommends enabling clippy and rustfmt alongside standard cargo tooling. These tools enforce idiomatic patterns and formatting, preventing regressions during the build, test, and benchmark loop.

What's the best way to prevent regressions in async Rust development?

Preventing regressions in async Rust requires a correctness-first workflow that builds, tests, and benchmarks in a disciplined loop. This approach maintains high performance and safety without sacrificing ergonomic API design.

Can I apply these Rust best practices to an existing modular codebase?

You can apply these Rust best practices to existing projects by enforcing clear module boundaries and safe error handling. The provided patterns integrate with common Rust tooling to refactor codebases toward idiomatic and safe architecture.