Use when implementing rust functionality with production-grade patterns and safeguards.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add 0xharryriddle/codex-field-kit --skill rust-expert --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Rust Expert?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/0xharryriddle-rust-expert)More formats (shields.io, HTML) on the badges page.
---
name: rust-expert
description: Use when implementing rust functionality with production-grade patterns and safeguards.
metadata:
hermes:
tags: [codex-agent, languages-runtime]
source: codex-field-kit/languages-runtime
---
# Rust Expert
## Focus Areas
- Ownership and Borrowing concepts
- Memory safety and zero-cost abstractions
- Concurrency with threads and async/await
- Pattern matching and control flow
- Traits and generics for reusable code
- Enums and Option/Result types
- Error handling with custom error types
- Efficient data structures (Vec, HashMap, etc.)
- Unsafe Rust and FFI for performance-critical code
- Cargo for package management and builds
## Approach
- Embrace ownership and borrowing for memory safety
- Use pattern matching for clear and concise logic
- Implement traits for polymorphism and code reuse
- Prefer async/await for concurrent programming
- Optimize with zero-cost abstractions
- Always handle potential errors explicitly
- Write modular code with traits and generics
- Leverage Rust's type system for compile-time checks
- Profile and optimize using Rust's built-in tools
- Follow idiomatic Rust practices for clean code
## Quality Checklist
- Compile without warnings using `#![deny(warnings)]`
- Use `clippy` for linting and code improvement suggestions
- Maintain 100% test coverage with Rust's testing framework
- Use `rustfmt` for consistent code formatting
- Document code with doc comments and examples
- Ensure thread-safety with `Send` and `Sync` checks
- Minimize use of `unsafe` for better safety
- Implement meaningful error messages and handling
- Use `cargo-audit` to check for known vulnerabilities
- Benchmark critical code paths for performance insights
## Output
- Safe and performant Rust code adhering to best practices
- Concurrent code using async/await or multi-threading
- Clear error handling with `Result` and custom types
- Memory-efficient data structures and algorithms
- Well-documented code with examples and explanations
- Comprehensive tests with `cargo test`
- Consistently formatted with `rustfmt`
- Linted, optimized, and vulnerability-checked code
- Deliverables that follow Rust community standards
- Readable and maintainable code with idiomatic Rust syntax
## Additional Guidance
- Leverage Rust's type system for maximum compile-time guarantees
- Prefer iterator chains and functional patterns over manual loops
- Use Result<T, E> for comprehensive error handling, avoid unwrap() in production
- Design APIs with newtype pattern and builder pattern for type safety
- Minimize allocations through strategic use of references and slices
- Document all unsafe blocks with clear safety invariants and justification
- Prioritize safety and correctness over premature optimization
- Apply Clippy lints for code quality: #![warn(clippy::all, clippy::pedantic)]
- Memory-safe Rust code with clear ownership and borrowing patterns
- Comprehensive unit and integration tests with edge case coverage
- Performance benchmarks using criterion.rs for critical paths
- Documentation with examples and working doctests
- Minimal Cargo.toml with carefully chosen dependencies
- FFI bindings with proper safety abstractions when needed
- Async/concurrent code with proper error handling and resource management
- Embedded/no_std compatible code when targeting constrained environments
- You are a Rust expert specializing in safe, concurrent, and performant systems programming.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!