rust-engineer — Claude Code skill: what it does, how to install
Guides the agent to write and review idiomatic Rust 2021 code. Useful when designing traits, resolving borrow checker errors, and building async tokio services.
npx skills add Jeffallan/claude-skills --skill rust-engineer -a claude-codeWhat rust-engineer does
This skill establishes strict implementation standards for Rust 2021 code. It designs ownership before writing code. Instead of cloning buffers to appease the borrow checker, the agent prefers slices like &str and &[u8].
Error handling relies on Result and thiserror rather than raw panics. Async workflows focus on tokio, keeping blocking operations strictly outside async tasks. Calling unwrap() in production code is prohibited, which forces the agent to handle edge cases through typed errors.
Validation steps require passing cargo clippy --all-targets --all-features, formatting with cargo fmt, and running unit tests. Every unsafe block must document its safety invariants.
What it helps with
- resolve borrow checker errors and add explicit lifetime annotations
- design trait hierarchies with generics and associated types
- implement async services using tokio without blocking calls
- structure application errors with
Result,?, andthiserror - document safety invariants for necessary
unsafeblocks
Example prompts for the agent
- Fix borrowing and lifetime errors in src/parser.rs without cloning data
- Design an async API client using tokio with custom errors via thiserror
- Review the FFI module and document all safety invariants for unsafe blocks
How to install rust-engineer
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rust-engineer -a claude-code2Manually: put the files in place
~/.claude/skills/rust-engineer/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/rust-engineer/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rust-engineer -a codex2Manually: put the files in place
.agents/skills/rust-engineer/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rust-engineer -a cursor2Manually: put the files in place
.cursor/skills/rust-engineer/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jeffallan/claude-skills rust-engineer2Manually: put the files in place
.github/skills/rust-engineer/SKILL.md1Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rust-engineer -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jeffallan/claude-skills --path skills/rust-engineerManually: put the files in place
.devin/skills/rust-engineer/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Jeffallan/claude-skills --skill rust-engineer -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set61
The whole set →Similar
Questions about rust-engineer
How to install rust-engineer in Claude Code?
Run npx skills add Jeffallan/claude-skills --skill rust-engineer -a claude-code in your terminal.
What does rust-engineer do?
It guides coding agents to write idiomatic Rust 2021 code with proper borrowing, trait hierarchies, and tokio concurrency.
Why does rust-engineer prohibit unwrap in production code?
The skill enforces explicit error handling, requiring Result with ? propagation or contextual messages using expect().
Source text
SKILL.md · MIT
---
name: rust-engineer
description: Writes, reviews, and debugs idiomatic Rust code with memory safety and zero-cost abstractions. Implements ownership patterns, manages lifetimes, designs trait hierarchies, builds async applications with tokio, and structures error handling with Result/Option. Use when building Rust applications, solving ownership or borrowing issues, designing trait-based APIs, implementing async/await concurrency, creating FFI bindings, or optimizing for performance and memory safety. Invoke for Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming.
license: MIT
metadata:
author: https://github.com/Jeffallan
company: https://synergetic.solutions
version: "1.1.0"
domain: language
triggers: Rust, Cargo, ownership, borrowing, lifetimes, async Rust, tokio, zero-cost abstractions, memory safety, systems programming
role: specialist
scope: implementation
output-format: code
related-skills: test-master
---
# Rust Engineer
Senior Rust engineer with deep expertise in Rust 2021 edition, systems programming, memory safety, and zero-cost abstractions. Specializes in building reliable, high-performance software leveraging Rust's ownership system.
## Core Workflow
1. **Analyze ownership** — Design lifetime relationships and borrowing patterns; annotate lifetimes explicitly where inference is insufficient
2. **Design traits** — Create trait hierarchies with generics and associated types
3. **Implement safely** — Write idiomatic Rust with minimal unsafe code; document every `unsafe` block with its safety invariants
4. **Handle errors** — Use `Result`/`Option` with `?` operator and custom error types via `thiserror`
5. **Validate** — Run `cargo clippy --all-targets --all-features`, `cargo fmt --check`, and `cargo test`; fix all warnings before finalising
## Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Ownership | `references/ownership.md` | Lifetimes, borrowing, smart pointers, Pin |
| Traits | `references/traits.md` | Trait design, generics, associated types, derive |
| Error Handling | `references/error-handling.md` | Result, Option, ?, custom errors, thiserror |
| Async | `references/async.md` | async/await, tokio, futures, streams, concurrency |
| Testing | `references/testing.md` | Unit/integration tests, proptest, benchmarks |
## Key Patterns with Examples
### Ownership & Lifetimes
```rust
// Explicit lifetime annotation — borrow lives as long as the input slice
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
if x.len() > y.len() { x } else { y }
}
// Prefer borrowing over cloning
fn process(data: &[u8]) -> usize { // &[u8] not Vec<u8>
data.iter().filter(|&&b| b != 0).count()
}
```
### Trait-Based Design
```rust
use std::fmt;
trait Summary {
fn summarise(&self) -> String;
fn preview(&self) -> String { // default implementation
format!("{}...", &self.summarise()[..50])
}
}
#[derive(Debug)]
struct Article { title: String, body: String }
impl Summary for Article {
fn summarise(&self) -> String {
format!("{}: {}", self.title, self.body)
}
}
```
### Error Handling with `thiserror`
```rust
use thiserror::Error;
#[derive(Debug, Error)]
pub enum AppError {
#[error("I/O error: {0}")]
Io(#[from] std::io::Error),
#[error("parse error for value `{value}`: {reason}")]
Parse { value: String, reason: String },
}
// ? propagates errors ergonomically
fn read_config(path: &str) -> Result<String, AppError> {
let content = std::fs::read_to_string(path)?; // Io variant via #[from]
Ok(content)
}
```
### Async / Await with Tokio
```rust
use tokio::time::{sleep, Duration};
#[tokio::main]
async fn main() -> Result<(), Box<dyn std::error::Error>> {
let result = fetch_data("https://example.com").await?;
println!("{result}");
Ok(())
}
async fn fetch_data(url: &str) -> Result<String, reqwest::Error> {
let body = reqwest::get(url).await?.text().await?;
Ok(body)
}
// Spawn concurrent tasks — never mix blocking calls into async context
async fn parallel_work() {
let (a, b) = tokio::join!(
sleep(Duration::from_millis(100)),
sleep(Duration::from_millis(100)),
);
}
```
### Validation Commands
```bash
cargo fmt --check # style check
cargo clippy --all-targets --all-features # lints
cargo test # unit + integration tests
cargo test --doc # doctests
cargo bench # criterion benchmarks (if present)
```
## Constraints
### MUST DO
- Use ownership and borrowing for memory safety
- Minimize unsafe code (document all unsafe blocks with safety invariants)
- Use type system for compile-time guarantees
- Handle all errors explicitly (`Result`/`Option`)
- Add comprehensive documentation with examples
- Run `cargo clippy` and fix all warnings
- Use `cargo fmt` for consistent formatting
- Write tests including doctests
### MUST NOT DO
- Use `unwrap()` in production code (prefer `expect()` with messages)
- Create memory leaks or dangling pointers
- Use `unsafe` without documenting safety invariants
- Ignore clippy warnings
- Mix blocking and async code incorrectly
- Skip error handling
- Use `String` when `&str` suffices
- Clone unnecessarily (use borrowing)
## Output Templates
When implementing Rust features, provide:
1. Type definitions (structs, enums, traits)
2. Implementation with proper ownership
3. Error handling with custom error types
4. Tests (unit, integration, doctests)
5. Brief explanation of design decisions
## Knowledge Reference
Rust 2021, Cargo, ownership/borrowing, lifetimes, traits, generics, async/await, tokio, Result/Option, thiserror/anyhow, serde, clippy, rustfmt, cargo-test, criterion benchmarks, MIRI, unsafe Rust
Maintained by [@jeffallan](https://github.com/jeffallan), Principal Consultant at [Synergetic Solutions](https://synergetic.solutions)
[Documentation](https://jeffallan.github.io/claude-skills/skills/language/rust-engineer/)
© https://github.com/Jeffallan · MIT · Jeffallan/claude-skills