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

fluentui-react-native / native-core

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

This is the instruction root for @fluentui-react-native/native-core and every descendant. The package owns modern native-backed components and modules, the legacy Callout and FocusZone wrappers, and their macOS and Windows native implementations. Read the user guide, then select the narrowest topic in the reference index: Native changes use the implement-native-component skill. Apple changes follow the repository's Apple and Office rules (R-APPLE-001 through R-APPLE-007, in native.apple-office); Windows Fabric views follow native.windows-fabric. - Follow R-APPLE-001 through R-APPLE-007 for shared services and renderer adapters.…

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, 4 are distinctive, and 4 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.

  • 4

    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:

    Follow R-APPLE-001 through R-APPLE-007 for shared services and renderer adapters.

    line 26
  3. Distinctive:

    Prefer Swift for new macOS AppKit/domain behavior.

    line 28
  4. Very specific:

    Use phasedComponent for hook-bearing wrappers: run hooks and create slots in the first phase and return a hook-free directComponent.

    line 53
  5. Distinctive:

    Keep legacy aliases/registrations and Win32 host ownership.

    line 56
  6. Distinctive:

    Keep generated code generated and verify packed native ownership.

    line 61
  7. Very specific:

    Run yarn format, yarn lint, yarn build, and yarn test in this package, plus yarn codegen:windows --check after schema changes and yarn …

    line 72
  8. Very specific:

    Add a changeset and finish with yarn clean-lage-cache followed by yarn lage buildci.

    line 75

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

Native Core agent instructions

This is the instruction root for @fluentui-react-native/native-core and every descendant. The package owns modern native-backed components and modules, the legacy Callout and FocusZone wrappers, and their macOS and Windows native implementations.

Start here

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

TaskRead
Public entry points, legacy wrappers, shims, or autolinkingEntry points
Modern Callout, FocusZone, popups, or their platform behaviorModern components
JavaScript, spec, native layout, or renderer adaptersArchitecture
Codegen, registration names, podspecs, or package contentsCodegen, registration, and publishing
macOS accessibility that depends on the RNmacOS patchRNmacOS patch
Validation, native stories, or the Apple boundary probeContributing
Planning work or checking open gatesRemaining work

Native changes use the implement-native-component skill. Apple changes follow the repository's Apple and Office rules (R-APPLE-001 through R-APPLE-007, in native.apple-office); Windows Fabric views follow native.windows-fabric.

Invariants

  • Follow R-APPLE-001 through R-APPLE-007 for shared services and renderer adapters. Paper RCT_EXTERN_MODULE files never import the generated Swift header or name generated Swift classes.
  • Prefer Swift for new macOS AppKit/domain behavior. Keep ObjC/ObjC++ for generated protocols, C++ conversion, registration, and renderer integration.
  • Paper and Fabric adapters supply resolved views and event sinks to shared behavior. Shared behavior must not traverse renderer registries.
  • A Paper RCTView subclass hosted by a Fabric component view has no React tag; keep RCTView from building focus, blur, or key events for it.
  • Modern and legacy facades share private host implementations. Legacy must not depend on React-19-only public wrappers.
  • Components and genuine modules are peer consumers of services. Do not route view commands through a global module or create speculative modules.
  • Extract only proven reuse. Share fixtures/contracts before forcing AppKit and Composition into a portable C++ framework.
  • AppKit mutations run on the main thread; Windows uses its owning dispatcher. Module invocation does not establish UI affinity.
  • Scope view/anchor/focus identities to attachment, surface/window, and generation. Legitimate app-wide non-view services have explicit lifecycle; unscoped global tag/focus registries are forbidden.
  • Observers, monitors, requests, and popup links have one owner and idempotent cleanup. Stale cleanup cannot detach a newer registration.
  • Async operations settle once through actual native results. Ref availability is not readiness; a void focus return is not confirmation. Preserve errors, distinguish refusal/cancellation/unsupported/timeout, and never autoqueue pre-mount focus requests.
  • New wrappers use React 19 ref props. FocusZone preserves its native root; Callout's deliberate presentation handle is documented in its contract.
  • Use phasedComponent for hook-bearing wrappers: run hooks and create slots in the first phase and return a hook-free directComponent. Do not wrap an inner hook component; hook-driven props are consumed by the first phase.
  • Keep legacy aliases/registrations and Win32 host ownership. Never send a new managed protocol to a baked host without capability evidence.
  • Root exports require equivalent mandatory behavior on every supported desktop host. Platform previews, compile checks, and skipped tests are not root admission.
  • Keep generated code generated and verify packed native ownership. Preserve the module-named macOS Swift interoperability header.
  • Record exact executed validation in the owning Components or Infrastructure workstream issue before switching machines. Keep the references and component contracts aligned with qualified behavior, and track open work only in remaining work (R-PKGDOC-009).

Validation

Run yarn format, yarn lint, yarn build, and yarn test in this package, plus yarn codegen:windows --check after schema changes and yarn test:apple-integration after macOS changes. Native qualification requires the native story lanes in contributing. Add a changeset and finish 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.