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

fluentui-react-native / storybook-desktop

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

This package owns the Storybook integration CLI and runtime orchestration. Read the package README, then select the closest topic in the reference index. Use references/contributing.md for source ownership and validation. - Keep app-specific identity, story discovery, and platform exclusions in the consumer app configuration. - Keep Storybook-specific behavior here; general target configuration and aggregate lifecycle reporting belong to @fluentui-react-native/desktop-test. - Only accept statically extractable story/test plans; invalid or dynamic plans fail generation. - Preserve authenticated runtime readiness, correlated request/run IDs,…

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

9 rules. About 0 are common, 4 are distinctive, and 5 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.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the package README, then select the closest topic in the reference index.

    line 7
  2. Distinctive:

    Keep app-specific identity, story discovery, and platform exclusions in the consumer app configuration.

    line 13
  3. Very specific:

    Keep Storybook-specific behavior here.

    line 15
  4. Distinctive:

    Only accept statically extractable story/test plans.

    line 17
  5. Distinctive:

    Treat generated manifests, runtime state, native workspaces, and build products as disposable.

    line 21
  6. Distinctive:

    Keep args refused and manifest-backed smoke selection on driver sessions.

    line 24
  7. Very specific:

    Keep global output formatting on --reporter.

    line 25
  8. Very specific:

    Run yarn format, yarn lint, yarn build, and yarn test from this package.

    line 31
  9. Very specific:

    When changing story extraction or runtime behavior, run the relevant apps/storybook manifest/bundle/smoke lane.

    line 32

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

Storybook Desktop agent instructions

This package owns the Storybook integration CLI and runtime orchestration.

Start here

Read the package README, then select the closest topic in the reference index. Use references/contributing.md for source ownership and validation.

Invariants

  • Keep app-specific identity, story discovery, and platform exclusions in the consumer app configuration.
  • Keep Storybook-specific behavior here; general target configuration and aggregate lifecycle reporting belong to @fluentui-react-native/desktop-test.
  • Only accept statically extractable story/test plans; invalid or dynamic plans fail generation.
  • Preserve authenticated runtime readiness, correlated request/run IDs, and native story-root verification. Never accept uncorrelated channel events.
  • Treat generated manifests, runtime state, native workspaces, and build products as disposable; fix their owning source.
  • Agent manifests use the controlled transport, never upstream channel relays. Keep args refused and manifest-backed smoke selection on driver sessions.
  • Keep global output formatting on --reporter; the child Node test reporter is --test-reporter. Long-lived command readiness is emitted only after its owned services pass readiness checks.

Validation

Run yarn format, yarn lint, yarn build, and yarn test from this package. When changing story extraction or runtime behavior, run the relevant apps/storybook manifest/bundle/smoke lane. Report each platform and renderer separately; JavaScript tests are not native qualification.

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.

Reviews can't be read right now.

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.