Microsoft.UI.Reactor plugin
Claude Code plugin for WinUI 3 in a React style: an agent and 16 skills write components without XAML or ViewModels
- 867 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Installation runs `bootstrap.ps1` with `-ExecutionPolicy Bypass` and installs the global dotnet tool `mur` and a template pack
- The agent builds and runs the app with `dotnet` commands, so project code executes on your machine
Install
- Works in
Manual install
git clone https://github.com/microsoft/microsoft-ui-reactor.git
cd microsoft-ui-reactor
& (Get-Process -Id $PID).Path -ExecutionPolicy Bypass -File .\bootstrap.ps1PowerShell commands from the README. The script installs the plugin into `~/.claude/plugins/reactor`, the `mur` CLI and the templates.
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Installation runs `bootstrap.ps1` with `-ExecutionPolicy Bypass` and installs the global dotnet tool `mur` and a template pack
- The agent builds and runs the app with `dotnet` commands, so project code executes on your machine
This is third-party code. Review the repository files before installing.
What it does
The reactor plugin from the Microsoft.UI.Reactor repository gives Claude Code the `reactor-dev` agent and 16 skills for the Reactor framework. Reactor describes a WinUI 3 interface as a tree of C# components with `UseState` and `UseEffect` hooks: no XAML, data bindings or ViewModels. Every element stays a real WinUI control. The skills cover the DSL, forms, navigation, charts, commanding, window docking, input and gestures, async resources, theming and builds. The agent takes element factories, hooks and check rules from them when it creates an app, adds a feature or fixes a bug. The framework is experimental: the README marks it with an April 2026 status, and its subsystems are listed as Preview, Draft or Early.
Who it is for. C# developers who build WinUI 3 desktop apps in a React style and hand part of the work to Claude Code.
Good fit when
- A new WinUI 3 app is created on Reactor from scratch, and the agent starts with the `reactor-getting-started` skill
- A form with field validation goes into a finished component, and the agent uses the `reactor-forms` skill
- The interface needs D3-based charts, which the `reactor-charts` skill covers
- A build fails and the agent follows the checks in the `reactor-build-and-check` skill
Not a fit when
- The app lives on XAML and MVVM: the README leaves that path to plain WinUI and Reactor adds nothing
- The interface has to run outside Windows: the framework is built on WinUI 3
- A version with stability guarantees is required: the project is experimental and many subsystems are still Draft or Early
Example request
Build a task list window with an add form on Reactor and keep the state in hooksLimitations
- The project is experimental, with an April 2026 status in the README. APIs of subsystems such as docking and navigation are marked Draft and may change.
- The plugin is installed by `bootstrap.ps1` from a cloned repository; the README describes no other way.
- Windows, Developer Mode and a build with an explicit platform are required: `dotnet build -p:Platform=x64`.
- Clone the repository into a short path such as `C:\src\`, or the build hits the 260-character limit.
How to disable. The plugin lives in `~/.claude/plugins/reactor`, and deleting that folder removes it. The `Microsoft.UI.Reactor` package is dropped from app dependencies separately.
FAQ
How do I install the Reactor plugin in Claude Code?
Clone the repository and run `bootstrap.ps1` through PowerShell. The script copies the plugin to `~/.claude/plugins/reactor`, installs the `mur` CLI and the `dotnet new reactor` templates. `mur doctor` confirms the install.
Is the plugin required to build an app on Reactor?
No. Install the template with `winget install Microsoft.WinAppCli` and `winapp new -t reactor -n MyApp`, then `dotnet run` starts the app. The plugin adds the knowledge for the agent on top.
Does Reactor replace XAML?
It describes WinUI 3 content in C# code but uses real WinUI controls. XAML and MVVM remain a working path, and both approaches live in one app.
Which platform does the build need?
Run the build with an explicit platform: `dotnet build -p:Platform=x64` or ARM64. Without `-p:Platform` a `WindowsAppSDKSelfContained` error appears. Enable Developer Mode in Windows and clone the repository into a short path.
Which skills ship in the plugin?
Sixteen, among them `reactor-dsl`, `reactor-forms`, `reactor-navigation`, `reactor-charts`, `reactor-docking`, `reactor-async` and `reactor-build-and-check`. The `reactor-dev` agent works through these skills.
Discussion
No questions or reviews yet.
Related
PluginsA Claude Code plugin of eight builder skills: UI cloning, PRDs, CLAUDE.md scaffolding, terse research and a refactor tournament.
Claude Code plugins with development recipes: agree on the outcome, design, implement with checks and run an independent review
Windows Dev Skills
win-dev-skills
Agent Plugins 1.0 from Microsoft for GitHub Copilot CLI, Claude Code and Codex: native Windows apps on WinUI 3 and the Windows App SDK. A preview version
A Claude Code plugin for .NET 10: 47 skills, 10 agents, 16 commands, rules, hooks and a Roslyn MCP server.
MadAppGang's Claude Code plugin marketplace: agents and commands for a React frontend and a Bun backend
A ready .claude folder in Polish: skills, agents and rules that lead a project from idea to a React and Supabase app.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| Microsoft.UI.Reactor (this card) | yes | 867 | |
| dotnet-artisan | no | 237 | a general .NET plugin with agents for ASP.NET Core, Blazor and MAUI, with no knowledge of the Reactor framework |
| dotnet-claude-kit | no | 829 | a .NET 10 kit with a Roslyn MCP server that does not cover WinUI 3 or Reactor |
README in short
The README presents Reactor as a new way to describe WinUI 3: a virtual element tree, hooks and a C# DSL over real controls. It continues with a quick start through `winapp new`, a subsystem table with statuses from Early to Preview and a build-from-source section where `bootstrap.ps1` installs the `mur` CLI and the agent plugin.