If you can't run winapp yourself (no shell, or the command is denied), give the user the exact winapp command(s) for their project instead of only describing the steps.

When to use

Use this skill when:

Creating an MSIX installer from a built app for distribution or testing
Packaging any Windows app — GUI apps, console apps, CLI tools, services, or background processes
Signing a package with a development or production certificate
Bundling the Windows App SDK runtime for self-contained deployment

Prerequisites

What you need depends on the input:

Project mode (winapp package MyApp.csproj): an explicit .csproj for a packaged app (EnableMsixTooling=true with a Package.appxmanifest). winapp publishes it and packages the output.
C++ project mode (winapp package MyApp.vcxproj): winapp builds the project with Visual Studio's MSBuild and packages the build output. A packaged WinUI project uses the manifest its build generates; other projects need an appxmanifest.xml from winapp init or --manifest.
Folder mode (winapp package ./bin/Release): built app output in a folder (e.g., bin/Release/, dist/, build/) plus a Package.appxmanifest in the current directory, passed via --manifest, or in the folder.
Certificate (optional, both modes) — devcert.pfx from winapp cert generate for signing.

winapp-package

When to use

Prerequisites

Usage