Skip to content

Awesome Humans of Rust

An agentic take on awesome-rust: distilled, opinionated guidance, thanks to awesome humans. Instead of links, it distils what proven Rust writers recommend into guidance your agent can follow, each opinion citing its sources. It documents current best practice in Rust code, and updates it as Rust evolves.

The writers are listed in AWESOME-HUMANS.md: people and publications with at least two years of accurate, independent writing on Rust.

Usage

  • Point your agent at it. Tell your coding agent to follow the opinions when it writes code:

    Follow the conventions at awesome-humans.net when writing Rust code
    

    The opinions cover conventions, project layout, language usage, and crate choices.

  • Check an existing project. Ask your coding agent to run review-project:

    Use the review-project skill at awesome-humans.net on <repository>
    

    To narrow the review, say what to include or leave out, such as "focus on testing, skip CI".

  • Start a project from the templates. Copy the files in templates/ into a new project, trimming what you don't need.

  • Read the opinions. Browse them at awesome-humans.net or on GitHub. Each page gives its recommendation, with the rationale and sources behind it.

Scope

opinions/ holds one file per topic:

  • Rust: edition 2024, the stable features that replace older idioms, the lints that enforce them, and panics

Freshness policy

Opinions target the latest stable Rust release and the latest edition, never an older toolchain. Nightly-only features appear only in "Coming next" notes. The maintenance skills move the repository to each new release.

Every resource records when it was last reviewed against its sources. AGENTS.md: Metadata defines the fields. The repository scripts enforce them.

Awesome humans

Every opinion cites a vetted source: a person, such as Ralf Jung or Alex Kladov, or a publication, such as the Rust Blog or the Rust documentation. A source is admitted on its track record: at least two years of sustained writing, with depth, accuracy, and an independent view. Videos, talks, and podcasts are out of scope for now, because an opinion cites text a reader can check. AWESOME-HUMANS.md has the roster and the criteria.

This diagram shows how a source is admitted and what its standing allows. The admission criteria in AWESOME-HUMANS.md and the vet-source skill are canonical over it.

Source standing: vet-source sorts a candidate into citable, watch list or declined, and a citable source is unmarked, Corroborate or Discovery-only

Standing can change. vet-source runs again when an admitted source goes dormant or drops in quality, and when a watch-listed source's blocker clears.

There's one citable tier. Two markings in a source's notes limit how it's cited:

  • Corroborate: A source marked **Corroborate.** is never the only citation for a claim.
  • Discovery-only: A source marked **Discovery-only.** is never cited. Cite the primary source it links to instead.

Any other limit, such as a concern about independence or an outdated back catalogue, goes in the source's notes as prose, and doesn't change its standing.

House opinions

House opinions are preferences from experience rather than from a vetted source. Each belongs to a house profile, named for the person or organisation that owns it, such as the owner's, simon-mckenna. On awesome-humans.net, every page shows sourced community practice only, until you choose a profile in the header. Agents read llms-<profile>.txt instead of llms.txt. In this repository, each house opinion is a marked block beside the sourced text it changes, and HOUSE-OPINIONS.md defines the format and records each one. Other contributors can propose sourced or experience-based opinions through the organisation's opinion pull request template.