rust-pro_skill

This skill helps you write idiomatic Rust with ownership, async, and safe concurrency, ensuring zero-cost abstractions and robust error handling.

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill sidetoolco/org-charts --skill rust-pro

  • SKILL.md1.2 KB

Overview

This skill is a Rust expert focused on safe, idiomatic systems programming that balances memory safety and high performance. I produce code that leverages Rust ownership, lifetimes, and traits to enforce correctness at compile time while minimizing runtime overhead. Deliverables include async implementations, safe concurrency patterns, clear error handling, and tests and benchmarks.

How this skill works

I inspect code requirements and propose designs that use the type system to encode invariants, preferring zero-cost abstractions like iterators and generics. For concurrency and async, I choose appropriate runtimes and synchronization primitives (Arc, Mutex, channels) and ensure cancellation and resource cleanup. When unsafe or FFI is required, I limit unsafe blocks to minimal, well-documented sections with explicit invariants.

When to use it

  • Building high-performance services or daemons where memory safety and throughput matter
  • Designing libraries that must offer zero-cost abstractions and ergonomic APIs
  • Implementing async networking or I/O with Tokio or async-std
  • Refactoring unsafe code to reduce UB risk and document invariants
  • Adding reliable concurrency with channels, Arc, and lock strategies

Best practices

  • Encode invariants in types and use lifetimes to prevent dangling references
  • Prefer Result-based error handling and define custom error types; avoid panics in libraries
  • Use iterators, maps, and combinators instead of manual indexing loops
  • Keep unsafe blocks small, documented, and justified with comments and tests
  • Follow clippy lints, add unit/doc tests, and provide benchmarks with criterion

Example use cases

  • Designing a threaded HTTP proxy using Tokio, channels, and zero-copy buffers
  • Writing a high-throughput telemetry collector with lock-free or sharded state
  • Creating an FFI boundary to C with careful ownership transfer and tests
  • Refactoring a legacy module to remove unwraps and introduce Result propagation
  • Authoring a generic trait-based cache with feature flags and benchmarks

FAQ

I avoid unsafe where possible; when needed I constrain it to minimal blocks with explicit invariants, safety comments, and tests to validate behavior.

Which async runtime do you use?

I choose the runtime that best fits the ecosystem and performance needs—commonly Tokio for production networking or async-std for simpler tasks—and make cancellation and timeouts explicit.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
rust-pro skill by sidetoolco/org-charts | VeilStrat