rust-code-style

Enforce Rust code style for the ai-editor project.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/brian861105/codex-skills --skill rust-code-style
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-code-style
Source: https://github.com/brian861105/codex-skills/tree/main/rust-code-style
Command: npx skills add https://github.com/brian861105/codex-skills --skill rust-code-style

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces consistent Rust code style across the ai-editor project to improve readability, maintainability, and code quality.

Core Features & Use Cases

  • Documentation standards: module-level docs and public function docs to clarify purpose and usage.
  • Code organization and naming: standardized module structure, naming conventions, and patterns for tests, errors, async/concurrency, and performance.
  • Testing and quality control: guidance on test structure, coverage expectations, and representative examples to illustrate best practices.

Quick Start

Follow this style guide when writing or reviewing Rust code for the ai-editor project.

Frequently Asked Questions about rust-code-style

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

FAQPage Schema
How do I enforce Rust code style for module documentation and naming conventions?

Enforce Rust code style by applying module-level and public function documentation standards alongside consistent naming conventions to clarify purpose and improve project maintainability.

What is the best way to structure tests and handle async concurrency in Rust projects?

Structure tests and handle async concurrency in Rust by following standardized patterns for test scaffolding, error handling, and performance to ensure consistent code quality.

Does this Rust code style guide apply to code reviews and refactoring tasks?

This Rust code style guide applies directly to new module additions, code reviews, and refactoring tasks to enforce consistency and maintainability across the project.

How do I document public functions in Rust to meet standard code style guidelines?

Document public functions in Rust by writing module-level docs and public function docs that clarify purpose and usage, satisfying standard code style guidelines for the project.

What testing standards should I follow when writing Rust code for the ai-editor project?

Follow testing standards that provide guidance on test structure, coverage expectations, and representative examples to illustrate best practices for the ai-editor project.