.NET MAUI — Deployment Skill
Purpose
This skill provides agents with best practices, workflows, and platform-specific guidance for building, packaging, signing, and distributing .NET MAUI applications. It covers Android, iOS, Windows, and MacCatalyst deployment, along with CI/CD recommendations.
The goal is to ensure that all deployment-related tasks follow secure, repeatable, and production-ready patterns.
Core Principles
- Platform correctness
Each platform has unique signing, packaging, and provisioning requirements.
- Security
Protect signing keys, certificates, and provisioning profiles.
- Automation
Prefer CI/CD pipelines for consistent builds.
- Environment separation
Use different configurations for Debug, Release, and Store builds.
- Repeatability
Deployment steps should be deterministic and documented.
Supported Deployment Targets
- Android (APK, AAB)
- iOS (IPA)
- Windows (MSIX)
- MacCatalyst (App bundle)
Recommended Folder Structure
/Deployment
/Deployment/Android
/Deployment/iOS
/Deployment/Windows
/Deployment/Mac
/Deployment/CI-CD
Agent Usage Guidelines
- When asked to “build for Android,” generate:
- Release build commands
- Signing instructions
- AAB packaging steps
- When asked to “deploy to iOS,” include:
- Provisioning profile requirements
- Certificate usage
- IPA packaging
- When asked to “create a CI pipeline,” generate:
- GitHub Actions or Azure DevOps YAML
- Environment variable usage
- Secure secrets handling
- When asked to “prepare a store build,” apply:
- Release configuration
- AOT (where supported)
- Optimized linking
Out of Scope
- Backend deployment
- UI design
- Authentication logic
1---2name: maui-deployment3description: A brief description of what this skill does4---56# .NET MAUI — Deployment Skill78## Purpose910This skill provides agents with best practices, workflows, and platform-specific guidance for building, packaging, signing, and distributing .NET MAUI applications. It covers Android, iOS, Windows, and MacCatalyst deployment, along with CI/CD recommendations.1112The goal is to ensure that all deployment-related tasks follow secure, repeatable, and production-ready patterns.1314## Core Principles15161. **Platform correctness**17 Each platform has unique signing, packaging, and provisioning requirements.182. **Security**19 Protect signing keys, certificates, and provisioning profiles.203. **Automation**21 Prefer CI/CD pipelines for consistent builds.224. **Environment separation**23 Use different configurations for Debug, Release, and Store builds.245. **Repeatability**25 Deployment steps should be deterministic and documented.2627## Supported Deployment Targets2829- Android (APK, AAB)30- iOS (IPA)31- Windows (MSIX)32- MacCatalyst (App bundle)3334## Recommended Folder Structure3536```text37/Deployment38/Deployment/Android39/Deployment/iOS40/Deployment/Windows41/Deployment/Mac42/Deployment/CI-CD43```4445## Agent Usage Guidelines4647- When asked to “build for Android,” generate:48 - Release build commands49 - Signing instructions50 - AAB packaging steps51- When asked to “deploy to iOS,” include:52 - Provisioning profile requirements53 - Certificate usage54 - IPA packaging55- When asked to “create a CI pipeline,” generate:56 - GitHub Actions or Azure DevOps YAML57 - Environment variable usage58 - Secure secrets handling59- When asked to “prepare a store build,” apply:60 - Release configuration61 - AOT (where supported)62 - Optimized linking6364## Out of Scope6566- Backend deployment67- UI design68- Authentication logic
rimblehelm