ia-rust-systems

Enforce disciplined Rust patterns for CLI tools and backend services.

30|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/iliaal/whetstone --skill ia-rust-systems
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ia-rust-systems
Source: https://github.com/iliaal/whetstone/tree/main/plugins/whetstone/skills/ia-rust-systems
Command: npx skills add https://github.com/iliaal/whetstone --skill ia-rust-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves Rust project drift by enforcing consistent, production-minded patterns for CLI tools, backend services, and workspace structure so changes stay verifiable and maintainable.

Core Features & Use Cases

  • Cargo workspace discipline: layered crate dependencies, centralized versions/lints, and stable library facade design for clean boundaries.
  • Production-grade Rust practices: typed error handling, async Tokio conventions, ownership/performance guidance, and clippy/rustfmt/test tooling.
  • Service & CLI patterns: clap derive CLIs and axum/tower HTTP services with structured errors, tracing guidance, and resilience practices.

Quick Start

Ask an AI to generate a Rust 2024 Cargo workspace with a clap-based CLI and an axum + tokio service, following workspace lints, typed errors, and verification steps.

Frequently Asked Questions about ia-rust-systems

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

FAQPage Schema
How do I structure a Rust Cargo workspace for production backend services?▼

Structure a Rust Cargo workspace by enforcing layered crate dependencies, centralized versions and lints, and a stable library facade. This maintains clean boundaries so changes stay verifiable and prevents multi-crate project drift.

What is the best way to handle errors in async Tokio and Axum applications?▼

The best way to handle errors in async Tokio and Axum applications is by enforcing typed error handling architecture. This provides structured errors and fail-fast feature gating without relying on unsafe shortcuts.

How do I set up Rust CLI tools with clap and production verification tooling?▼

Set up Rust CLI tools using clap derive patterns alongside clippy, rustfmt, and nextest. Apply cargo-deny configuration and CI test readiness to ensure disciplined, verifiable command-line applications.

Does this Rust workspace pattern require edition 2024?▼

Yes, this pattern targets Rust edition 2024 application code. It applies modern async conventions and production resilience defaults specifically designed for the latest edition's ownership and performance guidance.

How do I add observability and resilience to Axum and Tokio backend services?▼

Add observability and resilience to Axum and Tokio services by applying structured tracing guidance and production resilience defaults. This ensures fail-fast operations and maintainable layered ownership in backend deployments.

When should I avoid unsafe shortcuts in Rust service architecture?▼

Avoid unsafe shortcuts whenever building production CLI tools or backend services requiring verifiable maintainability. Enforcing typed errors, clippy, and cargo-deny setups prevents drift without compromising performance or safety.