What problem does it solve? Turning a browser-based ignifx game into a desktop application normally requires wiring up Electron's main, preload, and renderer processes, enabling WebGPU flags, securing the window, and bridging storage — all with subtle ordering traps that fail silently. This Skill provides the complete @ignifx/electron workflow so one renderer bundle serves both browser and desktop builds. ## Core Features & Use Cases - Main-process window factory: createGameWindow, applyWebGpuSwitches, registerIgnifxScheme, and serveIgnifxProtocol set up a hardened WebGPU-capable window over the ignifx:// protocol. - Sandboxed preload bridge: exposeIgnifxHost() exposes window.ignifxHost as the entire renderer interface, with context isolation and strict CSP enforced by default. - Renderer extension: the electron() extension provides app.desktop (fullscreen, window events, dialogs, paths, quit) and a file-system StorageBackend for app.storage. - Use Case: Scaffold a game with npx @ignifx/cli my-game --template 3d-third-person --desktop, then run pnpm dev:desktop to get a hot-reloading desktop build, and pnpm dist:desktop for an unsigned packaged app. ## Quick Start Use the electron skill to package my ignifx game as a desktop app and set up the main, preload, and renderer entry points.