rust-engineer
Skill3 starsChanged 9 months agoMITView on GitHub
Use when building Rust applications requiring memory safety, systems programming, or zero-cost abstractions. Invoke for ownership patterns, lifetimes, traits, async/await with tokio.
19 other projects use a version of this, 14 of them edited.
Adopted by
Most recently taken up by
- santiago-migoni/claude-skillsedited, first seen Nov 8, 2026
- AxlZero21/Skillsedited, first seen Nov 8, 2026
- dirien/yet-another-agent-harnessedited, first seen Nov 8, 2026
- lsyamsiar/claude-skillsedited, first seen Nov 1, 2026
- codeApe-7/ai-agent-workflowGroupedited, first seen Nov 1, 2026
- hu465/claude-skills-edited, first seen Oct 25, 2026
Used with
Projects with it also use fintech-engineer, react-specialist and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
belokonmSkillfintech-engineer
Expert in financial technology systems, double-entry ledger design, high-precision math, and regulatory compliance. Use when building payment systems, ledger architectures, financial calculations, PCI compliance, or banking integrations. Triggers include "fintech", "ledger", "double-entry", "financial calculations", "PCI compliance", "banking API".
Also in 3 projects that use this
belokonmSkillreact-specialist
Expert React developer specializing in React 18+, Next.js ecosystem, and modern React patterns. This agent excels at building performant, scalable React applications using hooks, concurrent features, state management solutions like Zustand, and data fetching with TanStack Query.
Also in 3 projects that use this
nilecuiSkillui-designer
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
Also in 3 projects that use this
- +9 more from belokonm
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 14
- Jeffallan/claude-skills★ 12k40% same
- farm-fe/farm★ 5.6k42% same
- dirien/yet-another-agent-harness★ 1942% same
- codeApe-7/ai-agent-workflowGroup★ 1842% same
- PIXARTSeu/Synapse★ 942% same
- idexal/idexal-skills★ 242% same
- AxlZero21/Skills★ 140% same
- musaJawad004/heron★ 142% same
- gloomyweather/opencode-setup★ 041% same
- hu465/claude-skills-★ 040% same
4 more not listed
Wrote their own version · 5
- jshsakura/awesome-opencode-skills★ 30same name
- LazyIsEfficient/agentic-os★ 17same name
- belokonm/claude-supercode-skills★ 11same name
- nicolasestrem/antigravity-gemini-skills★ 8same name
- marttp/my_agent_skills_I_use★ 4same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository66 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- angular-architectSkill
- api-designerSkill
- architecture-designerSkill
- atlassian-mcpSkill
- chaos-engineerSkill
- cli-developerSkill
- cloud-architectSkill
- code-documenterSkill
- code-reviewerSkill
- cpp-proSkill
- csharp-developerSkill
- database-optimizerSkill
- debugging-wizardSkill
- devops-engineerSkill
- django-expertSkill
- dotnet-core-expertSkill
- embedded-systemsSkill
- fastapi-expertSkill
- feature-forgeSkill
- fine-tuning-expertSkill
- flutter-expertSkill
- fullstack-guardianSkill
- game-developerSkill
- golang-proSkill
- graphql-architectSkill
- java-architectSkill
- javascript-proSkill
- kotlin-specialistSkill
- kubernetes-specialistSkill
- laravel-specialistSkill
- legacy-modernizerSkill
- mcp-developerSkill
- microservices-architectSkill
- ml-pipelineSkill
- monitoring-expertSkill
- nestjs-expertSkill
- nextjs-developerSkill
- pandas-proSkill
- php-proSkill
- playwright-expertSkill
- postgres-proSkill
- prompt-engineerSkill
- python-proSkill
- rag-architectSkill
- rails-expertSkill
- react-expertSkill
- react-native-expertSkill
- salesforce-developerSkill
- secure-code-guardianSkill
- security-reviewerSkill
- shopify-expertSkill
- spark-engineerSkill
- spec-minerSkill
- spring-boot-engineerSkill
- sql-proSkill
- sre-engineerSkill
- swift-expertSkill
- terraform-engineerSkill
- test-masterSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 9 are common, 5 are distinctive, and 0 are very specific to this project.
9
Common
Most of the 18 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 36
Design traits: - Create trait hierarchies with generics and associated types
- Distinctive: line 37
Implement safely: - Write idiomatic Rust with minimal unsafe code
- Distinctive: line 38
Handle errors: - Use Result/Option with ?
- Common: line 56
Use ownership and borrowing for memory safety
- Common: line 58
Use type system for compile-time guarantees
- Common: line 60
Add comprehensive documentation with examples
- Common: line 61
Run clippy and fix all warnings
- Distinctive: line 62
Use cargo fmt for consistent formatting
- Common: line 63
Write tests including doctests
- Common: line 66
Use unwrap() in production code (prefer expect() with messages)
- Common: line 67
Create memory leaks or dangling pointers
- Common: line 68
Use unsafe without documenting safety invariants
- Distinctive: line 72
Use String when &str suffices
- Common: line 77
When implementing Rust features, provide:
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Role Definition
You are a senior Rust engineer with 10+ years of systems programming experience. You specialize in Rust's ownership model, async programming with tokio, trait-based design, and performance optimization. You build memory-safe, concurrent systems with zero-cost abstractions.
When to Use This Skill
- Building systems-level applications in Rust
- Implementing ownership and borrowing patterns
- Designing trait hierarchies and generic APIs
- Setting up async/await with tokio or async-std
- Optimizing for performance and memory safety
- Creating FFI bindings and unsafe abstractions
Core Workflow
- Analyze ownership - Design lifetime relationships and borrowing patterns
- Design traits - Create trait hierarchies with generics and associated types
- Implement safely - Write idiomatic Rust with minimal unsafe code
- Handle errors - Use Result/Option with ? operator and custom error types
- Test thoroughly - Unit tests, integration tests, property testing, benchmarks
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 |
Constraints
MUST DO
- Use ownership and borrowing for memory safety
- Minimize unsafe code (document all unsafe blocks)
- Use type system for compile-time guarantees
- Handle all errors explicitly (Result/Option)
- Add comprehensive documentation with examples
- Run 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:
- Type definitions (structs, enums, traits)
- Implementation with proper ownership
- Error handling with custom error types
- Tests (unit, integration, doctests)
- 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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

