maui-current-apis

To avoid deprecated MAUI APIs during AI code generation, you need a guardrail that inspects your TargetFramework and package references to enforce safe, version-aware replacements. This skill provides that proactive validation.

Yes, deprecated API detection works with Blazor Hybrid and MauiReactor. It inspects package references like Microsoft.AspNetCore.Components.WebView.Maui and Reactor.Maui to apply safe replacements across all XAML/C# project types.

The checked package versions include Microsoft.Maui.Controls, CommunityToolkit.Maui, CommunityToolkit.Mvvm, and Reactor.Maui. It reads these package references to determine the correct deprecated API table for MAUI 10.

You should run MAUI API guardrails before generating any MAUI-related code. Running it early during scaffolding or AI-assisted development ensures API currency and prevents obsolete code from being inserted into your project.

AI assistants generate removed or obsolete MAUI APIs because they lack version-aware reasoning. Without inspecting the project's TargetFramework and package versions, the AI cannot distinguish between current and deprecated API tables.

The best way to update obsolete CommunityToolkit.Mvvm APIs is to apply a curated deprecated API table that maps removed methods to recommended replacements. This skill enforces those safe replacements automatically during code generation.