electron-desktop-app

Configure secure Electron apps with strict IPC boundaries and contextIsolation.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/StevenWXY/Project-Sibylla --skill electron-desktop-app
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: electron-desktop-app
Source: https://github.com/StevenWXY/Project-Sibylla/tree/main/.kilocode/skills/phase0/electron-desktop-app
Command: npx skills add https://github.com/StevenWXY/Project-Sibylla --skill electron-desktop-app

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Electron desktop app development often struggles with securing the main/renderer separation, safe exposure of APIs, and reliable update mechanisms across platforms. This skill provides comprehensive best practices for architecture, security, native module integration, auto-updates, and cross-platform packaging.

Core Features & Use Cases

  • Architectural guidance for main and renderer processes with strict IPC boundaries.
  • Security best practices including contextIsolation, nodeIntegration, and preload with contextBridge.
  • Auto-update & packaging guidance using electron-updater and electron-builder.
  • Cross-platform considerations for macOS, Windows, and Linux deployment.

Quick Start

Set up a new Electron project with secure main/renderer separation and start the app.

Frequently Asked Questions about electron-desktop-app

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

FAQPage Schema
How do I secure IPC boundaries between the main and renderer processes in an Electron app?▼

To secure Electron IPC boundaries, you should enable contextIsolation and disable nodeIntegration, using a preload script with contextBridge to safely expose only necessary APIs to the renderer process.

What is the best way to set up reliable auto-updates for a cross-platform Electron desktop app?▼

Reliable Electron auto-updates are best implemented using electron-updater paired with electron-builder, which manages cross-platform packaging and scalable distribution across macOS and Windows.

Does contextIsolation prevent me from using Node.js modules directly in my Electron renderer process?▼

Yes, contextIsolation prevents direct Node.js access in the renderer, requiring you to wire a preload script using contextBridge to securely expose specific native functionalities.

How do I package an Electron app for cross-platform deployment on macOS and Windows?▼

Packaging an Electron app for macOS and Windows involves using electron-builder to configure cross-platform build targets, ensuring native module integration and scalable distribution are handled correctly.

Why should I use a preload script with contextBridge instead of enabling nodeIntegration in Electron?▼

Using a preload script with contextBridge is a security best practice because it maintains strict main/renderer separation, whereas enabling nodeIntegration exposes dangerous native capabilities directly to the renderer.

Can I integrate native modules when building a cross-platform Electron desktop app?▼

Yes, native module integration is supported during Electron desktop app development, with architectural guidance provided to ensure compatibility alongside strict IPC boundaries and cross-platform packaging.