electron-app-stinger

Guides secure Electron application development across main, preload, and renderer process boundaries.

84|37|Updated May 23, 2026
One-click install
npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill electron-app-stinger-legioncodeinc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: electron-app-stinger
Source: https://github.com/legioncodeinc/vibe-coding-tools/tree/main/src/skills/electron-app-stinger
Command: npx skills add https://github.com/legioncodeinc/vibe-coding-tools --skill electron-app-stinger-legioncodeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about electron-app-stinger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure IPC between Electron main and renderer processes?▼

Pair a named ipcMain.handle channel with a single preload method that calls ipcRenderer.invoke for that channel only. Never expose the whole ipcRenderer object or forward event objects, and re-validate all payloads in the main process.

How to expose Node APIs safely to an Electron renderer?▼

Use a preload script with contextBridge.exposeInMainWorld to expose one narrow method per allowed native action. Keep Node integration disabled for any renderer loading remote content and preserve context isolation.

Should I use Electron or Tauri for a desktop app?▼

Electron suits apps needing the mature Node and Chromium ecosystem with established packaging and update tooling. Tauri is an alternative desktop boundary covered by a separate skill when a Rust-based, smaller-footprint shell is preferred.

Why is Node integration dangerous in Electron renderers?▼

Node integration in a renderer loading remote content lets an XSS vulnerability escalate into arbitrary code execution on the user's machine. Electron's official security guidance says to disable it and use preload with contextBridge instead.

When should I not use this Electron skill?▼

Do not use it for reverse engineering third-party Electron apps, which belongs to separate dissection material, or for Tauri-specific desktop work. Generic TypeScript or frontend design questions should go to the relevant language or UI skill.