bstack
AGENTS.md0 starsChanged 10 days agoMITView on GitHub
Start with docs/development.md for the checkout, validation and delivery gate, and the design for requirements. Read only the design sections your task lists. Set up and validate with the Node 24 command block in README.md. Iterate with npm test -- --task <id> from tests/tasks.json. Tests drive the public commands as child processes against disposable fixtures (conventions); reuse tests/scripts/discovery-fixture.ts and tests/fixtures/build.ts. Take expected results from the design, plan or acceptance case, not from the implementation; TDD is not the default (design…
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,843 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 repository17 other files it gives its agents.
- agents-mdSkill
- architectureSkill
- formal-verificationSkill
- foundationSkill
- glossarySkill
- howSkill
- maintenanceSkill
- no-mistakes-tuningSkill
- planSkill
- prototypeSkill
- readmeSkill
- recallSkill
- repo-auditSkill
- teachSkill
- verificationSkill
- visionSkill
- whySkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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
Start with docs/development.md for the checkout, validation and delivery gate, and the design for requirements.
- Distinctive: line 4
Read only the design sections your task lists.
- Distinctive: line 12
Write and review every test against the test-quality rules.
≈ “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
Working on bstack
Start with docs/development.md for the checkout, validation and delivery gate, and the design for requirements. Read only the design sections your task lists.
Set up and validate with the Node 24 command block in README.md.
Iterate with npm test -- --task <id> from tests/tasks.json.
Tests drive the public commands as child processes against disposable fixtures (conventions); reuse tests/scripts/discovery-fixture.ts and tests/fixtures/build.ts.
Take expected results from the design, plan or acceptance case, not from the implementation; TDD is not the default (design "Verification requirements").
Write and review every test against the test-quality rules.
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.