- Home
- Skills
- Vudovn
- Antigravity Kit
- Rust Pro
rust-pro_skill
- TypeScript
5.7k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 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 vudovn/antigravity-kit --skill rust-pro- SKILL.md7.4 KB
Overview
This skill helps you master Rust 1.75+ for building production-ready systems, services, and libraries using modern async patterns and advanced type-system features. It focuses on performance, memory safety, and practical application of the Tokio ecosystem, axum, and other cutting-edge crates. Use it proactively for design, implementation, testing, and optimization of Rust systems.
How this skill works
I analyze requirements and constraints (performance, safety, runtime) and recommend a runtime and crate ecosystem tailored to the problem. I design type-safe APIs, implement efficient algorithms with zero-cost abstractions, and produce comprehensive tests, benchmarks, and linting guidance. I also provide profiling strategies, unsafe-code safety invariants, and concrete optimization steps for hotspots.
When to use it
- Building high-performance network services, daemons, or system tooling in Rust
- Designing or refactoring async architectures with Tokio, async/await, and streams
- Solving ownership, lifetime, or complex generic/type-system issues
- Optimizing memory layout, binary size, or hot paths for throughput/latency
- Implementing safe FFI bindings or audited unsafe abstractions
Best practices
- Start by clarifying latency, throughput, memory, and fault-tolerance constraints
- Choose a runtime (Tokio vs. async-std) and crates (axum, sqlx, tonic) up front
- Favor compile-time safety: leverage traits, GATs, and phantom types to encode invariants
- Write unit, integration, and property-based tests; add benchmarks and CI checks
- Profile with perf/cargo-flamegraph and iterate on hottest call paths
- Document safety invariants for any unsafe blocks and minimize unsafe surface area
Example use cases
- Design an async web service with axum, sqlx connection pooling, and graceful shutdown
- Refactor a CPU-bound algorithm to use SIMD and memory-layout improvements
- Wrap a C library with safe FFI, automated bindings, and lifetime guarantees
- Implement a lock-free concurrent queue with atomic invariants and tests
- Tune an existing Tokio-based pipeline for backpressure and reduced latency
FAQ
Yes. I evaluate workload characteristics (IO-bound vs CPU-bound), required ecosystem crates, and platform constraints to recommend Tokio or alternatives, explaining trade-offs like feature set, ecosystem maturity, and runtime footprint.
How do you ensure unsafe code stays safe?
I minimize unsafe usage, encapsulate it behind safe APIs, document invariants precisely, add focused unit and fuzz tests, and suggest audit steps and formal checks where appropriate.