Engineering Conventions Skill (Rust Edition)

Standardize Rust project structure, dependencies, formatting, testing, and documentation conventions.

1|Updated Nov 24, 2025
One-click install
npx skills add https://github.com/YAPP-Github/27th-Web-Team-3-BE --skill engineering-conventions-skill-rust-edition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Engineering Conventions Skill (Rust Edition)
Source: https://github.com/YAPP-Github/27th-Web-Team-3-BE/tree/main/.claude/skills/engineering-conventions
Command: npx skills add https://github.com/YAPP-Github/27th-Web-Team-3-BE --skill engineering-conventions-skill-rust-edition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines and enforces Rust project engineering conventions, increasing consistency, readability, and onboarding velocity across teams.

Core Features & Use Cases

  • Project structure standards: Prescribed directory layout, module organization, and examples.
  • Dependency and tooling guidelines: Cargo.toml policies, edition, and recommended tooling (fmt, clippy, tests).
  • Code style and documentation: Rust formatting, error handling, and doc comments guidelines.
  • Use Case: Start a new Rust project using the conventions to ensure a maintainable baseline from day one.

Quick Start

Create a new Rust project and apply the conventions by aligning Cargo.toml, src structure, and formatting; run cargo fmt and cargo clippy to verify compliance.

Frequently Asked Questions about Engineering Conventions Skill (Rust Edition)

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

FAQPage Schema
What are standard Rust project conventions for structuring modules and Cargo.toml?

Standard Rust project conventions enforce a documented directory layout, module organization, and Cargo.toml policies to ensure consistency and faster onboarding across teams.

How do I set up coding style and formatting standards for a new Rust project?

To set up coding style standards for a new Rust project, apply prescribed formatting, error handling, and doc comment guidelines, then verify compliance using cargo fmt and cargo clippy.

Can I apply these Rust coding standards to existing projects or only new ones?

These Rust coding standards apply to both new and existing projects, enforcing structure, dependencies, formatting, testing, and documentation practices suitable for review and CI checks.

What's the best way to enforce Rust project standards during code review and CI?

The best way to enforce Rust project standards during CI is by applying documented module layout, Cargo.toml policies, and coding standards, then verifying them with cargo fmt and cargo clippy checks.

Do I need specific Rust tooling to maintain project conventions and documentation?

You need recommended Rust tooling like cargo fmt, cargo clippy, and testing frameworks to verify compliance with defined project conventions, formatting, and documentation practices.