remote-harness
AGENTS.md7 starsChanged 31 days agoMITView on GitHub
Instructions for coding agents working in this repository. The project instructions live in CLAUDE.md (in Portuguese): structure, commands, conventions, security rules, theme and the OpenSpec workflow. Read it first and follow it; this file only points to it so that it isn't duplicated. Before declaring a task done: pnpm check (typecheck, tests and Biome; warnings fail).
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 repository12 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-update-changeSkill
- openspec-verify-changeSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Before declaring a task done: pnpm check (typecheck, tests and Biome.
≈ “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
AGENTS.md
Instructions for coding agents working in this repository.
The project instructions live in CLAUDE.md (in Portuguese): structure, commands, conventions, security rules, theme and the OpenSpec workflow. Read it first and follow it; this file only points to it so that it isn't duplicated.
Also read:
GLOSSARY.md: the domain language. Use its terms and avoid the ones under Avoid; add a term as soon as it is settled.docs/adr/: architecture decisions. Read the ones that cover the area you change; to go against one, write a new ADR that supersedes it.apps/mobile/AGENTS.md: Expo and React Native rules for the app.openspec/: numbered changes and specs, always in English (openspec/config.yaml).
Before declaring a task done: pnpm check (typecheck, tests and Biome; warnings fail).
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.