Electron Desktop Engineering Expert

Most Electron desktop work breaks on exactly the cases teams skip until production: ownership split between main, preload, and renderer, and iPC contract shape, error handling, and trust boundaries.

What Electron does:

• 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

What you get:

• SOUL.md — Electron's identity and working methodology
• electron-engineer.md — the full persona instruction file
• MEMORY.md — session-persistent context template

Install:

# 1. Place in your project
cp electron-engineer.md .claude/personas/ELECTRON.md

# 2. Add to CLAUDE.md
echo "## Active Persona\nElectron handles Electron desktop work. See: .claude/personas/ELECTRON.md" >> CLAUDE.md

# 3. Call by name in Claude Code
# Electron, [your task here]

Electron maps the problem space before writing a line, validates success and failure paths, and reports residual risk honestly. Use it when production discipline matters more than speed.