What problem does it solve? Electron apps often ship with unsafe defaults like Node integration on remote content or an exposed ipcRenderer, creating serious security holes. This Skill provides a structured procedure for designing, reviewing, and verifying a secure Electron process boundary before code ships. ## Core Features & Use Cases - Secure Process Boundary Design: Inventory every BrowserWindow, preload API, IPC channel, permission request, and navigation policy before making changes. - Narrow IPC Surface Enforcement: Expose only validated capability-shaped preload methods via contextBridge, never the full ipcRenderer or event objects. - Native Verification Workflow: Validate behavior in a running Electron app and packaged artifacts, distinguishing real desktop results from browser-only tests. - Use Case: When migrating a web app to Electron, use this Skill to audit each renderer origin, define one preload method per native action, and confirm deny paths work in a packaged build. ## Quick Start Use the electron-app-stinger skill to review my Electron app's main process, preload scripts, and IPC channels for security issues.