agentleFS
Sign inStart free
MicrosoftKnown publishermicrosoft/fluentui-react-native/.github/skills/maintain-desktop-testing/SKILL.md

maintain-desktop-testing

Skill1.4k starsChanged 5 months agoMITView on GitHub

Change, review, or plan source changes to desktop-driver, desktop-test, storybook-desktop, or storybook-desktop-runtime, including native helpers. Applies package invariants, documentation, native and consumer validation, and changesets.

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 skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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. Distinctive:

    Read the owning package's AGENTS.md, then its contributing reference from the package index.

    line 16
  2. Distinctive:

    Review/plan: read-only. Do not implement, run write-mode formatting, build, create changesets, launch apps, or run native contracts.

    line 21
  3. Distinctive:

    Keep CLI presentation at the owning collector.

    line 31
  4. Distinctive:

    Update owning references and affected README/AGENTS files in the same change.

    line 39
  5. Very specific:

    Add a patch changeset for each changed published package.

    line 44
  6. Distinctive:

    When delegating, pass the package AGENTS.md and selected reference paths.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
SKILL.md

Maintain desktop testing packages

OwnerEntry
WebDriver service, clients, helpersdesktop-driver
App/suite config, lifecycle, WDIO, reportingdesktop-test
Storybook integration, CLI, extraction, testsstorybook-desktop
On-device bridge, Metro, theme, chromeruntime

Read the owning package's AGENTS.md, then its contributing reference from the package index. The runtime has no contributing reference; use its AGENTS.md validation section and its runtime contract reference instead.

Mode first

  • Review/plan: read-only. Do not implement, run write-mode formatting, build, create changesets, launch apps, or run native contracts. Report validation not run.
  • Implementation: continue below.

Implementation

  1. Change the lowest package that owns the behavior; update dependent references when needed. Preserve exact identity, fail-closed behavior, cancellation, ownership-safe cleanup, and explicit unsupported/skip status. Keep CLI presentation at the owning collector; use desktop-driver's shared reporter primitives rather than duplicating mode resolution or framing. Contract fixtures that spawn Node or generate specs pass values through arguments, not spliced source (R-SCAN-002).
  2. For standalone Swift/C++ helpers, read the provider README and native/PROTOCOL.md; keep protocol schema and docs in sync. Apply implement-native-component as a native overlay. React-module and Office bridging-header steps do not apply to these standalone helpers.
  3. Update owning references and affected README/AGENTS files in the same change.
  4. Iterate with yarn test <name> for the files you change (R-VALID-004), then run package format, lint, build, and test. Native changes also need the matching-OS helper contract and affected consumer lane; JS tests do not qualify native behavior.
  5. Add a patch changeset for each changed published package. Finish with yarn clean-lage-cache then yarn lage buildci.

When delegating, pass the package AGENTS.md and selected reference paths; subagents do not inherit them automatically.

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.

Check your setup, free