npx skills add smithery/rimblehelm --skill maui-deployment
rimblehelm/.net-maui-skills · Archived
maui-deployment
A brief description of what this skill does
Installation
npx skills add rimblehelm/.net-maui-skills --skill maui-deployment
Stronger alternatives
This repository is archived — consider an actively maintained alternative.
Defines recommended UI/UX patterns, layout strategies, styling conventions, accessibility rules…
40 installsA brief description of what this skill does
11 installsA brief description of what this skill does
9 installsA brief description of what this skill does
7 installsSimilar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsAlso in this package
Other skills from rimblehelm/.net-maui-skills.
npx skills add 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.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
master
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,858 B -
docs
SUMMARY.md66 B
History
- First seen on skills.sh
- 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
- 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