agentleFS
rebornixrebornix/Agmente/AgmenteUITests/AGENTS.md

Agmente / AgmenteUITests

AGENTS.md545 starsChanged 9 months agoMITView on GitHub

The file

We split this AGENTS.md into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    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:

    Use root .agmente.paths for machine-local ACP/Codex checkout locations when debugging upstream compatibility.

    line 7
  2. Distinctive:

    Read it as the source of truth.

    line 8
  3. Distinctive:

    Add-server flows for ACP and Codex.

    line 11
  4. Distinctive:

    Do not hard-code developer-specific endpoints or filesystem paths in tests.

    line 25
  5. Distinctive:

    Prefer accessibility IDs over coordinate taps.

    line 28
  6. Distinctive:

    If adding/changing critical controls, add stable accessibility IDs in app code.

    line 29
  7. Distinctive:

    Keep ACP and Codex add-server flows separately validated.

    line 30
  8. Distinctive:

    Keep test assertions tied to behavior, not layout coordinates.

    line 31
  9. Distinctive:

    After simulator E2E runs:

    line 34
  10. Distinctive:

    Stop local agent/app-server process.

    line 35

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

Agmente UI Tests Guide

Scope

Simulator-driven UI tests, including scenario-backed manual E2E and opt-in Codex local E2E.

External Repo Paths

  • Use root .agmente.paths for machine-local ACP/Codex checkout locations when debugging upstream compatibility.
  • Read it as the source of truth; do not hard-code local absolute paths.

Coverage Goals

  • Add-server flows for ACP and Codex.
  • Connect/initialize/session lifecycle UX.
  • Prompt send/stream/render experience.
  • Accessibility-id stability for critical controls.

Codex E2E Contract

  • E2E test is opt-in and environment-driven.
  • Scenario intent lives under e2e/scenarios/codex/; the env vars below are the UI-test harness contract, not the source of truth for scenario behavior.
  • Supported env keys:
    • AGMENTE_E2E_CODEX_ENABLED
    • AGMENTE_E2E_CODEX_ENDPOINT
    • AGMENTE_E2E_CODEX_HOST
    • AGMENTE_E2E_CODEX_PROMPT
    • AGMENTE_E2E_CODEX_CONFIG_PATH
  • Do not hard-code developer-specific endpoints or filesystem paths in tests.

UI Automation Rules

  • Prefer accessibility IDs over coordinate taps.
  • If adding/changing critical controls, add stable accessibility IDs in app code.
  • Keep ACP and Codex add-server flows separately validated.
  • Keep test assertions tied to behavior, not layout coordinates.

Cleanup Expectations

After simulator E2E runs:

  1. Stop local agent/app-server process.
  2. Uninstall app from simulator to reset state.

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.