QuayMesh
AGENTS.md1 starsChanged 31 days agoMITView on GitHub
Read CONTRIBUTING.md and the code involved in the requested change. Node lifecycle and installation belong in node/. Core operations belong in src/. Browser interfaces belong in src/ui/, and Windows applications belong in apps/. Retain node, workspace, task, and operation IDs across asynchronous work. Use standard JSON/YAML parsers and existing project libraries. Store credentials in local configuration or process environments. Keep public examples independent of a developer's machine. Use pnpm typecheck, pnpm build, and the tests relevant to the changed module.…
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.
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Read CONTRIBUTING.md and the code involved in the requested change.
- Very specific: line 17
Use pnpm typecheck, pnpm build, and the tests relevant to the changed module.
- Distinctive: line 23
Keep English and Simplified Chinese user guides consistent.
≈ “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
Development notes
Read CONTRIBUTING.md and the code involved in the requested change.
Structure
Node lifecycle and installation belong in node/. Core operations belong in src/. Browser interfaces belong in src/ui/, and Windows applications belong in apps/.
Implementation
Retain node, workspace, task, and operation IDs across asynchronous work. Use standard JSON/YAML parsers and existing project libraries.
Store credentials in local configuration or process environments. Keep public examples independent of a developer's machine.
Checks
Use pnpm typecheck, pnpm build, and the tests relevant to the changed module. Integration work uses real temporary files, databases, processes, and local connections.
Inspect rendered interface changes. Close development processes and remove temporary build inputs after the work is complete.
Documentation
Keep English and Simplified Chinese user guides consistent. Describe supported behavior directly, with examples drawn from public configuration.
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.