agentleFS
Sign inStart free
wxxb789wxxb789/hoa/AGENTS.md

hoa

AGENTS.md2 starsChanged 50 days agoMITView on GitHub

All HTML artifacts and their related assets MUST be written to ./.tmp-artifacts/. - Scope: rendered reports, dashboards, visualizations, session/insight reports, screenshots, and any backing assets they depend on (CSS, JS, images, fonts, and JSON/data files). - Location: always under ./.tmp-artifacts/ at the repo root. Create it with mkdir -p .tmp-artifacts if it does not exist. Never scatter these files in the repo root or in source directories. - Bundle per artifact: every artifact gets its own subfolder named after it,…

  • 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,700 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 repository8 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, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    All HTML artifacts and their related assets MUST be written to ./.tmp-artifacts/.

    line 5
  2. Very specific:

    Location: always under ./.tmp-artifacts/ at the repo root.

    line 10
  3. Very specific:

    Bundle per artifact: every artifact gets its own subfolder named after it, e.g.

    line 13

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

hoa — Project Agent Instructions

Generated Artifacts Output

All HTML artifacts and their related assets MUST be written to ./.tmp-artifacts/.

  • Scope: rendered reports, dashboards, visualizations, session/insight reports, screenshots, and any backing assets they depend on (CSS, JS, images, fonts, and JSON/data files).
  • Location: always under ./.tmp-artifacts/ at the repo root. Create it with mkdir -p .tmp-artifacts if it does not exist. Never scatter these files in the repo root or in source directories.
  • Bundle per artifact: every artifact gets its own subfolder named after it, e.g. ./.tmp-artifacts/<artifact-name>/. The main file and all of its related assets (data JSON, CSS, JS, images, fonts) live together in that one subfolder so each bundle is self-contained and portable. Never drop loose files directly in ./.tmp-artifacts/ — its root holds only bundle subfolders.
  • Version control: ./.tmp-artifacts/ is git-ignored. Never commit its contents and never force-add (git add -f) files from it.

Example layout:

.tmp-artifacts/
  session-report-20260626/      # one bundle
    session-report-20260626.html
    _session-report.json
    _session_index.json
  insights-report-zh-cn/        # another bundle
    insights-report-zh-cn.md
    _insights_data.json

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