Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Review the packaged build of [desktop app] for [target operating system]. Its essential journeys are [list].
Check launch, required runtime dependencies, asset paths, file associations, supported file locations, and the app's window or process exit behavior. Exercise a real document save and reopen, an invalid file, and an unwritable destination. Check keyboard access and the relevant scaling configuration.
Use an appropriate clean test environment where available. Report the exact build or artifact tested, observed outcomes, and any missing device or installation check. Identify signing, update, and recovery requirements without treating successful packaging as proof that the user journey works.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
- Electron — Application packaging and distribution
- Electron — Desktop application code signing
- Microsoft — Handling file activation
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted release checklist. Packaging, signing, and packaged resource locations have primary support; it does not assert that a development run validates a release.