moai-framework-electron

Architect Electron 33+ apps with secure IPC, auto-updates, and packaging.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/binee108/PasteTrader --skill moai-framework-electron-binee108
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-framework-electron
Source: https://github.com/binee108/PasteTrader/tree/main/.claude/skills/moai-framework-electron
Command: npx skills add https://github.com/binee108/PasteTrader --skill moai-framework-electron-binee108

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a framework-driven blueprint for building secure, cross-platform Electron desktop applications, addressing the complexity of coordinating Main/Renderer processes, IPC, auto-updates, packaging, and security hardening.

Core Features & Use Cases

  • Architecture blueprint for managing the Main and Renderer processes, including secure BrowserWindow setup and IPC patterns.
  • Auto-update integration using electron-updater with packaging support via Electron Forge and electron-builder.
  • Security hardening guidance and best practices to minimize attack surfaces; CSP, permissions, and safe preload usage.
  • Use Case: Rapidly scaffold a cross-platform desktop app with native OS integration and a robust update flow.

Quick Start

Install the moai-framework-electron pattern into a new Electron project, initialize a BrowserWindow with secure defaults, implement type-safe IPC, configure the updater, and set up Forge/electron-builder packaging.

Frequently Asked Questions about moai-framework-electron

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

FAQPage Schema
How do I build a secure cross-platform Electron desktop app?

Electron architecture separates Main and Renderer processes, using IPC for type-safe communication. Secure BrowserWindow creation with strict CSP and safe preload usage minimizes attack surfaces while maintaining native OS integration.

How does IPC communication work between Main and Renderer processes in Electron?

Electron IPC communication bridges the Main and Renderer processes using type-safe patterns. Secure preload scripts expose controlled APIs, ensuring the Renderer cannot directly access Node.js capabilities and reducing security risks.

What's the best way to configure auto-updates for an Electron app?

Configuring Electron auto-updates requires integrating electron-updater with packaging tools like Electron Forge or electron-builder. This establishes robust update workflows and cross-platform deployment capabilities.

Does this Electron framework blueprint support Electron 33 and later versions?

Yes, this framework blueprint is designed for developers building Electron 33+ apps. It provides architecture patterns for modern Main/Renderer separation, IPC communication, and secure packaging configurations.

Should I use Electron Forge or electron-builder for packaging?

Both Electron Forge and electron-builder are supported for packaging. The framework provides configuration guidance for each, allowing you to select based on your specific build and auto-update integration requirements.

How do I set up Content Security Policy and secure preload usage in Electron?

Security hardening in Electron involves configuring strict Content Security Policy (CSP) permissions and using safe preload scripts. This minimizes the application's attack surface by limiting Renderer capabilities and external resource loading.