Skip to content

Awesome Humans of Rust

An agentic take on awesome-rust: opinionated guidance for your coding agent, distilled from the writing of awesome humans. Instead of a list of links, it gives one recommendation per question, and each opinion cites its sources. It documents current best practice in Rust code, and changes 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.

Agents: Fetch llms.txt and every file it links as raw text. It links the opinions, templates, and skills.

Note

The Rust ecosystem is currently being bootstrapped. See Research, the research branches, and the plan. Review by 2027-01-17.

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/rust/llms.txt 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/rust/llms.txt on <repository>
    

    To narrow the review, say what to include or leave out:

    Use the review-project skill at awesome-humans.net/rust/llms.txt on <repository>, focus on panics and lints, skip the edition
    
  • Research a topic. Ask your coding agent to run research-topic, which answers from the opinions and the vetted sources, citing each claim:

    Use the research-topic skill at awesome-humans.net/rust/llms.txt to research whether to adopt cargo-nextest
    
  • Read the opinions and templates. Browse them at awesome-humans.net or on GitHub. Each opinion gives its recommendation, rationale, and sources, and the templates/ encode them.

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/metadata.md 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.

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

A house opinion is a preference from experience, not from a vetted source. Each belongs to a house profile, named for the person or organisation that owns it, such as simon-mckenna. On awesome-humans.net, every page shows only sourced community practice until you choose a profile in the header. An agent that follows a profile reads 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.