rust-style-conventions

Enforce Rust style conventions for imports, naming, and formatting.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matthewharwood/engmanager_xyz --skill rust-style-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-style-conventions
Source: https://github.com/matthewharwood/engmanager_xyz/tree/main/.claude/skills/rust-style-conventions
Command: npx skills add https://github.com/matthewharwood/engmanager_xyz --skill rust-style-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Foundational Rust style conventions applying to all Rust code, including import organization, naming, and formatting.

Core Features & Use Cases

  • Import Style: Top-level imports only, no inline paths.
  • Naming & Formatting: Standard conventions, rustfmt, line length.
  • Enforcement: Use of rustfmt and consistent usage.

Quick Start

Adopt the conventions in new Rust projects and run cargo fmt.

Frequently Asked Questions about rust-style-conventions

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

FAQPage Schema
How do I enforce Rust style conventions across my codebase?

Rust style conventions enforce consistent import organization, naming, and formatting across all code. Apply them by running cargo fmt, which automatically formats to rustfmt standards, and organize imports at the top of files in grouped sections following standard conventions.

What are the import organization rules for Rust projects?

Import organization requires all use statements at the top of files only—no inline imports. Group imports logically and follow standard naming conventions. This structure keeps dependencies visible and maintainable across your entire project.

Do I need to manually format Rust code or can rustfmt do it automatically?

Rustfmt handles automatic formatting, including line length and style rules. Run cargo fmt to apply conventions project-wide without manual intervention, ensuring consistent formatting across all Rust codebases.

What documentation is required for public Rust APIs?

Style conventions mandate documentation for public APIs and module-level docs. These requirements ensure your public interfaces are clear and discoverable, supporting maintainability and usability across projects.

Can I apply these conventions to existing Rust projects?

Yes, conventions apply automatically to all Rust codebases. Adopt them in existing projects by running cargo fmt and reorganizing imports to top-of-file style, then enforce compliance going forward.