rimblehelm/.net-maui-skills · Archived

maui-deployment

A brief description of what this skill does

First seen Jan 27, 2026

Installation

$ npx skills add rimblehelm/.net-maui-skills --skill maui-deployment

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from rimblehelm/.net-maui-skills.

npx skills add rimblehelm/.net-maui-skills

Browse all from rimblehelm/.net-maui-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Also listed on

Alternate registries and mirrors of this skill.

Repository health

Default branch master
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,858 B
  • docs SUMMARY.md 66 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 5 installs

SKILL.md

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

  1. Security

Protect signing keys, certificates, and provisioning profiles.

  1. Automation

Prefer CI/CD pipelines for consistent builds.

  1. Environment separation

Use different configurations for Debug, Release, and Store builds.

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