agentleFS
duckduckgoduckduckgo/apple-browsers/.maestro/AGENTS.md

apple-browsers

AGENTS.md274 starsChanged 9 days agoApache-2.0View on GitHub

Read this before writing, fixing or running a flow in .maestro/. - Pin every flag that decides which surface a flow asserts on, as quoted ff.<flag>: "true" launch arguments; unquoted YAML booleans are ignored. An unpinned flag follows the live privacy config, so a privacy-configuration change can turn a flow red with no app change. - ff. arguments don't make the user internal. A flag whose default is .internalOnly also needs isInternalUser: "true". - tapOn doesn't retry a tap the…

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
  1. Very specific:

    Read this before writing, fixing or running a flow in .maestro/.

    line 3

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

iOS end-to-end tests (Maestro)

Read this before writing, fixing or running a flow in .maestro/.

  • Pin every flag that decides which surface a flow asserts on, as quoted ff.<flag>: "true" launch arguments; unquoted YAML booleans are ignored. An unpinned flag follows the live privacy config, so a privacy-configuration change can turn a flow red with no app change.
  • ff. arguments don't make the user internal. A flag whose default is .internalOnly also needs isInternalUser: "true".
  • tapOn doesn't retry a tap the app dropped. Guard each navigation step by waiting with extendedWaitUntil for an element that only exists on the destination screen.
  • Locally, setup_ui_tests.sh builds into the repository's DerivedData/ and creates the iPhone 16 and iPad 10th generation simulators on iOS 18.2; it exits unless Maestro is exactly 1.40.3. run_ui_tests.sh <flow-or-folder> then reinstalls the app for each flow and runs it on the iPad when the flow has the ipad tag.
  • CI runs suites by tag on Maestro Cloud: see the matrix in .github/workflows/ios_end_to_end.yml. iPad runs exist only for the suites listed there with an iPad device, and they exclude flows tagged iphone; iPhone runs exclude flows tagged ipad.
  • To reproduce a CI failure without building, download the run's duckduckgo-ios-app artifact and run the flow on a local iPhone 16 / iOS 18.2 simulator, which matches the Cloud device.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.