agentleFS
MicrosoftKnown publishermicrosoft/microsoft-ui-xaml/dxaml/xcp/AGENTS.md

microsoft-ui-xaml / xcp

AGENTS.md8.6k starsChanged 51 days agoMITView on GitHub

Most code in this repo uses the IFC_RETURN macro to record some information about an HRESULT and return if it's a failure.

Trending

Quiet since August.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 1 mentionMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 1 mentionSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/microsoft-ui-xaml repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about microsoft/microsoft-ui-xaml

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

See all 72

Talked about on GitHub, Stack Overflow, Hacker News and Bluesky (72 times).

On GitHub · 30

25 more on GitHub

On Stack Overflow · 30

25 more on Stack Overflow

On Hacker News · 11

6 more on Hacker News

On Bluesky · 1

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Prefer IFC_RETURN where applicable.

    line 5
  2. Very specific:

    Instead of using return <expr>.

    line 6
  3. Very specific:

    Don't use S_FALSE

    line 7

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

Most code in this repo uses the IFC_RETURN macro to record some information about an HRESULT and return if it's a failure.

  • Prefer IFC_RETURN where applicable. Covert IFC to IFC_RETURN opportunistically, only if you're already changing that function.
  • Instead of using return <expr>; to return an HRESULT, prefer to IFC_RETURN(<expr>) first and then return S_OK;.
  • Don't use S_FALSE

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.