Propose Rust coding patterns applying ownership, borrowing, and lifetime rules.
npx skills add https://github.com/wolram/skills --skill rust-staff-engineer
Please help me install this Agent Skill. Skill: rust-staff-engineer Source: https://github.com/wolram/skills/tree/main/rust-staff-engineer Command: npx skills add https://github.com/wolram/skills --skill rust-staff-engineer
Equip teams with a Staff-level Rust expert to design, review, and mentor for safe, idiomatic, and high-performance Rust software.
Provide a minimal Rust module scaffold demonstrating safe ownership, borrowing, and concurrency patterns.
High-intent search queries and answers about installing and using this skill.
Design Rust APIs by applying ownership, borrowing, and lifetime rules to define clear module boundaries and data flows. This approach ensures safe, idiomatic code generation with concrete, testable recommendations that follow compiler guidance.
Handling Rust ownership in service architectures requires mapping data flows across modules using strict lifetime discipline. This maximizes memory safety and performance while providing testable code examples for robust service design.
Yes, architectural code reviews for Rust evaluate module boundaries, API design, and lifetime discipline. The review provides concrete, testable recommendations and code examples that align with Rust best practices and compiler guidance.
Tune Rust performance by proposing coding patterns that leverage safe borrowing and ownership rules to optimize data flows. This yields high-performance services while strictly adhering to idiomatic Rust safety standards and compiler checks.
Explicit lifetime annotations in Rust API design are needed when passing references across module boundaries or building complex data flows. They ensure borrowing rules are satisfied, yielding safe, testable, and compiler-approved code recommendations.
KonghaYaoAnalyze module boundaries and dependencies in multi-crate Rust projects.
ahravAnalyze and optimize Rust assembly output to fix compiler inefficiencies.
farmountainEnforce Rust best practices, memory safety, and ownership patterns in code.
baekenoughEnforce idiomatic Rust patterns for ownership, borrowing, and error handling.
