desktop

Guide Electron desktop development with IPC handlers and window management patterns.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/razgulay/my-lobe-chat --skill desktop-razgulay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop
Source: https://github.com/razgulay/my-lobe-chat/tree/main/.agents/skills/desktop
Command: npx skills add https://github.com/razgulay/my-lobe-chat --skill desktop-razgulay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, frontmatter-driven guide for developing Electron-based desktop features, helping teams implement IPC handlers, preload scripts, window management, and menus with clear patterns and best practices.

Core Features & Use Cases

  • Architecture overview and pattern guidance for Electron apps (main and renderer processes, preload scripts, and IPC wiring)
  • Practical examples for common desktop tasks (window creation, IPC method registration, and menu configuration)
  • Reference implementations and best practices to reduce integration risk and speed up feature development

Quick Start

Create a new Electron feature by following the controller-service-model pattern shown in this guide, wiring a new IPC handler, its service, and a corresponding renderer service.

Frequently Asked Questions about desktop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the controller-service-model pattern for Electron desktop apps?

To set up Electron IPC handlers, wire a new IPC method in the main process, expose it securely through preload scripts, and call it from the renderer. This pattern cleanly separates desktop window management logic from UI components.

How do I configure window management and menus in an Electron app?

Electron window management and menu configuration are handled in the main process. You create browser windows, define native menus, and wire IPC channels to communicate securely with the renderer process using preload scripts.

How does a preload script communicate with the main process in Electron?

A preload script bridges the Electron main and renderer processes by securely exposing IPC channels. It allows the renderer to invoke main process handlers, enabling structured desktop window management and feature wiring without exposing Node.js APIs directly.

What's the best way to architect a new Electron desktop feature?

The best way to architect an Electron desktop feature is using a structured controller-service-model pattern. This separates IPC handlers, services, and renderer calls, providing clear references and best practices for maintaining main and renderer processes.

Do I need preload scripts to secure IPC communication in Electron?

Yes, preload scripts are essential for securing IPC communication in Electron. They act as a controlled bridge between the main and renderer processes, ensuring that desktop window management and IPC handlers operate safely without leaking Node.js APIs.