Skip to content

Awesome lists, distilled.

An agentic take on awesome lists (such as awesome-dotnet and awesome-rust):
distilled, opinionated guidance, thanks to awesome humans.

This project documents current best practice in code and updates it as ecosystems evolve. Opinions come from awesome humans: people and publications with at least two years of accurate, independent writing on the subject.

Every opinion states its recommendation first, cites its sources, and targets the latest released versions.

Agents: Fetch /llms.txt and every file it links as raw text. It links every ecosystem's opinions, templates, and skills.

Ecosystems

Each ecosystem includes:

  • Awesome humans: The roster of sources that the opinions cite.
  • Opinions: One topic per page, with its recommendation, rationale, and sources.
  • Templates: Files that encode the opinions.
  • Skills: Agent skills that check a project against the opinions and keep the opinions current.

Usage

  • Point your agent at it. Tell your coding agent to follow the opinions when it writes code. Each prompt asks for raw text, because an agent's fetch tool otherwise gives it a summary of the rules:

    Fetch awesome-humans.net/llms.txt and every file it links as raw text, then follow its conventions when writing code
    

    The agent picks the ecosystem from your project's files, such as Cargo.toml or a .csproj. For an empty project, name the ecosystem in the prompt, such as when writing Rust code.

  • Check an existing project. Ask your coding agent to run review-project, for .NET or Rust:

    Fetch awesome-humans.net/llms.txt and every file it links as raw text, then use its review-project skill on <repository>
    

    To narrow the review, say what to include or leave out, and optionally name a house profile:

    Fetch awesome-humans.net/llms.txt and every file it links as raw text, then use its review-project skill on <repository>, focus on logging and testing, skip CI, use the simon-mckenna house profile
    
  • Research a topic. Ask your coding agent to run research-topic, for .NET or Rust, which answers from the opinions and the vetted sources, citing each claim:

    Fetch awesome-humans.net/llms.txt and every file it links as raw text, then use its research-topic skill to research how to pin dependency versions
    
  • Read the opinions and templates. Each opinion gives its recommendation, rationale, and sources. The .NET templates and Rust templates encode them.

To understand how sources are vetted and how opinions stay current, see How it works.

Acknowledgement

Agents build and maintain this project, so the usual disclaimers apply, but it wouldn't exist without the people whose writing it draws on. Every opinion cites their work. Thank you to all of these awesome humans, and to everyone who supports them.

Want in or out?

  • Suggest a source. Know a person or publication with at least two years of accurate, independent writing about an ecosystem we cover? Suggest them for vetting. Every new source goes through the same admission criteria, and the decision log records every outcome.
  • Improve an opinion. Challenge or correct one, propose a new one, or fix a template, a skill, or the site. Want in says which repository it goes to, and whether to start with an issue or a pull request.
  • Opt out. If you're a listed source and don't want your work cited, ask to opt out, or email contact@awesome-humans.net if you'd rather not ask in public. Once the maintainer verifies that you control the source, we remove citations of your work within 30 days.

For how we handle each of these, see Want in or out?