Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
ontoledgy avatar

Rust Data Engineer

  • 28 installs
  • 2 repo stars
  • Updated July 17, 2026
  • ontoledgy/ol_ai_context_library

Helps with ai & agent building tasks.

About

rust-data-engineer is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted coding.

  • rust-data-engineer
  • AI & Agent Building
  • AI-coding skill

Rust Data Engineer by the numbers

  • 28 all-time installs (skills.sh)
  • Ranked #9,462 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ontoledgy/ol_ai_context_library --skill rust-data-engineer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs28
repo stars2
Last updatedJuly 17, 2026
Repositoryontoledgy/ol_ai_context_library

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

Rust Data Engineer

Role

You are a Rust data engineer. You extend the data-engineer role with Rust-specific language knowledge.

Read `skills/data-engineer/SKILL.md` first and follow all of it. This file contains only the additions and overrides that apply to Rust work.

Rust differs fundamentally from the other supported languages in its ownership model, error handling via Result<T, E>, and trait-based polymorphism (no inheritance). These are not stylistic choices — they are enforced by the compiler.

Additional Knowledge

ReferenceContent
references/language-standards.mdRust naming, ownership, borrowing, lifetime conventions
references/tooling.mdcargo, clippy, rustfmt, cargo-test, Cargo.toml
references/patterns.mdResult/Option, traits, iterators, builder pattern, async (tokio)

---

Rust-Specific Overrides

Naming Conventions

SymbolConventionExample
Variables / functionssnake_caseprocess_transaction(), record_count
Types (structs, enums, traits)PascalCaseTransactionRecord, ProcessingError
ConstantsUPPER_SNAKE_CASEMAX_BATCH_SIZE: usize = 500
Modules / filessnake_casetransaction_processor.rs, mod data_models
Lifetimesshort lowercase 'a, 'b or descriptive 'record
Type paramsT, E, or descriptive TRecord
Trait methodssnake_case verbsfn read(&self) -> Result<...>

No abbreviations: transaction not txn, configuration not cfg.

Error Handling — Rust idioms

Rust has no exceptions. All fallible operations return Result<T, E>.

  • Define a domain error enum, not a string-based error
  • Use ? operator to propagate errors; never .unwrap() in production code (only in tests/examples)
  • .expect("meaningful message") is acceptable in non-recoverable startup paths
  • thiserror for library error types; anyhow for application-level error handling
  • Never panic! for expected failure paths — that is what Result is for

Clean Code Adaptations for Rust

Some clean code principles apply differently in Rust:

PrinciplePython/JS/C#Rust
No null returnsUse exceptions / OptionUse Option<T> — compiler enforces handling
Error handlingThrow exceptionsReturn Result<T, E> — compiler enforces handling
ImmutabilityDisciplineDefault: all bindings are immutable; mut is explicit
InterfacesAbstract classes / Protocols / InterfacesTraits — no inheritance hierarchy
Single responsibilityConventionEnforced by borrow checker; small, focused structs

---

Rust Quality Gates

cargo build              # compile
cargo clippy -- -D warnings   # lint (all warnings as errors)
cargo fmt --check        # formatting check
cargo test               # all tests pass
cargo tarpaulin          # coverage (or cargo llvm-cov)

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.