What problem does it solve?
Publishing an Electron desktop app to npm often results in broken installs, missing binaries, or users downloading the wrong artifacts across platforms and architectures.
Core Features & Use Cases
- Deterministic multi-phase release flow: runs an ordered workflow that prevents partial publishing mistakes by publishing sibling binaries before the root package.
- Per-OS/arch optionalDependencies launcher pattern: packages each platform build into a sibling npm package and pins exact versions from the root so installs resolve correctly.
- Builder detection with safety guardrails: auto-detects electron-builder vs electron-forge, refuses ambiguous setups, and blocks cross-compiling macOS from non-macOS hosts.
- Unpacked-artifact validation: verifies that builds produce unpacked application directories (not installers) before assembling the publishable npm packages.
Quick Start
Ask the skill to publish your Electron desktop app to the npm registry using the platform-specific sibling optionalDependencies launcher pattern.