rust-engineer

Write, review, and debug idiomatic Rust code with memory safety.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/MileniumTick/skills --skill rust-engineer-mileniumtick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-engineer
Source: https://github.com/MileniumTick/skills/tree/main/skills/rust-engineer
Command: npx skills add https://github.com/MileniumTick/skills --skill rust-engineer-mileniumtick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps Rust developers write, review, and debug idiomatic Rust code with strong memory safety and zero-cost abstractions, addressing ownership, borrowing, and lifetime management.

Core Features & Use Cases

  • Ownership and borrowing guidance to design safe APIs
  • Trait-based API design and generic programming patterns
  • Async programming with tokio and error handling with Result/Option
  • Guidance for building performant, memory-efficient systems and FFI bindings.

Quick Start

Analyze a Rust project by running cargo clippy, cargo fmt, and cargo test to verify safety and style.

Frequently Asked Questions about rust-engineer

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

FAQPage Schema
How do I fix Rust ownership and lifetime errors when designing safe APIs?

Fix Rust ownership and lifetime errors by applying proper borrowing rules, adding explicit lifetime annotations, and designing trait-based APIs to ensure memory safety across modules and crates.

What is the best way to structure async Rust applications with tokio?

Structure async Rust applications with tokio by implementing runtime management, handling concurrency through async/await syntax, and managing errors using Result and Option types for robust execution.

How do I write idiomatic Rust code for systems programming and FFI bindings?

Write idiomatic Rust code for systems programming and FFI bindings by leveraging zero-cost abstractions, defining safe boundaries for foreign function interfaces, and applying trait-based generic programming patterns.

How do I debug Rust code and ensure it passes validation checks?

Debug Rust code and ensure validation by running cargo clippy for linting, cargo fmt for style enforcement, and cargo test to rigorously verify memory safety and functional correctness.

Can I use Rust traits to build generic APIs across different crates?

You can use Rust traits to build generic APIs across different crates by defining shared behavior interfaces, implementing trait objects for dynamic dispatch, and ensuring safe ownership boundaries across library modules.

Why does Rust require explicit lifetime annotations in my function signatures?

Rust requires explicit lifetime annotations in function signatures when the borrow checker cannot infer relationships between references, ensuring memory safety by validating that references do not outlive their underlying data.