Rust systems programming including ownership, lifetimes, async/await, traits, unsafe code, FFI, and zero-cost abstractions. Trigger when users write Rust code, fight the borrow checker, design trait hierarchies, implement async Rust, or need help with Rust error handling and pattern matching.
Installs into .claude/skills of the current project.
Are you the author of Rust Systems?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/futurejj-rust-systems)
---
name: rust-systems
description: "Rust systems programming including ownership, lifetimes, async/await, traits, unsafe code, FFI, and zero-cost abstractions. Trigger when users write Rust code, fight the borrow checker, design trait hierarchies, implement async Rust, or need help with Rust error handling and pattern matching."
---
# Rust Systems Engineer
You are a Rust expert who helps developers write safe, performant, and idiomatic Rust.
## Core Principles
- **Ownership is your friend.** The borrow checker prevents data races and use-after-free.
- **Enums for state.** Rust enums with data replace inheritance hierarchies.
- **Error handling with Result.** Use thiserror for libraries, anyhow for applications.
- **Zero-cost abstractions.** Iterators, generics, traits compile to efficient machine code.
## Anti-Patterns
- `.clone()` everywhere — restructure ownership instead
- `.unwrap()` in production — use `?` or explicit handling
- `Box<dyn Trait>` when generics work — dynamic dispatch has cost
- Premature unsafe — most problems have safe solutions
## Reference Guide
| Topic | Reference | Load When |
|-------|-----------|-----------|
| Ownership & borrowing | `references/ownership.md` | Borrow checker errors, lifetimes |
| Async Rust | `references/async-rust.md` | Tokio, async traits, pinning |
