Skills Guide

Electron Pro Development

VerifiedSafe

Expert-level Electron development focusing on cross-process architecture, IPC security, context isolation, packaging, and runtime behavior.

Download and use
Sby Skills Guide Bot
DevelopmentAdvanced
7/27/2026
Claude CodeCursorWindsurfCopilotCodex
#electron#ipc#desktop#preload#security

Recommended for

Backend developerClaude CodeCode reviewFrontend developerCursorCopilot

Automated summary

Guides Electron implementation and debugging by reasoning about the responsibility split between the main process, preload bridge, and renderer.

Strengths

  • Explicitly maps the main / preload / renderer split before making changes
  • Treats IPC contracts, error handling, and trust boundaries as first-class concerns
  • Enforces concrete security checks: context isolation, minimized preload exposure, allowlists, and CSP implications
  • Validates one normal path plus one failure or retry path, and accounts for packaging and signing impact

Limitations

  • Deliberately does not redesign architecture across processes
  • Assumes prior familiarity with Electron processes and IPC
  • Signing and auto-update flows still require manual verification outside automated checks
When to use it

Use it whenever a task involves Electron-specific code: preload bridges, IPC contracts, window lifecycle, native integration, or packaging.

When not to use it

Avoid it for plain web apps without an Electron runtime, or when the goal is a full architectural redesign across processes.

Security analysis

Safe
Quality score90/100

The skill contains only engineering guidance for Electron development. It does not instruct destructive commands, secret exfiltration, obfuscated payloads, or safety-disabling behavior, and it explicitly emphasizes security boundaries, context isolation, minimal preload exposure, and IPC allowlists.

No concerns found

How this analysis is made

Examples

Corriger un échec IPC
Dans mon app Electron, un appel IPC depuis le renderer échoue silencieusement quand le fichier de config est absent et l'UI reste bloquée sur le spinner. Diagnostique le contrat IPC entre preload et main, propose le correctif le plus étroit et indique comment valider le chemin nominal et le chemin d'erreur.
Restreindre le pont preload
Mon preload expose `require` et tout le module fs au renderer. Réécris-le pour exposer une API minimale basée sur une liste d'autorisation explicite, compatible avec contextIsolation, en listant les fichiers modifiés et les implications CSP.
Vérifier l'impact packaging
J'ajoute une intégration au système de fichiers natif dans le processus principal. Dis-moi quels fichiers main/preload/renderer sont concernés, quel impact cela a sur le packaging et l'auto-update, et quels contrôles manuels restent nécessaires côté signature.

name: electron-pro description: "Use when a task needs Electron-specific implementation or debugging across main/renderer/preload boundaries, packaging, and desktop runtime behavior." compatibility: opencode metadata: model: gpt-5.4 model_reasoning_effort: high sandbox_mode: workspace-write

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.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/electron-pro-development-ms2s7d3h' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/electron-pro-development-ms2s7d3h/download' --output '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md.part' && mv '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md.part' '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Environment declared by the author: opencode

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md' && test -s '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/electron-pro' && cp -R '.skill-downloads/electron-pro-development-ms2s7d3h' '.claude/skills/electron-pro'

Cursor
test -f '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md' && test -s '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/electron-pro' && cp -R '.skill-downloads/electron-pro-development-ms2s7d3h' '.cursor/skills/electron-pro'

Codex
test -f '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md' && test -s '.skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/electron-pro' && cp -R '.skill-downloads/electron-pro-development-ms2s7d3h' '.agents/skills/electron-pro'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/electron-pro-development-ms2s7d3h'

openskills read 'electron-pro-development-ms2s7d3h'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/electron-pro-development-ms2s7d3h/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

React Hook Form Best Practices

Development

Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.

Claude CodeCursorWindsurf+2intermediateSafe 108,623
Skills Guide Bot

Emotion to Mantine Migration

Development

Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.

Claude CodeCursorWindsurf+1intermediateSafe 48,981
Skills Guide Bot

Scope Creep Detector

Development

Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.

Claude CodeCursorCodexintermediateSafe 135,015
Skills Guide Bot