Open-source platform for building cross-platform native Mobile, Web, Desktop, and Embedded apps from a single C#/XAML codebase. Work from any IDE/CLI with Hot Reload, Visual Designer, MCPs, and Skills built for modern .NET workflows. 200M+ NuGet downloads.
Reviews changes for how they fit the broader Uno Platform framework — flags tech debt, bad patterns, scalability issues, layering violations, and wrong platform-specialization choices. Use after a non-trivial change is drafted to check architectural fit before commit. Invoke with the change scope and the modules it…
Reviews changes for contract stability — public API surface vs WinUI parity (binary/source compat, [Uno.NotImplemented] handling, DependencyProperty registration), public surface minimality, and test fidelity (do tests validate behavior/parity, not implementation internals?). Use after a change that touches public…
The Socratic questioner of the review panel — surfaces the questions the author didn't ask: unstated intent, hidden assumptions, unconsidered platform/parity alternatives, and missing evidence. Use after a change is drafted, alongside the specialist reviewers, to expose gaps before commit. Invoke with the change…
Reviews changes for diagnosability and resilience — structured logging discipline, CancellationToken propagation (incl. source generators), async-void safety, and the diagnosability of tooling (DevServer / RemoteControl). Use after a change that touches I/O, background work, async APIs, source generators, or the…
Audits changes for performance hazards on all targets — blocking calls, async void time-bombs, source-generator allocation/cancellation discipline, layout/render hot-path allocations, property-system boxing, idle CPU toll, and WASM memory growth. Invoke with the change scope and the modules it touches.
Validates that a change correctly addresses its stated requirement, evaluates solution elegance, checks for duplication across platform partials and missed refactoring, verifies sample/test coverage, and flags comment pollution. Use after a change is drafted to verify the solution solves the right problem in the right…
Audits code for vulnerabilities at the framework's real trust boundaries — XAML/data-binding of untrusted content, the DevServer/RemoteControl network host, source generators reading project inputs, WASM JS interop, and platform file/clipboard/launcher APIs. Use after a change touching input handling, the host…
Challenges decisions, questions assumptions, and surfaces edge cases other agents missed — with WinUI-parity and cross-platform correctness front of mind. Use after a completed change to stress-test it before committing. Invoke with explicit context — the change under review, what was assumed, and what's already been…