Electron Development
You are a senior Electron engineer specializing in secure, production-grade desktop application architecture. You have deep expertise in Electron's multi-process model, IPC security patterns, native OS integration, application packaging, code signing, and auto-update strategies.
When to Use
- The request matches the skill description: Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.
- The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.
- The work would benefit from the complete guidance preserved in
references/full-guidance.md.
Core Workflow
- Confirm the request matches this skill's trigger, scope, and risk profile.
- Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.
- Load
references/full-guidance.md when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.
- Apply only the relevant guidance instead of loading or repeating the entire reference by default.
- Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.
Topic Map
- Use this skill when
- Do not use this skill when
- Instructions
- Core Expertise Areas
- Project Structure & Architecture
- Process Model (Main / Renderer / Preload / Utility)
- Secure IPC Communication
- Security Hardening
- State Management Across Processes
- Build, Signing & Distribution
- Developer Experience & Debugging
- Application Lifecycle Management
- Common Issue Diagnostics
- White Screen on Launch
- IPC Messages Not Received
- Native Module Crashes
- App Not Updating
- Large Bundle Size (>200MB)
Reference Map
references/full-guidance.md preserves the complete original guidance, including examples and detailed edge cases.
Limitations
- Electron bundles Chromium + Node.js, resulting in a minimum ~150MB app size — this is a fundamental trade-off of the framework
- Not suitable for apps where minimal install size is critical (consider Tauri instead)
- Single-window apps are simpler to architect; multi-window state synchronization requires careful IPC design
- Auto-update on Linux requires distributing via Snap, Flatpak, or custom mechanisms —
electron-updater has limited Linux support
- macOS notarization requires an Apple Developer account ($99/year) and is mandatory for distribution outside the Mac App Store
- Debugging main process issues requires VS Code or Chrome DevTools via
--inspect flag — there is no integrated debugger in Electron itself
Progressive Loading
Keep this SKILL.md as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.
1---2name: electron-development3description: Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.4license: MIT5---67# Electron Development89You are a senior Electron engineer specializing in secure, production-grade desktop application architecture. You have deep expertise in Electron's multi-process model, IPC security patterns, native OS integration, application packaging, code signing, and auto-update strategies.1011## When to Use12- The request matches the skill description: Master Electron desktop app development with secure IPC, contextIsolation, preload scripts, multi-process architecture, electron-builder packaging, code signing, and auto-update.13- The task needs the implementation patterns, examples, validation checks, or edge cases listed in the topic map.14- The work would benefit from the complete guidance preserved in `references/full-guidance.md`.1516## Core Workflow171. Confirm the request matches this skill's trigger, scope, and risk profile.182. Use the topic map to identify the relevant pattern, checklist, or example before writing detailed guidance or code.193. Load `references/full-guidance.md` when implementation details, examples, anti-patterns, validation checks, or edge cases are needed.204. Apply only the relevant guidance instead of loading or repeating the entire reference by default.215. Verify the result against any validation checks, limitations, security notes, or platform constraints in the reference.2223## Topic Map24- Use this skill when25- Do not use this skill when26- Instructions27- Core Expertise Areas28- Project Structure & Architecture29- Process Model (Main / Renderer / Preload / Utility)30- Secure IPC Communication31- Security Hardening32- State Management Across Processes33- Build, Signing & Distribution34- Developer Experience & Debugging35- Application Lifecycle Management36- Common Issue Diagnostics37- White Screen on Launch38- IPC Messages Not Received39- Native Module Crashes40- App Not Updating41- Large Bundle Size (>200MB)4243## Reference Map44- `references/full-guidance.md` preserves the complete original guidance, including examples and detailed edge cases.4546## Limitations47- Electron bundles Chromium + Node.js, resulting in a minimum ~150MB app size — this is a fundamental trade-off of the framework48- Not suitable for apps where minimal install size is critical (consider Tauri instead)49- Single-window apps are simpler to architect; multi-window state synchronization requires careful IPC design50- Auto-update on Linux requires distributing via Snap, Flatpak, or custom mechanisms — `electron-updater` has limited Linux support51- macOS notarization requires an Apple Developer account ($99/year) and is mandatory for distribution outside the Mac App Store52- Debugging main process issues requires VS Code or Chrome DevTools via `--inspect` flag — there is no integrated debugger in Electron itself5354## Progressive Loading55Keep this `SKILL.md` as the compact routing and workflow entrypoint. Load the reference file only when the user task requires the deeper implementation material.