apple-browsers
AGENTS.md274 starsChanged 9 days agoApache-2.0View on GitHub
Loaded into every agent session. Add a line only when agents demonstrably get something wrong and nothing catches it during the task. Procedures live in .claude/skills/; personal preferences live in your user-level config. - Before finishing, run mint run swiftlint lint --strict --force-exclude on the files you changed. CI uses --strict, so any warning, including the file-header check, fails the PR; --force-exclude skips files CI doesn't lint, such as Package.swift. - Every new Swift Testing @Test needs .timeLimit(.minutes(1)), which requires…
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 32,671 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 repository11 other files it gives its agents.
- .maestro/AGENTS.mdAGENTS.md
- ddg-add-feature-flagSkill
- ddg-add-pixelSkill
- ddg-apple-feedback-reviewSkill
- ddg-design-systemSkill
- ddg-diagnose-ci-failureSkill
- ddg-drk-add-iconSkill
- ddg-macos-add-promoSkill
- ddg-sentry-reportSkill
- ddg-xcode-add-fileSkill
- verify-iosSkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before finishing, run mint run swiftlint lint --strict --force-exclude on the files you changed.
- Very specific: line 11
Every new Swift Testing @Test needs .timeLimit(.minutes(1)), which requires @available(iOS 16, macOS 13, *).
- Very specific: line 20
Before reviewing any change, read REVIEW.md first (and REVIEW-pixels.md for pixel or wide event changes).
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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
DuckDuckGo Apple browsers
Loaded into every agent session. Add a line only when agents demonstrably get
something wrong and nothing catches it during the task. Procedures live in
.claude/skills/; personal preferences live in your user-level config.
- Before finishing, run
mint run swiftlint lint --strict --force-excludeon the files you changed. CI uses--strict, so any warning, including the file-header check, fails the PR;--force-excludeskips files CI doesn't lint, such asPackage.swift. - Every new Swift Testing
@Testneeds.timeLimit(.minutes(1)), which requires@available(iOS 16, macOS 13, *). - Adding, moving or deleting files in the Xcode projects: use the
ddg-xcode-add-fileskill. - Adding or changing a pixel or wide event: use the
ddg-add-pixelskill. - Tests that depend on the remote Privacy Configuration arrange each flag state explicitly and assert the app's behavior in that state, including flags changing while the app runs. They never assert what the live configuration currently contains.
- Before reviewing any change, read
REVIEW.mdfirst (andREVIEW-pixels.mdfor pixel or wide event changes). - Pull requests: fill in
.github/PULL_REQUEST_TEMPLATE.md. If theSnapshotReferencessubmodule changed, run./scripts/open-snapshot-submodule-pr.shfirst and add the PR link it prints to the description.
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.

