What problem does it solve?
Modifying Electron desktop code risks breaking the privilege boundary between renderer and main process, flashing console windows on Windows, or regressing startup, updater, and deep-link behavior across packaged builds. This Skill enforces the architectural rules and validation steps needed to change the OpenChamber desktop shell safely.
Core Features & Use Cases
- Runtime Boundary Enforcement: Keeps renderer contracts in packages/ui, server behavior in packages/web, and Electron limited to native concerns like windows, menus, dialogs, notifications, updater, deep links, SSH, and tunnels.
- IPC and Security Rules: Gates privileged commands in the main process, exposes the narrowest preload bridge payloads, and prevents leaking filesystem, shell, tokens, or host secrets to remote pages.
- Windows Background Process Handling: Spawns hidden child processes with windowsHide, stdio ignore, and unref, avoiding cmd.exe shims that flash console windows.
- Use Case: When adding a new native notification capability, use this Skill to place the bridge in preload, handle the operation in main.mjs, gate the privileged command, and validate both HMR development and bundled builds.
Quick Start
Use the desktop-shell skill to add a new native menu action with a preload bridge and privileged main-process handler in the Electron package.