agentleFS
zackleconzacklecon/claude-skills/skills/rust-engineer/SKILL.md

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

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.
  • belokonmSkill

    fintech-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

  • belokonmSkill

    react-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

  • nilecuiSkill

    ui-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

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
  1. Distinctive:

    Design traits: - Create trait hierarchies with generics and associated types

    line 36
  2. Distinctive:

    Implement safely: - Write idiomatic Rust with minimal unsafe code

    line 37
  3. Distinctive:

    Handle errors: - Use Result/Option with ?

    line 38
  4. Common:

    Use ownership and borrowing for memory safety

    line 56
  5. Common:

    Use type system for compile-time guarantees

    line 58
  6. Common:

    Add comprehensive documentation with examples

    line 60
  7. Common:

    Run clippy and fix all warnings

    line 61
  8. Distinctive:

    Use cargo fmt for consistent formatting

    line 62
  9. Common:

    Write tests including doctests

    line 63
  10. Common:

    Use unwrap() in production code (prefer expect() with messages)

    line 66
  11. Common:

    Create memory leaks or dangling pointers

    line 67
  12. Common:

    Use unsafe without documenting safety invariants

    line 68
  13. Distinctive:

    Use String when &str suffices

    line 72
  14. Common:

    When implementing Rust features, provide:

    line 77

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

  1. Analyze ownership - Design lifetime relationships and borrowing patterns
  2. Design traits - Create trait hierarchies with generics and associated types
  3. Implement safely - Write idiomatic Rust with minimal unsafe code
  4. Handle errors - Use Result/Option with ? operator and custom error types
  5. Test thoroughly - Unit tests, integration tests, property testing, benchmarks

Reference Guide

Load detailed guidance based on context:

TopicReferenceLoad When
Ownershipreferences/ownership.mdLifetimes, borrowing, smart pointers, Pin
Traitsreferences/traits.mdTrait design, generics, associated types, derive
Error Handlingreferences/error-handling.mdResult, Option, ?, custom errors, thiserror
Asyncreferences/async.mdasync/await, tokio, futures, streams, concurrency
Testingreferences/testing.mdUnit/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:

  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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.