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

fluentui-react-native / design

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

This is the instruction root for @fluentui-react-native/design and every descendant. The package owns Fluent UI React Native's theming contract: theme sources and providers, ready-made Fluent and Flex themes, structured appearance, Flex and legacy tokens, the token mappings, themed style factories, the runtime color library, and test-only design fixtures. Read the user guide, then select the narrowest topic in the reference index: Component authors applying tokens and styles also follow their component workflow; for agentic components that is the repository reference…

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

8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

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

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

    line 9
  2. Very specific:

    Keep one ThemeProvider for both authoring models.

    line 28
  3. Distinctive:

    Keep the root entry point free of the legacy projection, deprecated token data, and color compositing.

    line 32
  4. Distinctive:

    Keep color resolution lazy: resolving, merging, and reading rest never run the interaction algorithm, and a derived state computes once per …

    line 35
  5. Very specific:

    Treat src/tokens/mappings/flex-token-map.yaml as the canonical token mapping (R-DESIGN-001), and regenerate rather than edit generated …

    line 37
  6. Very specific:

    Keep the Fluent 2 token JSON loaders and pipeline mappers in src/deprecated/.

    line 40
  7. Very specific:

    Update the owning reference with every behavior or API change, and record unfinished work only in references/remaining-work.md …

    line 43
  8. Very specific:

    Run yarn format, yarn lint, yarn build, yarn test, and yarn check:mappings in this package, add a changeset, and finish with yarn …

    line 48

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

Design agent instructions

This is the instruction root for @fluentui-react-native/design and every descendant. The package owns Fluent UI React Native's theming contract: theme sources and providers, ready-made Fluent and Flex themes, structured appearance, Flex and legacy tokens, the token mappings, themed style factories, the runtime color library, and test-only design fixtures.

Start here

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

TaskRead
Theme authoring, providers, appearance, theme hooks, or legacy projectionTheming
Authoring, resolving, or reading Flex colors, or migrating flat colorsFlex colors
Token sources, Flex token mapping, or the pinned x3 sourceTokens
Themed style caches or state and color style factoriesStyling
Runtime color parsing, contrast, or interaction colorsColor library
Test fixtures or contrast validationTesting helpers
Exports, subpaths, bundle boundaries, or compatibility packagesEntry points
Source layout, generated files, tests, or validationContributing
Planning theming or appearance workRemaining work

Component authors applying tokens and styles also follow their component workflow; for agentic components that is the repository reference components.agentic.styles-and-tokens.

Invariants

  • Keep one ThemeProvider for both authoring models. Providers publish metadata; only hooks construct converted models, and neither hook constructs the model it does not return.
  • Key caches by source, revision, and resolved appearance, keep them outside author-owned objects, and give every new ThemeState a new style registry.
  • Keep the root entry point free of the legacy projection, deprecated token data, and color compositing; it reaches the color library's interaction algorithm only through the Flex interaction policy. Legacy and optional APIs stay behind their subpaths.
  • Keep color resolution lazy: resolving, merging, and reading rest never run the interaction algorithm, and a derived state computes once per resolved color.
  • Treat src/tokens/mappings/flex-token-map.yaml as the canonical token mapping (R-DESIGN-001), and regenerate rather than edit generated token and projection files.
  • Production code must not depend on the testing entry point (R-DESIGN-002).
  • Keep the Fluent 2 token JSON loaders and pipeline mappers in src/deprecated/. Only tests, other deprecated code, build scripts, and the existing deprecated consumers may use them, and no other entry point may reach them (R-DESIGN-003).
  • Update the owning reference with every behavior or API change, and record unfinished work only in references/remaining-work.md (R-PKGDOC-009).

Validation

Run yarn format, yarn lint, yarn build, yarn test, and yarn check:mappings in this package, add a changeset, and finish with yarn clean-lage-cache followed by yarn lage buildci. See contributing.

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.