amplifier-foundation / libraries
AGENTS.md17 starsChanged 3 months agoMITView on GitHub
Read this directory's README and the affected library's README, provenance and qualification notes before changing it. Own one library directory per worktree; coordinate shared CI/release files through an integration owner. - Keep packages independently installable. Do not add them to the base Foundation wheel, root imports or required dependencies merely because their sources live here. - Keep application policy, host/client authority and native execution outside. Public mechanisms take explicit storage paths and scoped inputs from callers. - Preserve native history…
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 repository5 other files it gives its agents.
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Distinctive: line 3
Read this directory's README and the affected library's README, provenance and qualification notes before changing it.
- Distinctive: line 7
Keep packages independently installable.
- Distinctive: line 9
Keep application policy, host/client authority and native execution outside.
- Distinctive: line 16
Run the affected library's meaningful contract tests and any consumers whose public contracts changed.
≈ “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.
Files
Optional library boundaries
Read this directory's README and the affected library's README, provenance and qualification notes before changing it. Own one library directory per worktree; coordinate shared CI/release files through an integration owner.
- Keep packages independently installable. Do not add them to the base Foundation wheel, root imports or required dependencies merely because their sources live here.
- Keep application policy, host/client authority and native execution outside. Public mechanisms take explicit storage paths and scoped inputs from callers.
- Preserve native history and unknown effect receipts. Do not replay work to recover a projection or infer success from an interrupted transport.
- Build wheels and test imports in an owned installed-consumer environment. Explicitly select its Python executable for installers; never target an inherited active environment or running application's worker environment.
- Run the affected library's meaningful contract tests and any consumers whose public contracts changed. Record unverified integration/deployment boundaries.
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
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.