Readme Curation.instructions

---
applyTo: "README.md"
---

# Curating the main list (README.md)

`README.md` is the index and the primary awesome list. Edits here should be
careful and minimal.

## Structure and ordering

- Keep the existing section order and headings. Do not introduce, rename, or
  reorder categories as part of adding an entry.
- Place each new entry in the single best-fit existing category.
- Add entries to the **bottom** of a category, unless that section is alphabetised
  or otherwise ordered — then follow the existing order.
- Match the link style of the surrounding section. Some lists use a hyphen
  (`[name](link) - Description.`) and others an em dash (`—`); follow the local
  convention rather than imposing one.

## Descriptions

- Keep them short, neutral, and factual — a plain statement of what the resource
  is, not a marketing tagline.
- Start with a capital letter and end with a full stop.
- Do not begin with "A" or "An", and do not use title-case.
- Avoid time-sensitive wording ("new", "latest", "now supports"). The dated
  Announcements table is the only place for time-stamped entries.

## Links

- HTTPS only.
- Prefer the canonical source: the project's GitHub repository, official
  documentation, or the primary paper — not a marketing site, mirror, or
  package-registry page.

## Before adding

- Confirm the resource is relevant to prompt engineering, context engineering, or
  AI agents.
- Search the whole repository for the URL and the name first — duplicates are the
  most common problem.
- If it resembles an existing entry, only suggest it if it is demonstrably better,
  and say why.

## Protected areas — do not edit casually

Badges, the Announcements table, contributor tables, and anything between
`<!-- ALL-CONTRIBUTORS-LIST:START -->` and `<!-- ALL-CONTRIBUTORS-LIST:END -->`.
Leave these unless the maintainer explicitly asks.