elite-rust

Enforce Rust Edition 2024, typed errors, and test-driven workflows.

Updated Dec 24, 2025
One-click install
npx skills add https://github.com/so-sai/TachFile_To --skill elite-rust
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elite-rust
Source: https://github.com/so-sai/TachFile_To/tree/main/.agent/skills/elite-rust
Command: npx skills add https://github.com/so-sai/TachFile_To --skill elite-rust

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Elite Rust Standards enforce edition compliance, robust error handling, and disciplined testing to prevent unsafe patterns and brittle codebases.

Core Features & Use Cases

  • Enforces Rust Edition 2024 and dependency version pinning for stability.
  • Mandates typed errors via thiserror and anyhow, and explicit async usage with tokio.
  • Promotes a test-driven workflow with a mandatory red-phase failing test and walkthrough verification.
  • Guides interoperability and observability practices to maintain clean contracts across modules.

Quick Start

Set up a Rust project to Edition 2024, pin Polars 0.52.x, replace unwrap/expect with proper error handling, enable #[tracing::instrument], and begin with a failing test to initiate the Red phase.

Frequently Asked Questions about elite-rust

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

FAQPage Schema
How do I enforce safe error handling in Rust without using unwrap or expect?

Safe Rust error handling replaces unwrap and expect with typed errors using thiserror for library-specific errors and anyhow for application boundaries. This approach prevents runtime panics and ensures robust error propagation across modules.

What's the best way to set up a Rust project for Edition 2024 and pinned dependencies like Polars?

Configuring Rust Edition 2024 involves updating the Cargo manifest and pinning dependencies such as Polars to a specific 0.52.x version. This ensures build stability and enforces elite standards across library and runtime components.

How does test-driven development with a red phase work for async Rust applications?

Rust TDD with a red phase requires writing a failing test before implementation. For async applications using tokio, this involves creating async test functions that initially fail, guiding development through verification workflows.

Can I use thiserror and anyhow together for error handling in Rust libraries?

Yes, thiserror and anyhow can be combined in Rust projects. thiserror creates custom typed errors for library APIs, while anyhow provides flexible error handling at application boundaries, ensuring clean contracts across modules.

Why should I enable tracing instrumentation for async Rust runtime components?

Enabling tracing instrumentation in Rust provides explicit observability for async runtime components. It allows you to trace execution flows across tokio tasks, which is critical for maintaining clean contracts and diagnosing issues.

Does Rust Edition 2024 require explicit async usage patterns with tokio?

Rust Edition 2024 promotes disciplined async usage, and using tokio satisfies this requirement. Explicit async patterns ensure safe and robust runtime behavior across IPC boundaries and concurrent operations.