3개의 표준 Agent Skills와 코딩을 가르치는 lints config 작성, 검토, 포트 및 집행 관용 Rust에 에이전트:

• **rust-best-practices ** 에이전트가 쓰거나 Rust를 변경할 때마다 로드, steers it 관대, 견고한 유지 가능한 코드로.
• rust-review 기존 Rust 코드, 파일, 크레이트, 또는 디프를 검토하고, 쓰기 모든 발견이 규칙을 깨우고 수정을 보여줍니다.
• rust-port 포트 C, C++, Python, Go, 또는 동일하게 관용 Rust에 대한 JavaScript 행동, 원래 테스트를 먼저 포팅하여 두 경기를 증명할 수 있습니다.
• **lints/**는 기계 검사 규칙을 시행하는 drop-in clippy 구성입니다. CI 소개

Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI 및 기타 모든 작업을 수행합니다. Agent Skills 형식을 읽는 대리인. 기술에서 모든 코드 예는 위에 컴파일 안정되어 있는 녹 및 config에 있는 각 lint는 현재 clippy에 대하여 검사되었습니다.

지도는 5개의 근원에서 증류됩니다, 각 묶음의 응축한 소화로 기술 그래서 대리인은 그것을 필요로 할 때 본래 이유를 상담할 수 있습니다:

• Google Rust 스타일 가이드

Beautiful Rust

Three standard Agent Skills and a lints config that teach coding agents to write, review, port, and enforce idiomatic Rust:

• rust-best-practices loads whenever an agent writes or changes Rust, and steers it toward idiomatic, robust, maintainable code.
• rust-review reviews existing Rust code, a file, a crate, or a diff, and writes a prioritized report where every finding cites the rule it breaks and shows the fix.
• rust-port ports C, C++, Python, Go, or JavaScript to idiomatic Rust with the same behavior, porting the original tests first so you can prove the two match.
• lints/ is a drop-in clippy configuration that enforces the machine-checkable rules in CI.

They work with Claude Code, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, and any other agent that reads the Agent Skills format. Every code example in the skills compiles on stable Rust, and every lint in the config was checked against current clippy.

The guidance is distilled from five sources, with a condensed digest of each bundled in the skill so the agent can consult the original reasoning when it needs to:

• Google Rust Style Guide
• Rust API Guidelines (official rust-lang checklist)
• Effective Rust by David Drysdale
• Rust Design Patterns (idioms, patterns, anti-patterns)
• Microsoft Pragmatic Rust Guidelines

Where the sources disagree, the skill picks a side and says why.

What it changes

Asked for a small semver-parsing library, an agent without the skill produced working code with public fields, no # Errors docs, and unwrap() in its doc examples. With the skill, the same agent kept the fields private, documented failure modes, and wrote doc examples users can copy safely. Condensed from those two runs:

// Without the skill
/// A semantic version. The fields are public for convenience.
pub struct Version {
    pub major: u64,
    pub minor: u64,
    pub patch: u64,
    pub pre: Vec,
    pub build: Vec,
}

impl Version {
    /// Parses a version string.
    ///
    /// ```
    /// let v = Version::parse("1.2.3").unwrap();
    /// ```
    pub fn parse(s: &str) -> Result { /* ... */ }
}

// With the skill
/// A semantic version. Equality, hashing, and ordering ignore build metadata.
pub struct Version {
    major: u64,
    minor: u64,
    patch: u64,
    pre: Vec,
    build: Vec,
}

impl Version {