aif-best-practices

Name: aif-best-practices
Availability: InStock
Author: vanyastaff

Enforces Rust coding standards for Nebula's error handling and naming conventions.

2|Updated May 26, 2025

Search Tags:#code quality #best practices #error handling #coding standards #rust #naming conventions

Ready to run

npx skills add https://github.com/vanyastaff/nebula --skill aif-best-practices-vanyastaff

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: aif-best-practices
Source: https://github.com/vanyastaff/nebula/tree/main/.ai-factory/skill-context/aif-best-practices
Command: npx skills add https://github.com/vanyastaff/nebula --skill aif-best-practices-vanyastaff

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces consistent and high-quality Rust coding practices across the Nebula project, preventing common errors and improving maintainability.

Core Features & Use Cases

Rust Error Handling: Ensures proper use of thiserror, #[non_exhaustive], and error propagation.
Naming Conventions: Enforces kebab-case for crates and dot.notation.lowercase for action keys.
Code Structure: Promotes modularity with pub mod prelude and limits function length.
Use Case: Automatically checks new Rust code contributions against these established project rules, ensuring all developers adhere to the same high standards for error handling, naming, and code organization.

Quick Start

Apply the aif-best-practices skill to review the current Rust code for adherence to project conventions.

Frequently Asked Questions about aif-best-practices

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

FAQPage Schema

How do I enforce Rust coding standards for error handling and naming conventions?▼

You can enforce Rust coding standards by validating error handling patterns with `thiserror`, checking `#[non_exhaustive]` attributes, and verifying `kebab-case` crate naming to ensure codebase consistency.

What is the best way to check Rust code for proper thiserror and non_exhaustive usage?▼

The best way to check Rust code for proper thiserror usage is to validate error propagation patterns and ensure `#[non_exhaustive]` attributes are applied to prevent breaking changes across the codebase.

How do I validate crate naming conventions and module structure in a Rust project?▼

Validate crate naming conventions by enforcing `kebab-case` for crates and `dot.notation.lowercase` for action keys, while promoting modular code structure using `pub mod prelude` and limiting function length.

Does this Rust code review approach work for checking action keys and prelude modules?▼

Yes, this Rust code review approach works by validating `dot.notation.lowercase` for action keys and ensuring modularity through `pub mod prelude`, maintaining high code quality and organization.

When do I need to enforce Rust error handling patterns and coding standards?▼

You need to enforce Rust error handling patterns and coding standards when reviewing new code contributions, ensuring all developers adhere to the same high standards for error handling, naming, and code organization.