agentleFS
chattyminchattymin/PokeTokenBar/AGENTS.md

PokeTokenBar

AGENTS.md557 starsChanged 40 days agoMITView on GitHub

Read CLAUDE.md for the repository's contribution, testing, and release instructions. When creating, preparing, or updating a PR, use .agents/skills/prepare-pr/SKILL.md. This repository's rules take precedence over a personal PR skill's default title or body format. Use an English Conventional Commits title and fill out .github/PULL_REQUEST_TEMPLATE.md with the actual changes and validation results. Mark checklist items complete only when supported by the work performed. Every PR with a visible UI change must embed images in UI changes: actual screenshots, local renders of…

  • 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,542 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read CLAUDE.md for the repository's contribution, testing, and release instructions.

    line 3
  2. Very specific:

    When creating, preparing, or updating a PR, use .agents/skills/prepare-pr/SKILL.md.

    line 7
  3. Very specific:

    Use an English Conventional Commits title and fill out .github/PULL_REQUEST_TEMPLATE.md with the actual changes and validation results.

    line 9

≈ “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

Repository instructions

Read CLAUDE.md for the repository's contribution, testing, and release instructions.

Pull requests

When creating, preparing, or updating a PR, use .agents/skills/prepare-pr/SKILL.md. This repository's rules take precedence over a personal PR skill's default title or body format.

Use an English Conventional Commits title and fill out .github/PULL_REQUEST_TEMPLATE.md with the actual changes and validation results. Mark checklist items complete only when supported by the work performed.

Every PR with a visible UI change must embed images in UI changes: actual screenshots, local renders of the production UI, or clearly labeled illustrations of the changed UI are accepted. Include before/after images for an existing screen; for a new screen, explain that no previous screen exists and include its image. Text alone does not satisfy this requirement. If images are missing, the agent must produce and attach them as part of the authorized PR work without asking the user to supply them. Try suitable generation and attachment alternatives before declaring a blocker. Keep publication pending only when a concrete failure still prevents completion, and report the attempted methods and required user action. Remove UI changes only when there is no visible UI change.

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.