desktop

Implement Electron desktop features with controllers, IPC types, and renderer services.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/mabdulrauf/wazone-back --skill desktop-mabdulrauf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: desktop
Source: https://github.com/mabdulrauf/wazone-back/tree/main/.agents/skills/desktop
Command: npx skills add https://github.com/mabdulrauf/wazone-back --skill desktop-mabdulrauf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Electron desktop feature development often involves coordinating main/renderer processes, IPC, and window management, which can become complex and error-prone without a clear pattern.

Core Features & Use Cases

  • Architecture and patterns for building desktop features with Electron (main/renderer, IPC, and services)
  • Step-by-step guide to create controllers, define IPC types, implement renderer services, and wire store actions
  • Use cases include adding new desktop features, menu integrations, window lifecycle management, and secure IPC boundaries

Quick Start

Begin by creating a new feature under apps/desktop/src/main/controllers, define IPC types, and implement a corresponding renderer service to expose the feature to the UI.

Frequently Asked Questions about desktop

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

FAQPage Schema
How do I structure main and renderer process communication in Electron?

Electron main and renderer communication is structured using controllers, defined IPC types, and renderer services to enforce secure boundaries and streamline cross-process feature development.

What is the best way to organize a new Electron desktop feature?

Organize an Electron desktop feature by creating a controller under apps/desktop/src/main/controllers, defining IPC types, implementing renderer services, and wiring store actions.

How does this Electron architecture pattern handle window lifecycle management?

Window lifecycle management is handled through standard architecture patterns that coordinate main process controllers and renderer services to manage window creation, updates, and secure closures.

Can I use these IPC patterns for menu integrations in Electron?

Yes, these IPC patterns support menu integrations by exposing main process controller logic to the renderer through typed IPC boundaries and dedicated renderer services.

Do I need specific tooling workflows to maintain secure IPC boundaries?

Maintaining secure IPC boundaries requires following the standard tooling workflows and architectural patterns provided to coordinate controllers, IPC types, and renderer services correctly.