agentleFS
MicrosoftKnown publishermicrosoft/WindowsAppSDK/dev/Templates/Dotnet/templates/reactor-blank-app/AGENTS.md

WindowsAppSDK / reactor-blank-app

AGENTS.md4.7k starsChanged 10 months agoMITView on GitHub

This is a WinUI 3 app built with Microsoft.UI.Reactor and the Windows App SDK. The UI is declared in pure C# — there is no XAML in this project, so don't add .xaml files or convert components to XAML. The WinApp CLI handles the Windows-specific parts of app development. Install it with: A sample of the commands it provides: Prefer these over hand-rolled scripts for packaging, signing, and UI verification. 1. From the project directory, run dotnet build and fix…

Trending

Quiet since September.about the whole repository

Dec 2025: 1 mentionJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 0 mentionsApr 2026: 0 mentionsMay 2026: 1 mentionJun 2026: 1 mentionJul 2026: 1 mentionAug 2026: 0 mentionsSep 2026: 2 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the microsoft/WindowsAppSDK repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about microsoft/WindowsAppSDK

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

See all 46

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

On GitHub · 26

21 more on GitHub

On Stack Overflow · 16

11 more on Stack Overflow

On Bluesky · 1

The file

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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Prefer these over hand-rolled scripts for packaging, signing, and UI verification.

    line 31
  2. Very specific:

    Run winapp ui inspect -a <app> --interactive, replacing <app> with the app's process name or PID.

    line 38

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

Working on this app

This is a WinUI 3 app built with Microsoft.UI.Reactor and the Windows App SDK. The UI is declared in pure C# — there is no XAML in this project, so don't add .xaml files or convert components to XAML.

Use the WinApp CLI

The WinApp CLI handles the Windows-specific parts of app development. Install it with:

winget install Microsoft.winappcli --source winget

A sample of the commands it provides:

CommandUse it to
winapp runBuild and launch the app with full MSIX package identity
winapp find-ui "<query>" --source reactorFind a working Reactor code example before writing a component from scratch
winapp ui inspect -a <app>Inspect the running app's UI element tree
winapp ui invoke|set-value|send-keysDrive the UI to verify a change works
winapp ui screenshot -a <app>Capture the window as a PNG
winapp manifestCreate and modify Package.appxmanifest
winapp package / winapp signBuild and code-sign an MSIX for distribution
winapp certCreate a development signing certificate

Prefer these over hand-rolled scripts for packaging, signing, and UI verification.

Development workflow

  1. From the project directory, run dotnet build and fix any build errors.
  2. Launch with dotnet run. Keep the app running and use another terminal for UI verification.
  3. Run winapp ui inspect -a <app> --interactive, replacing <app> with the app's process name or PID. Use the reported selectors with winapp ui invoke or winapp ui set-value to exercise the changed UI, then inspect again to confirm the expected result. For visual changes, capture a screenshot with winapp ui screenshot -a <app> -o screenshot.png.

Discovering commands

The list above is only a sample. Every command documents itself — check the help before guessing at syntax:

winapp --help
winapp <command> --help
winapp --cli-schema      # full command tree as JSON, for tooling

WinUI skills

The WinUI plugin provides skills for design, development, UI testing, and packaging. Install it for GitHub Copilot CLI with:

copilot plugin marketplace add microsoft/WinAppCli
copilot plugin install winui@winappcli

For Claude Code or Codex, follow the installation instructions.

Apply skill guidance without introducing XAML; keep the UI in pure C#.

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.