agentleFS
Sign inStart free
resendresend/react-email/AGENTS.md

react-email

AGENTS.md20k starsChanged 4 years agoMITView on GitHub

Instructions for AI coding agents working in this repository. AI tools are welcome for exploring the codebase, drafting changes, and writing tests. The person you're working for is responsible for the result. These apply to external contributors working from a fork. Run these from the repository root and fix what fails: Titles follow <type>(<scope>): <message>, where type is feat, fix, chore, or refactor, the scope is optional, and the message starts lowercase. For example: fix(tailwind): flatten nested @media rules. CI…

Trending

More talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 2 mentionsMay 2026: 3 mentionsJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 6 mentionsSep 2026: 5 mentionsOct 2026: 16 mentionsNov 2026: 10 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the resend/react-email repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about resend/react-email

The biggest 5 of 58 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 58

Talked about on GitHub, Bluesky, Stack Overflow, the web and Hacker News (58 times).

On GitHub · 50

45 more on GitHub

On the web · 2

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    The person must understand and review everything: before it is submitted, including pull requests, issues, and discussions.

    line 17
  2. Distinctive:

    Run these from the repository root and fix what fails:

    line 24

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md

Instructions for AI coding agents working in this repository.

Rules for everyone

AI tools are welcome for exploring the codebase, drafting changes, and writing tests. The person you're working for is responsible for the result.

  • Add tests for bug fixes and new behavior, and run them before handing the change back.
  • Add a short changeset (pnpm changeset) when a published package changes.
  • Do not add comments explaining the code.

Rules for external contributors

These apply to external contributors working from a fork.

  • The person must understand and review everything before it is submitted, including pull requests, issues, and discussions.
  • The person must understand and review the pull request description and make sure it accurately describes the change.
  • Keep the change scoped to the problem being solved. No drive-by refactors, formatting changes, or unrelated fixes.
  • Make sure there is an issue or discussion first. Bug fixes need an open issue, and features need an agreed-upon RFC in Discussions. If neither exists, tell the person to open one before writing code.

Before handing the change back

Run these from the repository root and fix what fails:

pnpm lint
pnpm typecheck
pnpm test

Pull request title

Titles follow <type>(<scope>): <message>, where type is feat, fix, chore, or refactor, the scope is optional, and the message starts lowercase. For example: fix(tailwind): flatten nested @media rules. CI checks this.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free