Awesome Reviewers expert instructions

404 — nothing is published here

Nothing is published at this path. Every path this site serves is listed in one of the indexes below, so a client that guessed a slug can look up the real one rather than crawling.

Where to look next

  • Home — search the whole corpus by title, repository, topic or language.
  • Domains — every instruction grouped by the kind of system it came out of.
  • Awesome Reviewers API — the endpoints, the error format and the markdown variants.
  • /openapi.json — OpenAPI 3.1 description of those endpoints.
  • /raw/index.json — every instruction with its slug and raw URL.
  • /llms.txt — the same corpus, domain-grouped, as plain text.
  • /sitemap.xml — every HTML page on the site.

The same thing, as markdown

# 404 Not Found

Nothing is published at this path on Awesome Reviewers.

## Recover

- Corpus index: https://awesomereviewers.com/raw/index.json — every slug, with its raw markdown URL
- LLM index: https://awesomereviewers.com/llms.txt — the whole corpus, domain-grouped
- API description: https://awesomereviewers.com/openapi.json — OpenAPI 3.1
- API documentation: https://awesomereviewers.com/api/
- Sitemap: https://awesomereviewers.com/sitemap.xml

## Common mistakes

- An instruction is `/reviewers/<slug>/` as a page and `/raw/<slug>.md` as markdown.
- A domain is `/domains/<domain>/` as a page and `/raw/bundles/<domain>.md` as markdown.
- Slugs are lowercase and hyphenated, and only the ones in `/raw/index.json` exist.

The same thing, as JSON

RFC 9457 problem details, documented at /api/#errors.

{
  "type": "https://awesomereviewers.com/api/#error-not-found",
  "title": "Resource not found",
  "status": 404,
  "detail": "Nothing is published at this path.",
  "code": "not_found",
  "resolution": "Every published path is listed in https://awesomereviewers.com/raw/index.json and https://awesomereviewers.com/llms.txt. Look the slug up there and retry."
}