agentleFS
Sign inStart free
decocmsdecocms/studio/plugins/AGENTS.md

studio / plugins

AGENTS.md415 starsChanged 3 months agoMITView on GitHub

The registered rules and their configuration live in .oxlintrc.json at the repository root. Keep rule severity at error, or off with a reason. An exception at one site needs a scoped directive naming the rule and reason. Do not downgrade the rule for every caller. Every registered JS plugin must have a diagnostic-producing fixture in js-plugins-smoke.test.ts. A plugin exception can leave oxlint exiting zero, so lint success alone does not prove the plugin ran. Keep oxlint pinned exactly. After changing…

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:

    Do not downgrade the rule for every caller.

    line 6
  2. Very specific:

    Every registered JS plugin must have a diagnostic-producing fixture in js-plugins-smoke.test.ts.

    line 8
  3. Very specific:

    Keep oxlint pinned exactly.

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 36,368 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

Lint tooling

The registered rules and their configuration live in .oxlintrc.json at the repository root. Keep rule severity at error, or off with a reason. An exception at one site needs a scoped directive naming the rule and reason. Do not downgrade the rule for every caller.

Every registered JS plugin must have a diagnostic-producing fixture in js-plugins-smoke.test.ts. A plugin exception can leave oxlint exiting zero, so lint success alone does not prove the plugin ran.

Keep oxlint pinned exactly. After changing a plugin, its registration, or the oxlint version, run bun test ./plugins from the repository root. When changing React Compiler rule settings, read their existing explanations in .oxlintrc.json before changing the chosen exceptions.

Download now (ZIP)

  • Other versions2 projects use a version of this.

    Word for word · 2

    1. decocms/admin★ 409100% same
    2. decocms/mesh★ 409100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 28,693 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 repository4 other files it gives its agents.

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