- Maui Controls Deep DiveApply advanced MAUI control guidance. USE FOR: `CollectionView` incremental loading, `RemainingItemsThreshold`, `EmptyView`, `AutomationId`, avoiding `ScrollView` wrappers, .NET 10 `SafeAreaEdges`, `GraphicsView`/`IDrawable`, gestures, animations. DO NOT USE FOR: general layout, full accessibility, profiling, handlers.dotnet/maui-labs224
- Maui Current ApisKeep MAUI guidance target-framework-safe. USE FOR: checking TFM, net8 vs net10 API choices, `SafeAreaEdges`, replacing `Application.Current.MainPage`, Xamarin.Forms namespaces, Shell/window APIs, avoiding .NET 10-only APIs on older targets. DO NOT USE FOR: workload discovery, runtime inspection, migration planning.dotnet/maui-labs224
- Maui Custom HandlersImplement or migrate MAUI visual handlers. USE FOR: handler mappers, type guards, unique mapper keys, renderer-to-handler migration, `ConnectHandler`/`DisconnectHandler`, `PropertyMapper`, `CommandMapper`, custom `ViewHandler`, platform partials, `CreatePlatformView`, `ConfigureMauiHandlers`. DO NOT USE FOR: non-visual APIs, full Xamarin migration, native SDK bindings.dotnet/maui-labs224
- Maui Devflow DebugRun DevFlow inspect-and-fix loops for MAUI apps. USE FOR: launch, device selection, agent recovery, broker/port/adb, tree/screenshot, Blazor CDP, and iterative UI debugging. DO NOT USE FOR: first-time setup or non-MAUI automation. INVOKES: DevFlow `maui_*` MCP tools when available; `maui devflow` CLI as fallback; `dotnet`, `adb`, and `simctl` for build, deployment, and connectivity work.dotnet/maui-labs224
- Maui Devflow DebugRun DevFlow inspect-and-fix loops for MAUI apps. USE FOR: launch, device selection, agent recovery, broker/port/adb, tree/screenshot, Blazor CDP, and iterative UI debugging. DO NOT USE FOR: first-time setup or non-MAUI automation. INVOKES: DevFlow `maui_*` MCP tools when available; `maui devflow` CLI as fallback; `dotnet`, `adb`, and `simctl` for build, deployment, and connectivity work.dotnet/maui-labs224
- Maui Devflow OnboardAdd MAUI DevFlow to a .NET MAUI project with agent package references, MauiProgram.cs registration, Blazor WebView support, GTK variants, Central Package Management guidance, and verification commands. USE FOR: first-time DevFlow setup, reviewing what files to edit, choosing DevFlow packages, or continuing after `maui devflow init` installs skills. DO NOT USE FOR: troubleshooting an already-integrated app that cannot connect, iterative app debugging, UI inspection, or generic MAUI build failuresdotnet/maui-labs224
- Maui Devflow OnboardAdd DevFlow to a MAUI app. USE FOR: package refs, `MauiProgram` registration, Blazor WebView/GTK variants, verification after `maui devflow init`. DO NOT USE FOR: troubleshooting, debugging, UI inspection, or build failures. INVOKES: `maui devflow`, `dotnet`.dotnet/maui-labs224
- Maui Devflow Session ReviewReview past MAUI DevFlow sessions. USE FOR: DevFlow friction reports, classifying `maui_tap`/`maui_hittest`/`maui_screenshot`/`maui_cdp_webviews` issues vs app bugs, markdown Environment/Findings reports, scrubbed dotnet/maui-labs issue drafts, workaround summaries. Does not run live `maui devflow`. DO NOT USE FOR: fixing bugs, onboarding, live debugging, or memory search.dotnet/maui-labs224
- Maui Device CapabilitiesImplement MAUI device capabilities with permissions and platform declarations. USE FOR: camera/media/file pickers, durable file copies, geolocation, maps, contacts, Android manifest entries, iOS usage descriptions, runtime permission prompts, denied/cancelled flows. DO NOT USE FOR: notifications, auth, UI layout.dotnet/maui-labs224
- Maui Essentials AiAdopt `Microsoft.Maui.Essentials.AI` for local/on-device MAUI AI. USE FOR: Apple Intelligence chat, `IChatClient`, iOS/macOS/Mac Catalyst 26+ checks, fallback UI, `NLEmbeddingGenerator`, local tool invocation, privacy/offline UX. DO NOT USE FOR: source-generated tools, cloud-only AI, UI debugging.dotnet/maui-labs224
- Maui Labs Platform TargetingTarget MAUI Labs desktop backends from MAUI apps. USE FOR: Linux GTK4 head projects, `maui-linux-gtk4`, `maui-macos`, `maui-wpf`, net10 desktop setup, `UseMauiAppLinuxGtk4`, AppKit vs Mac Catalyst, parity planning. DO NOT USE FOR: backend implementation, handlers, Essentials services.dotnet/maui-labs224
- Maui Localization ThemingImplement MAUI localization and theming. USE FOR: RESX/AppResources, runtime culture switching, RTL/FlowDirection, platform language metadata, `AppThemeBinding`, `DynamicResource`, light/dark/system themes, `UserAppTheme`. DO NOT USE FOR: general layout, accessibility audits, icon/splash assets.dotnet/maui-labs224
- Maui Networking Offline DataBuild MAUI networking and offline data. USE FOR: typed `HttpClient`, JSON serialization, Android `10.0.2.2`, iOS simulator localhost, LAN/dev-tunnel fallback, debug cleartext, offline-first screens, SQLite/EF Core sync metadata, queues, encryption decisions, retries, cancellation. DO NOT USE FOR: auth redirects, Aspire service discovery, UI layout.dotnet/maui-labs224
- Maui Notifications Deep LinksImplement MAUI notifications and deep links. USE FOR: local/push notifications, FCM HTTP v1 migration, APNs/Azure Notification Hubs, permission UX, Android channels/`POST_NOTIFICATIONS`, iOS `UNUserNotificationCenter`, token lifecycle, notification tap navigation, app links/universal links/URI schemes. DO NOT USE FOR: OAuth callbacks, generic Shell navigation, picker/location permissions.dotnet/maui-labs224
- Maui PerformanceFix measurable MAUI performance issues. USE FOR: `maui profile startup`, Release/physical-device measurements, janky `CollectionView`, compiled bindings, oversized images, `MauiImage` `BaseSize`, thumbnail decoding, trim/NativeAOT regressions, IL2026, source-generated serializers, linker validation. DO NOT USE FOR: generic UI bugs, workload discovery, architecture-only work.dotnet/maui-labs224
- Maui Platform BackendGuide .NET MAUI backend implementation for new platforms (GTK, AppKit, Avalonia, TUI, etc.) in the dotnet/maui-labs repository. USE FOR: creating a new MAUI backend, implementing a control handler, adding Essentials services, setting up build targets, scaffolding project structure, debugging handler rendering with DevFlow. DO NOT USE FOR: building or running existing MAUI apps (use maui-devflow-debug skill), DevFlow CLI/MCP tool development (see AGENTS.md). INVOKES: GitHub MCP tools for referencdotnet/maui-labs224
- Maui Platform InvokeAdd native platform APIs through MAUI services and lifecycle hooks. USE FOR: DI wrappers, permissions, AndroidManifest.xml, Info.plist, entitlements, partial platform files, `ConfigureLifecycleEvents`, choosing services vs handlers vs bindings. DO NOT USE FOR: visual handlers, native SDK bindings, backend.dotnet/maui-labs224
- Maui Project StructureConfigure MAUI single-project structure. USE FOR: app icons/splash screens, resource folders, images/fonts/raw assets, app display/build versioning, Central Package Management, platform metadata files, `AndroidManifest.xml`, `Info.plist`, package IDs/app identifiers. DO NOT USE FOR: UI debugging, workload discovery, MVVM/Shell architecture.dotnet/maui-labs224
- Maui Release NotesTurn official .NET/MAUI release notes into an app upgrade plan. USE FOR: breaking-change summaries, Xcode/JDK/Android SDK requirements, global.json/workload/package updates, CI image changes, migration checklists, validation plans, live version lookup. DO NOT USE FOR: authoring workload release notes or marketing copy.dotnet/maui-labs224
- Maui Ui PatternsFix MAUI UI layout, state, and automation issues. USE FOR: `CollectionView` scrolling, DataTemplate bindings, command bindings, Grid/FlexLayout sizing, binding-driven states, avoiding `ScrollView` parents, stable AutomationIds, `x:DataType`, EmptyView/loading/error states. DO NOT USE FOR: Shell routes, full accessibility, vendor-specific controls.dotnet/maui-labs224
- Maui Unit TestingAdd MAUI app tests around ViewModels, services, platform abstractions, and unit/integration/device boundaries. USE FOR: xUnit, avoiding `MauiProgram.CreateMauiApp` in unit tests, fakes/mocks, injectable Essentials interfaces, `PlatformNotSupportedException`, navigation/data services, AppProjectReference, device-test decisions. DO NOT USE FOR: UI automation or profiling.dotnet/maui-labs224
- Project ConventionsCore conventions and patterns for this codebasedotnet/maui-labs224
- Project ConventionsCore conventions and patterns for this codebasedotnet/maui-labs224
- Release ProcessStep-by-step release checklist for Squad — prevents v0.8.22-style disastersdotnet/maui-labs224
- Release ProcessStep-by-step release checklist for Squad — prevents v0.8.22-style disastersdotnet/maui-labs224
- ReskillTeam-wide charter and history optimization through skill extractiondotnet/maui-labs224
- ReskillTeam-wide charter and history optimization through skill extractiondotnet/maui-labs224
- Reviewer ProtocolReviewer rejection workflow and strict lockout semanticsdotnet/maui-labs224
- Reviewer ProtocolReviewer rejection workflow and strict lockout semanticsdotnet/maui-labs224
- Secret HandlingNever read .env files or write secrets to .squad/ committed filesdotnet/maui-labs224
- Secret HandlingNever read .env files or write secrets to .squad/ committed filesdotnet/maui-labs224
- Session RecoveryFind and resume interrupted Copilot CLI sessions using session_store queriesdotnet/maui-labs224
- Session RecoveryFind and resume interrupted Copilot CLI sessions using session_store queriesdotnet/maui-labs224
- Squad ConventionsCore conventions and patterns used in the Squad codebasedotnet/maui-labs224
- Squad ConventionsCore conventions and patterns used in the Squad codebasedotnet/maui-labs224
- Test DisciplineUpdate tests when changing APIs — no exceptionsdotnet/maui-labs224
- Test DisciplineUpdate tests when changing APIs — no exceptionsdotnet/maui-labs224
- Verification ProtocolMandatory end-to-end verification for .NET MAUI and Comet app tasks. Enforces dependency ownership — broken tools and missing config are YOUR problem to fix, not blockers to report. USE FOR: any task touching UI, pages, navigation, services, or app behavior. Triggers: after code changes, before marking todos done, when reporting task results, when a tool fails. DO NOT USE FOR: documentation-only changes, squad config edits, or build system changes that don't affect the running app.dotnet/maui-labs224
- Windows CompatibilityCross-platform path handling and command patternsdotnet/maui-labs224
- Windows CompatibilityCross-platform path handling and command patternsdotnet/maui-labs224
- Xamarin Forms MigrationPlan Xamarin.Forms to MAUI migrations. USE FOR: audits, fresh `dotnet new maui`, namespace updates, `DependencyService` to DI, `MessagingCenter` replacement, renderer triage, `MauiProgram`, permissions, parity planning. DO NOT USE FOR: brand-new MAUI apps, native SDK bindings, backend.dotnet/maui-labs224
- Update Integration TestsUpdate the integration tests in this repository after a .NET preview1 or GA release. Use this skill when asked to update tests for a new .NET version release, when an issue mentions updating integration tests for a .NET release, or when test failures indicate a new .NET version has shipped and tests are out of date.dotnet/install-scripts213
- Validate Install ScriptsOpen validation PRs in key .NET repos to test install script changes against their CI. Use this skill when asked to validate install scripts, open validation PRs, or check/close validation PRs. Supports two modes: 'open' (create PRs) and 'check-close' (verify CI and close).dotnet/install-scripts213
- Address ReviewAddress all code review comments on a PR. Assesses each comment, replies, reacts, and resolves threads.dotnet/nuget-trends188
- Pr Failure ScanAnalyze a dotnet/xharness pull request's CI failures: isolate the failures Build Analysis did not already recognize, search existing repository issues for matches, assess whether each failure is likely caused by the PR, and draft a single AI-generated triage comment for explicit approval before posting. Use this skill whenever the user wants to triage, investigate, or analyze a dotnet/xharness PR's CI, build, or test failures, mentions Build Analysis misses or pipelines excluded from Build Analydotnet/xharness188
- Docs MaintenanceReviews or updates repository documentation as a dedicated task after implementation is complete. Use before submitting a pull request or when reviewing a pull request.dotnet/docker-tools181
- Investigating PipelineDiagnoses a single Azure Pipelines build. Shows the build timeline tree with stages, jobs, and task results, and retrieves task logs for debugging failures. Use when a user provides a build ID or Azure DevOps build URL and wants to understand what failed and why.dotnet/docker-tools181
- Investigating Pull RequestInspect GitHub pull request status, read review comments, and diagnose PR validation failures. Use when the user wants to check the status of a pull request or diagnose PR validation failures.dotnet/docker-tools181
- Reviewing CsharpReviews C# changes in the ImageBuilder codebase against the repo's modern C# conventions and invariants. Use when reviewing a C# diff, pull request, or staged/unstaged changes and you want anti-patterns caught before merge.dotnet/docker-tools181
- Triaging PipelinesTriage recent Azure Pipelines runs and failures.dotnet/docker-tools181
- Triaging Pull RequestsTriage open pull requests into actionable categories.dotnet/docker-tools181
- Dotnet Buildtools Prereqs Docker Analyze Official BuildAnalyze supplied evidence for a dotnet-buildtools-prereqs-docker official image build failure, or inspect repository-only context, and return read-only findings and proposed next steps. Use for diagnosis or investigation without live queries, credentials, code execution, edits, builds, pipeline operations, or publication. Not the end-to-end repair workflow.dotnet/dotnet-buildtools-prereqs-docker88
- Dotnet Buildtools Prereqs Docker Fix Official BuildRepair failures in the dotnet-buildtools-prereqs-docker Azure DevOps image build, validate with the unofficial test pipeline, and open the appropriate GitHub pull request after the Build stage succeeds. Use only for an explicit request for this end-to-end repair workflow, not read-only investigation or supplied-evidence analysis; those use dotnet-buildtools-prereqs-docker-analyze-official-build.dotnet/dotnet-buildtools-prereqs-docker88
- Add Darc CommandAdd a new command (verb) to the DARC CLI. Use when asked to "add a darc command", "create a new darc verb", "add a darc operation", or extend the darc tool with a new subcommand.dotnet/arcade-services87
- Arcade Services Failed Work ItemsList failed Product Construction Service (PCS/Maestro) work items in a time window and summarize retry-exhausted operations. Use for "list failed work items", "summarize PCS failures", or "what failed in Maestro". Teams-free and read-only; use arcade-services-work-item-analysis for root-cause investigation.dotnet/arcade-services87
- Arcade Services Work Item AnalysisAnalyze one failed PCS/Maestro work item by operation ID, correlate exceptions and traces with repository source, and offer a local fix, PR, further analysis, or issue creation. Use for "why did this work item fail" or "analyze this PCS operation". Teams-free; read-only until an explicit follow-up decision.dotnet/arcade-services87
- Arcade Services Work Item Analysis TeamsInvestigate a PCS/Maestro failure alert or selected failed work item and post findings to its Teams alert thread. Use for "investigate the Maestro alert and post findings", "reply to the pcs-workitem-failure-alert", or "analyze this work item and post to Teams". Reuses the Teams-free listing and analysis skills.dotnet/arcade-services87
- Setup Dev EnvironmentSet up an arcade-services local development environment from zero by following docs/DevGuide.md. Use when asked to "set up my dev environment", "bootstrap local development", "get me running locally", or "configure the repo for local dev". Runs the automatable steps, verifies prerequisites, and flags the human-gated ones.dotnet/arcade-services87
- Cleanup Unreferenced PackagesIntelligently removes unreferenced packages from source-build-assets (SBA). Accounts for pending-uptake packages, dependency graphs, and flow timing between SBA and the VMR.dotnet/source-build-assets54
- Android Tools ReviewerReview pull requests for dotnet/android-tools using lessons from past code reviews. Trigger when the user says "review this" with a GitHub PR URL, asks to review a PR, or wants code review feedback. Fetches the diff, checks it against established rules (netstandard2.0, async, security, error handling, patterns, performance), and posts a batched 🤖-prefixed review via gh CLI.dotnet/android-tools40