| name | electron |
| description | Build cross-platform desktop applications with Electron, covering main/renderer process architecture, IPC communication, BrowserWindow management, menus, tray icons, packaging, and security best practices. Use when the user asks about Electron, needs to create desktop applications, implement Electron features, or build cross-platform desktop apps. |
| license | Complete terms in LICENSE.txt |
When to use this skill
Use this skill whenever the user wants to:
- Build cross-platform desktop applications with Electron
- Understand Electron architecture (main process, renderer process, preload)
- Implement IPC (Inter-Process Communication) between processes
- Create and manage BrowserWindow instances
- Implement menus, tray icons, and native features
- Package and distribute Electron applications
- Use Electron Forge for project scaffolding and building
- Debug and test Electron applications
- Implement security best practices
- Use Electron APIs (app, BrowserWindow, ipcMain, ipcRenderer, etc.)
How to use this skill
This skill is organized to match the Electron official documentation structure (https://www.electronjs.org/zh/docs/latest/, https://www.electronjs.org/zh/docs/latest/api/app). When working with Electron:
-
Identify the topic from the user's request:
- Getting started/ๅฟซ้ๅผๅง โ
examples/getting-started/installation.md or examples/getting-started/quick-start.md
- Main process/ไธป่ฟ็จ โ
examples/processes/main-process.md
- Renderer process/ๆธฒๆ่ฟ็จ โ
examples/processes/renderer-process.md
- IPC communication/IPC ้ไฟก โ
examples/processes/ipc-communication.md
- BrowserWindow/็ชๅฃ โ
examples/api/browser-window.md
- Menu/่ๅ โ
examples/api/menu.md
- Packaging/ๆๅ
โ
examples/advanced/packaging.md
- Security/ๅฎๅ
จ โ
examples/advanced/security.md
-
Load the appropriate example file from the examples/ directory:
Getting Started (ๅฟซ้ๅผๅง) - examples/getting-started/:
examples/getting-started/installation.md - Installing Electron and basic setup
examples/getting-started/quick-start.md - Quick start tutorial
Processes (่ฟ็จ) - examples/processes/:
examples/processes/main-process.md - Main process concepts and usage
examples/processes/renderer-process.md - Renderer process concepts
examples/processes/preload-scripts.md - Preload scripts usage
examples/processes/ipc-communication.md - IPC communication patterns
API Examples (API ็คบไพ) - examples/api/:
examples/api/browser-window.md - BrowserWindow usage
examples/api/menu.md - Menu and context menu
examples/api/tray.md - System tray
examples/api/dialog.md - File dialogs
examples/api/ipc-main.md - ipcMain usage
examples/api/ipc-renderer.md - ipcRenderer usage
Advanced (้ซ็บง) - examples/advanced/:
examples/advanced/packaging.md - Application packaging
examples/advanced/security.md - Security best practices
examples/advanced/auto-updater.md - Auto updater
examples/advanced/native-modules.md - Native modules
Tools (ๅทฅๅ
ท) - examples/tools/:
examples/tools/electron-forge.md - Electron Forge usage
examples/tools/electron-fiddle.md - Electron Fiddle usage
-
Follow the specific instructions in that example file for syntax, structure, and best practices
Important Notes:
- All examples follow Electron latest API
- Examples use both CommonJS (require) and ES modules (import)
- Each example file includes key concepts, code examples, and key points
- Always check the example file for best practices and common patterns
- Electron supports Windows, macOS, and Linux
-
Reference API documentation in the api/ directory when needed:
api/app.md - app module API
api/browser-window.md - BrowserWindow API
api/ipc-main.md - ipcMain API
api/ipc-renderer.md - ipcRenderer API
api/menu.md - Menu API
api/tray.md - Tray API
-
Use templates from the templates/ directory:
templates/main-process.md - Main process template
templates/preload-script.md - Preload script template
templates/renderer-process.md - Renderer process template
templates/package-json.md - package.json template
Doc mapping (one-to-one with official documentation)
Quick Start Example
const { app, BrowserWindow, ipcMain } = require('electron')
const path = require('path')
function createWindow() {
const win = new BrowserWindow({
width: 800, height: 600,
webPreferences: {
preload: path.join(__dirname, 'preload.js'),
nodeIntegration: false,
contextIsolation: true
}
})
win.loadFile('index.html')
}
app.whenReady().then(createWindow)
ipcMain.handle('get-data', async () => {
return { message: 'Hello from main process' }
})
const { contextBridge, ipcRenderer } = require('electron')
contextBridge.exposeInMainWorld('api', {
getData: () => ipcRenderer.invoke('get-data')
})
API Reference (api/)
api/app.md - app module API
api/browser-window.md - BrowserWindow API
api/ipc-main.md / api/ipc-renderer.md - IPC APIs
api/menu.md / api/tray.md / api/dialog.md - UI APIs
Best Practices
- Security: Never enable nodeIntegration in renderer process, use preload scripts
- Process separation: Keep main and renderer processes separate
- IPC communication: Use IPC for safe communication between processes
- Resource management: Properly clean up resources (windows, listeners)
- Error handling: Implement proper error handling and crash reporting
- Performance: Optimize for performance, use webContents for debugging
- Packaging: Use Electron Forge or electron-builder for packaging
- Auto updates: Implement auto-updater for production apps
- Native modules: Handle native module compatibility
- Cross-platform: Test on all target platforms
Resources
Keywords
Electron, desktop app, main process, renderer process, preload, IPC, BrowserWindow, Menu, Tray, Dialog, packaging, electron-builder, electron-forge, electron-fiddle, cross-platform, ๆก้ขๅบ็จ, ไธป่ฟ็จ, ๆธฒๆ่ฟ็จ, IPC ้ไฟก, ็ชๅฃ, ่ๅ, ๆ็, ๆๅ