agentleFS
MicrosoftKnown publishermicrosoft/fluentui-react-native/packages/agentic/desktop-test/AGENTS.md

fluentui-react-native / desktop-test

AGENTS.md1.4k starsChanged 5 months agoMITView on GitHub

This package owns neutral app/suite configuration, desktop lifecycle, and aggregate reporting. Read the user guide, then select the narrowest topic in the reference index. For configuration work, begin with configuration; for reports and run status, use reporting, including the shared CLI reporter modes and bounded structured output contract. - Keep the harness application-neutral: no Storybook, React, or React Native dependencies. Storybook is introduced only by the optional integration. - Preserve exact application identity and ownership semantics. Reject unknown config fields…

Trending

Quiet since March.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/fluentui-react-native repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about microsoft/fluentui-react-native

The biggest 5 of 37 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 37

Talked about on GitHub and Bluesky (37 times).

On GitHub · 36

31 more on GitHub

On Bluesky · 1

The file

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

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the user guide, then select the narrowest topic in the reference index.

    line 8
  2. Distinctive:

    Keep the harness application-neutral: no Storybook, React, or React Native dependencies.

    line 16
  3. Distinctive:

    Never count skipped capabilities, empty work, or incomplete work as passing coverage.

    line 24
  4. Distinctive:

    Keep published API changes explicit and update the owning reference with the implementation.

    line 26
  5. Very specific:

    Keep generic and Storybook service composition in src/driverService.ts.

    line 28
  6. Very specific:

    Run the package scripts: yarn format, yarn lint, yarn build, and yarn test.

    line 33

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

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

Desktop Test agent instructions

This package owns neutral app/suite configuration, desktop lifecycle, and aggregate reporting.

Start here

Read the user guide, then select the narrowest topic in the reference index. For configuration work, begin with configuration; for reports and run status, use reporting, including the shared CLI reporter modes and bounded structured output contract.

Invariants

  • Keep the harness application-neutral: no Storybook, React, or React Native dependencies. Storybook is introduced only by the optional integration.
  • Preserve exact application identity and ownership semantics. Reject unknown config fields and invalid app/suite references.
  • WDIO owns suite sessions. Do not create competing WebDriver sessions from hooks.
  • Cleanup only resources whose ownership was recorded; interactive runs use the per-user workload lock.
  • Never count skipped capabilities, empty work, or incomplete work as passing coverage.
  • Keep published API changes explicit and update the owning reference with the implementation.
  • Keep generic and Storybook service composition in src/driverService.ts; never bypass its durable recovery, descriptor lifetime or settled close.

Validation

Run the package scripts: yarn format, yarn lint, yarn build, and yarn test. For changes to native lifecycle or consumers, follow the qualification matrix in references/contributing.md. Add a patch changeset for this published package and finish code/configuration changes with yarn clean-lage-cache followed by yarn lage buildci.

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.