electron-development

Builds Electron apps with secure IPC, preload whitelisting, and signed packaging workflows.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/NAMEWTA/electron-template-v3-vite --skill electron-development-namewta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: electron-development
Source: https://github.com/NAMEWTA/electron-template-v3-vite/tree/main/.agents/skills/electron-development
Command: npx skills add https://github.com/NAMEWTA/electron-template-v3-vite --skill electron-development-namewta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds secure, production-grade Electron apps by enforcing strict IPC and security patterns across main, preload, and renderer processes.

Core Features & Use Cases

  • Secure IPC with explicit preload whitelisting and contextIsolation
  • Multi-process architecture with main, preload, and renderer boundaries
  • Packaging, code signing, and auto-update workflows using electron-builder
  • Comprehensive security hardening, CSP headers, and safe navigation policies

Quick Start

Create a new Electron project, implement a lean main process, a secure preload script with contextBridge, and connect the renderer via a whitelisted IPC API.

Frequently Asked Questions about electron-development

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

FAQPage Schema
How do I secure IPC communication in an Electron app?

Secure IPC in Electron requires explicit preload whitelisting and contextIsolation to enforce strict boundaries between main, preload, and renderer processes.

What is the best way to set up a secure Electron preload script?

The best way to set up a secure Electron preload script is using contextBridge to expose a tightly whitelisted IPC API to the renderer.

How do I configure auto-update and code signing for desktop packaging?

You can configure auto-update and code signing for desktop packaging by using electron-builder to enforce signed distribution and robust update workflows.

Why does my Electron app need CSP headers and safe navigation policies?

Your Electron app needs CSP headers and safe navigation policies as mandatory security hardening defaults to prevent unauthorized resource loading and cross-process exploitation.

How do I manage state across main and renderer processes in Electron?

Managing state across Electron processes requires defining explicit multi-process architecture boundaries with main, preload, and renderer layers to handle robust state synchronization.

Can I use electron-builder for cross-platform desktop distribution?

Yes, you can use electron-builder for cross-platform desktop distribution to handle packaging, code signing, and auto-update workflows across different operating systems.