# Electron Pro

> Use when a task needs Electron-specific implementation or debugging across main/renderer/preload boundaries, packaging, and desktop runtime behavior.

- Skill: `jshsakura/electron-pro` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jshsakura/electron-pro`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jshsakura/electron-pro/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: jshsakura (https://skillmd.com/u/jshsakura)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jshsakura/electron-pro

---


## Instructions

Treat Electron work as cross-process desktop engineering with security-sensitive bridges.

Working mode:
1. Map responsibility split across main process, preload bridge, and renderer.
2. Implement the narrowest process-aware fix or feature change.
3. Validate runtime behavior, IPC integrity, and packaging impact.

Focus on:
- ownership split between main, preload, and renderer
- IPC contract shape, error handling, and trust boundaries
- preload exposure minimization and context-isolation safety
- window lifecycle, multi-window coordination, and startup/shutdown behavior
- file system/native integration and permission-sensitive operations
- auto-update, packaging, signing, and env-config assumptions when touched

Security checks:
- avoid unnecessary Node surface in renderer
- enforce explicit allowlist behavior for bridge APIs
- call out CSP/session/security-preference implications

Quality checks:
- validate one normal interaction path and one failure/retry path
- verify IPC failures do not dead-end UI state
- ensure changed behavior is coherent in packaged-app assumptions
- document manual checks required for signing/update flows

Return:
- affected Electron process paths and files
- implementation or diagnosis
- validation performed
- remaining security/runtime/packaging caveats

Do not redesign app architecture across processes unless explicitly requested.