electron
Skill3 starsChanged 6 months agoMITView on GitHub
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.
21 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- full-stack-skills/electron-skillsedited, first seen Nov 8, 2026
- skillpie/ZCodeOnlinetheir own version, first seen Nov 5, 2026
- ZCodium-project/ZCodiumtheir own version, first seen Nov 1, 2026
- JunfengRan/dev-envtheir own version, first seen Oct 20, 2026
- foxl-ai/skillstheir own version, first seen Oct 15, 2026
- ccbud/CCBuddytheir own version, first seen Oct 14, 2026
Used with
Projects with it also use dep-refs, feature-boundary-planner and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
betacatslingSkilldep-refs
Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.
Also in 5 projects that use this
betacatslingSkillfeature-boundary-planner
Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.
Also in 5 projects that use this
Cartograf666Skillarchitecture-governance
Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.
Also in 5 projects that use this
ZCodium-projectSkille2e-case-lifecycle
Plan, maintain, replay, and promote ZCode desktop E2E cases and their fixtures, coverage matrices, and CI admission evidence.
Also in 3 projects that use this
ZCodium-projectSkillzcode-large-task-fixture
Generate, verify, or remove large synthetic ZCode task fixtures in local ~/.zcode persistence for UI/session performance testing. Use when testing big conversation/task rendering, task list performance, snapshot recovery, tool-call rendering, reasoning, patches, todos, and model usage without spending time chatting manually.
Also in 3 projects that use this
VercelSkillai-elements
Build AI chat interfaces using ai-elements components — conversations, messages, tool displays, prompt inputs, and more. Use when the user wants to build a chatbot, AI assistant UI, or any AI-powered chat interface.
Also in 5 projects that use this
Other versions21 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- 302ai/302-AI-Studio★ 13373% same
- full-stack-skills/electron-skills★ 877% same
Wrote their own version · 19
- vercel-labs/agent-browser★ 47ksame name
- zai-org/ZCode★ 8.6ksame name
- coder/cmux★ 2.1ksame name
- coder/mux★ 2.1ksame name
- phodal/routa★ 1.8ksame name
- opral/flashtype★ 292same name
- ZCodium-project/ZCodium★ 248same name
- G1Joshi/Agent-Skills★ 15same name
- intent-hq/cloudlands-fe★ 9same name
- ccbud/CCBuddy★ 8same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-browserSkill
- ai-sdkSkill
- electron-scaffoldSkill
- grill-meSkill
- ou-features-auditSkill
- ou-full-code-reviewSkill
- ouroboros-intent-e2eSkill
- ouroboros-test-plan-authorSkill
- prd-to-ticketsSkill
- team-implement-ticketsSkill
- ai-sdkSkill
- grill-meSkill
- meta-thinkingSkill
- ou-full-code-reviewSkill
- prd-to-ticketsSkill
- refactor-agents-mdSkill
- team-implement-ticketsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 21 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use this skill whenever the user wants to:
- Distinctive: line 13
Create and manage BrowserWindow instances
- Distinctive: line 16
Use Electron Forge for project scaffolding and building
- Distinctive: line 19
Use Electron APIs (app, BrowserWindow, ipcMain, ipcRenderer, etc.)
- Distinctive: line 68
All examples follow Electron latest API
- Distinctive: line 71
Always check the example file for best practices and common patterns
- Distinctive: line 138
Security: Never enable nodeIntegration in renderer process, use preload scripts
- Distinctive: line 139
Process separation: Keep main and renderer processes separate
- Distinctive: line 140
IPC communication: Use IPC for safe communication between processes
- Distinctive: line 144
Packaging: Use Electron Forge or electron-builder for packaging
- Distinctive: line 147
Cross-platform: Test on all target platforms
“Common” is measured: kept by at least 6 in 10 of the 21 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdorexamples/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
- Getting started/快速开始 →
Load the appropriate example file from the
examples/directory:Getting Started (快速开始) -
examples/getting-started/:examples/getting-started/installation.md- Installing Electron and basic setupexamples/getting-started/quick-start.md- Quick start tutorial
Processes (进程) -
examples/processes/:examples/processes/main-process.md- Main process concepts and usageexamples/processes/renderer-process.md- Renderer process conceptsexamples/processes/preload-scripts.md- Preload scripts usageexamples/processes/ipc-communication.md- IPC communication patterns
API Examples (API 示例) -
examples/api/:examples/api/browser-window.md- BrowserWindow usageexamples/api/menu.md- Menu and context menuexamples/api/tray.md- System trayexamples/api/dialog.md- File dialogsexamples/api/ipc-main.md- ipcMain usageexamples/api/ipc-renderer.md- ipcRenderer usage
Advanced (高级) -
examples/advanced/:examples/advanced/packaging.md- Application packagingexamples/advanced/security.md- Security best practicesexamples/advanced/auto-updater.md- Auto updaterexamples/advanced/native-modules.md- Native modules
Tools (工具) -
examples/tools/:examples/tools/electron-forge.md- Electron Forge usageexamples/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 APIapi/browser-window.md- BrowserWindow APIapi/ipc-main.md- ipcMain APIapi/ipc-renderer.md- ipcRenderer APIapi/menu.md- Menu APIapi/tray.md- Tray API
- Use templates from the
templates/directory:templates/main-process.md- Main process templatetemplates/preload-script.md- Preload script templatetemplates/renderer-process.md- Renderer process templatetemplates/package-json.md- package.json template
Doc mapping (one-to-one with official documentation)
examples/→ https://www.electronjs.org/zh/docs/latest/api/→ https://www.electronjs.org/zh/docs/latest/api/app
Quick Start Example
// main.js
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, // Security: always disable
contextIsolation: true // Security: always enable
}
})
win.loadFile('index.html')
}
app.whenReady().then(createWindow)
// IPC handler example
ipcMain.handle('get-data', async () => {
return { message: 'Hello from main process' }
})// preload.js
const { contextBridge, ipcRenderer } = require('electron')
contextBridge.exposeInMainWorld('api', {
getData: () => ipcRenderer.invoke('get-data')
})API Reference (api/)
api/app.md- app module APIapi/browser-window.md- BrowserWindow APIapi/ipc-main.md/api/ipc-renderer.md- IPC APIsapi/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
- Official Website: https://www.electronjs.org/zh/
- Documentation: https://www.electronjs.org/zh/docs/latest/
- API Reference: https://www.electronjs.org/zh/docs/latest/api/app
- Electron Forge: https://www.electronforge.io
- Electron Fiddle: https://www.electronjs.org/zh/fiddle
- GitHub Repository: https://github.com/electron/electron
Keywords
Electron, desktop app, main process, renderer process, preload, IPC, BrowserWindow, Menu, Tray, Dialog, packaging, electron-builder, electron-forge, electron-fiddle, cross-platform, 桌面应用, 主进程, 渲染进程, IPC 通信, 窗口, 菜单, 托盘, 打包
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

