sage-rust-conventions

Enforce Rust naming, error handling, async, and testing conventions for Sage codebases.

12|1|Updated Jul 15, 2025
One-click install
npx skills add https://github.com/majiayu000/sage --skill sage-rust-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sage-rust-conventions
Source: https://github.com/majiayu000/sage/tree/main/.sage/skills/sage-rust-conventions
Command: npx skills add https://github.com/majiayu000/sage --skill sage-rust-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill codifies Rust coding conventions to improve consistency and maintainability across a Sage Rust codebase.

Core Features & Use Cases

  • Naming conventions: enforce snake_case for modules, functions, and variables; discourage nonstandard abbreviation.
  • Error handling: promote consistent error types and propagation using idiomatic Rust patterns.
  • Async & testing: provide guidelines for async functions and reliable test strategies.
  • Use case: during code reviews, apply the conventions to ensure readable, maintainable, and safe Rust code across the project.

Quick Start

Audit a Rust module by providing a file path, for example: sage/src/llm_client.rs, and apply the Sage Rust conventions described in this Skill.

Frequently Asked Questions about sage-rust-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are standard Rust naming conventions for modules and functions?

Standard Rust naming conventions enforce snake_case for modules, functions, and variables while discouraging nonstandard abbreviations to improve codebase consistency and readability.

How do I handle error propagation in Rust async functions?

Handle error propagation in Rust async functions by promoting consistent error types and using idiomatic Rust patterns to ensure maintainable and safe asynchronous execution.

How do I audit a Rust file for code convention violations?

Audit a Rust file for convention violations by providing the file path during code reviews and applying established guidelines for naming, error handling, async patterns, and testing practices.

Can I enforce Rust coding standards without external linting tools?

You can enforce Rust coding standards without external linting tools by applying documentation-style guidance and best practices during code reviews and automated checks.

What testing practices should I follow for Rust async code?

Follow testing practices for Rust async code by applying established guidelines that ensure reliable test strategies and maintainable asynchronous patterns across the project.