libxmtp / nix
AGENTS.md127 starsChanged 11 days agoMITView on GitHub
Build affected outputs with nix build --no-link .#<output>; run dev/nix-shell 'just lint-config' and dev/nix-shell 'just test dev'. - Keep compiler credentials and writable host caches out of derivations. - For shell logging/cache diagnostics, read shell diagnostics. Before changing Node pins or patches, read runtime maintenance. - Keep source closures narrow but complete, including embedded data, migrations, proto inputs, and test fixtures. Use xmtp.filesets.mkClosureSource for package checks. Verify relevant edits change .drvPath and unrelated edits do not. - Dependency layers must…
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 repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- .github/workflows/AGENTS.mdAGENTS.md
- proto/AGENTS.mdAGENTS.md
- sdks/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/workflows/CLAUDE.mdCLAUDE.md
- nix/CLAUDE.mdCLAUDE.md
- proto/CLAUDE.mdCLAUDE.md
- sdks/CLAUDE.mdCLAUDE.md
- authoring-specsSkill
- check-ciSkill
- checking-spec-complianceSkill
- reviewing-specsSkill
- smoke-checkSkill
- working-with-nixSkill
- working-with-worktreesSkill
- writing-agent-docsSkill
- writing-rustSkill
- writing-rust-testsSkill
- writing-typescriptSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 1 is common, 4 are distinctive, and 1 is very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈4
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
- Common: line 6
Keep compiler credentials and writable host caches out of derivations.
- Distinctive: line 8
Before changing Node pins or patches, read runtime maintenance.
- Very specific: line 9
Keep source closures narrow but complete, including embedded data, migrations, proto inputs, and test fixtures.
- Distinctive: line 14
Keep compiler, linker, and Apple SDK from one toolchain.
- Distinctive: line 16
Read build maintenance for source filters, dependency layers, services, bindgen pins, generated products, and Android emulator changes.
- Distinctive: line 18
Read RN build constraints before changing RN derivations, native dependencies, host access, or cross-host exchange.
≈ “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
Nix
Build affected outputs with nix build --no-link .#<output>; run
dev/nix-shell 'just lint-config' and dev/nix-shell 'just test dev'.
- Keep compiler credentials and writable host caches out of derivations.
- For shell logging/cache diagnostics, read shell diagnostics. Before changing Node pins or patches, read runtime maintenance.
- Keep source closures narrow but complete, including embedded data, migrations,
proto inputs, and test fixtures. Use
xmtp.filesets.mkClosureSourcefor package checks. Verify relevant edits change.drvPathand unrelated edits do not. - Dependency layers must use their consumer's Cargo packages, targets, profile, features, and environment. Workspace feature unification can hide missing inputs.
- Keep compiler, linker, and Apple SDK from one toolchain. Preserve exact canonical Xcode pins and separate local outputs; never switch global Xcode in build code.
- Read build maintenance for source filters, dependency layers, services, bindgen pins, generated products, and Android emulator changes.
- Read RN build constraints before changing RN derivations,
native dependencies, host access, or cross-host exchange. Keep sandbox access
narrow and local receipts distinct from canonical admission. Keep advisory RN
outputs isolated in
ciSets.<system>.rn. - Cache setup and limits: Nix setup.
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.