Rust Systems

What it does

This skill provides a comprehensive set of best practices and style conventions for systems programming in Rust. It contains 52 rules across five categories, designed to improve code quality, consistency, and maintainability when building performance-critical applications, command-line tools, or daemon processes. The guidelines cover project organization, module structure, naming conventions, type & trait patterns, and error handling.

When to use it

This skill is helpful in the following situations:

• Writing new Rust code or modules.
• Organizing existing Rust project structures.
• Defining custom types, traits, or error handling mechanisms.
• Reviewing Rust code for adherence to style guidelines and consistency.
• Developing systems tools, CLIs, or daemon processes.

Key capabilities

• Project Organization: Guidelines on using Cargo Workspaces, directory naming conventions (snake_case), separating binaries and libraries, feature domain grouping, common crates, and flat crate structures.
• Module Structure: Recommendations for explicit module declarations, co-locating tests, submodule organization with mod.rs, separating types and errors into dedicated files, clean API re-exports using pub use, and conditional compilation.
• Naming Conventions: Rules for function/method names (snake_case), type names (PascalCase), constants (SCREAMING_SNAKE_CASE), getter prefixes (get_), boolean predicates (is_, has_, should_), constructors (new), conversions (to_, from_), and more.
• Type & Trait Patterns: Guidance on using Option for nullable fields, consistent derive order, the builder pattern, associated types, phantom data, and newtype patterns.
• Error Handling: (Specific error handling rules are not detailed in the provided source.)

Example prompts

Here are some example prompts you could give an AI agent with this skill:

• "Check my Rust code for adherence to project organization guidelines."
• "Suggest a naming convention for this new function that calculates [specific task]."
• "How should I structure modules in my Rust library?"

Tips & gotchas

• The rules are categorized by priority (HIGH), indicating their importance. Focus on the highest-priority rules first.
• This skill provides guidelines, not automated enforcement. It's intended to be used as a reference and for manual review.