What problem does it solve? Handling app state transitions in .NET MAUI is error-prone: developers lose draft data on backgrounding, confuse Deactivated with Stopped, or miss that Android's back button can skip Stopped entirely. This Skill provides correct patterns for subscribing to Window lifecycle events and preserving state across background and resume cycles. ## Core Features & Use Cases - Window Lifecycle Events: Subscribe to Created, Activated, Deactivated, Stopped, Resumed, and Destroying via CreateWindow overrides or a custom Window subclass. - Platform Lifecycle Mapping: Maps cross-platform events to native callbacks on Android (OnCreate, OnPause), iOS/Mac Catalyst (DidEnterBackground, WillEnterForeground), and Windows (VisibilityChanged, Closed), plus ConfigureLifecycleEvents for direct native hooks. - State Preservation Workflow: Save transient state in OnStopped and OnDestroying using Preferences, then restore it in OnResumed. - Use Case: A user is drafting a message in your MAUI app and switches to another app. Save the draft text and scroll position in OnStopped, restore them in OnResumed, and also save in OnDestroying to handle the Android back-button path. ## Quick Start Use the maui-app-lifecycle skill to add Window lifecycle handlers that save my form draft when the app backgrounds and restore it on resume.