Google Rust Style Guide, enforced

Try it now

Let your agent do it

Recommended

One prompt, zero config work. Your coding agent downloads the configs, turns on the lints, runs fmt, clippy and cargo-deny, and fixes your code until everything is green.

1. Copy the prompt

   Prompt

   Apply the Google Rust Style Guide kit to this repository.
   Follow the instructions at
   https://daniakash.github.io/Google-Rust-Style-Guide/_llms-txt/for-coding-agents.txt
   Then run cargo +nightly fmt, cargo clippy --workspace --all-targets -- -D warnings,
   and cargo deny check bans, and fix what they report without editing the lint configuration.

2. Paste it into your agent from your project root. Works with Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot and any agent that can run commands.

3. Review the diff. Expect new config files, lint tables in Cargo.toml, and fixes in your code. The lint configuration itself should match the downloaded files exactly.

Do it yourself

Run this in a single-crate Cargo project. It adds five files, turns on the lints, and shows you what the guide flags. Existing files are never overwritten.

Terminal

base=https://daniakash.github.io/Google-Rust-Style-Guide/files
for f in rustfmt.toml clippy.toml deny.toml rust-toolchain.toml AGENTS.md; do
  if [ -e "$f" ]; then echo "skipped $f (already exists)"; else curl -fsSLO "$base/$f"; fi
done
curl -fsSL "$base/crate-lints.toml" >> Cargo.toml   # workspaces: see the quick start
cargo clippy --all-targets

Using a workspace, or want each step explained? The quick start walks through it in four steps with the expected output.

Every rule has exactly one home

Google’s Rust style guide mixes mechanical rules with design judgment. The kit gives each rule to the cheapest layer that can hold it.

Tools enforce

rustfmt, 41 clippy and rustc lints, and cargo-deny cover 32 of 62 in-scope rules. CI blocks the merge.

Agents follow

AGENTS.md teaches Claude Code, Codex, Cursor and others the judgment rules no linter can check.

Humans review

A review guide covers what is left: API shape, ownership design and whether each exception is justified.

Exceptions are written down

Allowed deviations become #[expect(lint, reason = "...")] at the exact spot, so reviewers can judge them.

Start here

Quick startFive minutes from zero to a green cargo clippy.

CoverageEvery guide section and the check that enforces it.

AGENTS.mdThe rules your coding agent should follow.

Human review guideWhat to check once CI is green.

Unofficial

This is a community project. It is not affiliated with, endorsed by, or maintained by Google. The style guide itself is published by Google under CC-BY 3.0.