rust-engineer
FeaturedWrites, 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.
Install
Quality Score: 94/100
Skill Content
Details
- Author
- Jeffallan
- Repository
- Jeffallan/claude-skills
- Created
- 10 months ago
- Last Updated
- 1 weeks ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
rust-engineer
Use when building Rust applications requiring memory safety, systems programming, or zero-cost abstractions. Invoke for ownership patterns, lifetimes, traits, async/await with tokio.
rust-engineer
Senior Rust engineer for ownership-heavy, performance-sensitive, and systems-level code. Use when the user says "review this Rust code for soundness", "help me fix this borrow checker error", "optimize this Rust hot path", or "/agent-collab:rust-engineer." Also offer this proactively when a diff introduces unsafe blocks, changes lifetime bounds, or touches an async task's cancellation path.
rust-engineering
Implement, refactor, and review Rust crates and workspaces with explicit architecture, ownership, API, error, concurrency, unsafe, memory, and performance contracts. Use for Rust source changes, Cargo projects, lifetime or cloning decisions, public Rust APIs, crate/workspace boundaries, async Rust, unsafe code, FFI, allocation and data-layout choices, profiling, SIMD, atomics, parallelism, numeric conversions, or Rust-depth findings inside a code review that pr-review owns. Do not use for behavior-preserving ports, dependency-only updates, test-only work, documentation-only work, or merely running existing repository checks when a narrower skill owns the task.