maui-current-apis

Detect deprecated .NET MAUI APIs across XAML/C#, Blazor Hybrid, and MauiReactor.

Updated Nov 5, 2025
One-click install
npx skills add https://github.com/mkazimoto/AppMAUICopilot --skill maui-current-apis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maui-current-apis
Source: https://github.com/mkazimoto/AppMAUICopilot/tree/main/.github/skills/maui-current-apis
Command: npx skills add https://github.com/mkazimoto/AppMAUICopilot --skill maui-current-apis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents generation and review of MAUI code that uses deprecated, obsolete, or removed APIs across XAML/C#, Blazor Hybrid, and MauiReactor, helping teams keep projects current and maintainable.

Core Features & Use Cases

  • Reasoning framework for detecting the project's target framework and library versions to determine API availability.
  • Curated table of the most common MAUI 10 deprecated API traps and recommended replacements.
  • Guidance for code generation and code review to migrate away from deprecated APIs and ensure API currency.
  • Use Case: Before generating MAUI code or reviewing existing code, validate API usage and surface migration notes.

Quick Start

Run this skill before generating MAUI code to verify API currency and provide migration guidance.

Frequently Asked Questions about maui-current-apis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check .NET MAUI code for deprecated API usage during code review?

To check .NET MAUI code for deprecated API usage, validate XAML/C#, Blazor Hybrid, and MauiReactor code against a curated deprecation table. This detects the project's TargetFrameworks and library versions to surface migration notes and block obsolete APIs.

What is the best way to migrate removed MAUI APIs in XAML and C#?

The best way to migrate removed MAUI APIs in XAML and C# is to apply migration guardrails using a curated deprecation table. This provides clear migration guidance and safe replacements by detecting the project's target framework and library versions.

Does this API migration approach work with Blazor Hybrid and MauiReactor projects?

Yes, API migration guardrails work with Blazor Hybrid and MauiReactor projects. The validation detects the project's target framework and library versions to determine API availability across these specific MAUI frameworks.

When do I need to validate API currency for MAUI code generation?

You need to validate API currency for MAUI code generation before generating any new code. Running this check beforehand verifies API availability and provides migration guidance to prevent introducing deprecated, obsolete, or removed APIs into your project.

Why does my MAUI code use obsolete APIs after upgrading library versions?

Your MAUI code uses obsolete APIs because target framework and library version changes alter API availability. Detecting these project settings and validating against a curated deprecation table identifies the removed APIs and recommends safe defaults.

What are the limitations of using a curated deprecation table for MAUI migration?

A limitation of using a curated deprecation table for MAUI migration is that it covers the most common deprecated API traps rather than an exhaustive list. Detection depends on accurately reading the project's TargetFrameworks and library versions to determine API availability.