Guidance for building desktop applications with Electron, a framework that packages web technologies as apps for Windows, macOS, and Linux.

It helps create windows, menus, tray icons, and native features; connect app processes; package apps; debug them; and apply security practices.

It explains how the separate parts of an Electron app communicate and how to handle desktop-specific behavior safely.

electron — Skill by recomposesh

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/recomposesh/recompose/electron

Any agent

npx skills add recomposesh/recompose --skill electron

Clone the repo

git clone --depth 1 https://github.com/recomposesh/recompose

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,074 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00051	$0.02074
Opus 5	$0.00026	$0.01037
Sonnet 5	$0.00010	$0.00415
Haiku 4.5	$0.00005	$0.00207

Measured 2d ago against content hash 3d7a6da310ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

electron scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/electron/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Read the full file on GitHub · 193 lines

Files

What ships with it

12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 193 lines · 51 tokens per session scan A 3d7a6da310ba

Subscribe to this mod's changes

electron is a skill published in the GitHub repository recomposesh/recompose (25 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 2,074 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Frontend

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens