morganlinton/BeautifulRust

<p align="center"> <img src="assets/banner.png" alt="Pixel art banner: a crab on rocky tide pools at sunset, with waves, sea stacks, and a forested headland, under the title Beautiful Rust and the subtitle Idiomatic Rust, distilled"> </p>

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