# maui-deployment

> A brief description of what this skill does

- Author: Rimblehelm
- Repository: Rimblehelm/.NET-MAUI-Skills
- Version: 20260127084330
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-06
- Source: https://github.com/Rimblehelm/.NET-MAUI-Skills
- Web: https://mule.run/skillshub/@@Rimblehelm/.NET-MAUI-Skills~maui-deployment:20260127084330

---

---
name: maui-deployment
description: A brief description of what this skill does
---

# .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

1. **Platform correctness**
   Each platform has unique signing, packaging, and provisioning requirements.
2. **Security**
   Protect signing keys, certificates, and provisioning profiles.
3. **Automation**
   Prefer CI/CD pipelines for consistent builds.
4. **Environment separation**
   Use different configurations for Debug, Release, and Store builds.
5. **Repeatability**
   Deployment steps should be deterministic and documented.

## Supported Deployment Targets

- Android (APK, AAB)
- iOS (IPA)
- Windows (MSIX)
- MacCatalyst (App bundle)

## Recommended Folder Structure

```text
/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