What problem does it solve? After upgrading to .NET 10, .NET MAUI apps default to edge-to-edge rendering, causing content to overlap status bars, notches, and keyboards. This Skill guides you through the new cross-platform SafeAreaEdges and SafeAreaRegions APIs to control per-edge insets on Android, iOS, and Mac Catalyst. ## Core Features & Use Cases - Per-edge safe area control: Apply SafeAreaRegions values (None, Container, SoftInput, All, Default) uniformly, per-axis, or per-edge via XAML or C#. - Keyboard avoidance and immersive layouts: Build chat UIs, photo viewers, and mixed layouts with edge-to-edge headers and safe bodies. - Blazor Hybrid integration: Coordinate CSS env(safe-area-inset-*) variables with viewport-fit=cover to avoid double-padding. - Legacy migration: Replace ios:Page.UseSafeArea, Layout.IgnoreSafeArea, and WindowSoftInputModeAdjust.Resize with the new API. - Use Case: Your Android content slides behind the status bar after upgrading to .NET 10; add SafeAreaEdges="Container" to the ContentPage to restore .NET 9 behavior. ## Quick Start Ask the AI to fix a .NET MAUI page whose content overlaps the status bar or keyboard using the SafeAreaEdges property.