Skip to content

aalmada/Stationary / .agents/skills/dotnet-maui

dotnet-maui

Verified

Build, architect, debug, test, and publish .NET MAUI 10 cross-platform native apps for Android, iOS, Mac Catalyst, and Windows using C#, XAML, or C# markup. USE FOR: MAUI project configuration, single-project targeting, pages, layouts, controls, XAML, MVVM, data binding, CommunityToolkit.Mvvm, dependency injection, Shell navigation, handlers, platform integration, permissions, lifecycle, accessibility, localization, performance, trimming, Appium UI tests, Android/iOS/Windows publishing. DO NOT USE FOR: ASP.NET Core web UI, Blazor-only apps, Avalonia, WPF-only, Xamarin.Forms migration without MAUI target code, or generic .NET code with no MAUI UI or platform concern.

references/deployment-and-publishing.md

View on GitHub
# Deployment And Publishing

## Release Workflow

1. Build a Release configuration for each target framework and inspect warnings, especially trimming warnings.
2. Set unique application identifiers, version name/display version, build version, icons, splash screens, and privacy/store metadata.
3. Configure signing and provisioning through secure CI secrets or platform credential stores; never commit certificates, profiles, or passwords.
4. Install the signed package on physical devices and test upgrades, permissions, deep links, offline use, lifecycle transitions, and failure recovery.
5. Submit the platform package only after it passes the appropriate store validation.

## Platform Outputs

| Target | Distribution Artifact | Release Considerations |
| --- | --- | --- |
| Android | AAB for stores; APK for direct installation | Signing key, manifest permissions, Play requirements |
| iOS | IPA | macOS build host, signing certificate, provisioning profile, App Store requirements |
| Mac Catalyst | APP or PKG | Signing, provisioning/capabilities, sandbox requirements |
| Windows | MSIX or unpackaged app | Package identity/signing for MSIX, Windows deployment requirements |

- Match the installed SDK/workload to CI and pin it as part of reproducible builds.
- Run final checks against the actual generated artifact, not a Debug deployment or a package assembled locally with different credentials.
- Maintain versioning rules that support store requirements and in-place upgrades.

## Sources

- [Deployment and testing](https://learn.microsoft.com/dotnet/maui/deployment/?view=net-maui-10.0)
- [Publish for Android](https://learn.microsoft.com/dotnet/maui/android/deployment/?view=net-maui-10.0)
- [Publish for iOS](https://learn.microsoft.com/dotnet/maui/ios/deployment/?view=net-maui-10.0)
- [Publish for Windows](https://learn.microsoft.com/dotnet/maui/windows/deployment/overview?view=net-maui-10.0)
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall