Electron

What This Skill Does

The Electron skill for OpenClaw provides an expert framework for developing secure, high-performance desktop applications using the Electron framework. It acts as a safety-first architectural consultant, ensuring that developers adhere to industry-standard security non-negotiables, such as enforcing context isolation and disabling Node.js integration in renderer processes. Beyond security, this skill guides you through the complex lifecycle of Electron development, including native module compilation, efficient packaging strategies, and cross-platform distribution requirements. Whether you are bootstrapping a new project or debugging memory leaks and performance bottlenecks, this skill provides the necessary technical guardrails to build professional-grade applications that avoid common pitfalls like white flashes, improper IPC communication, and distribution failures.

Installation

To integrate the Electron skill into your workflow, execute the following command in your terminal:

clawhub install openclaw/skills/skills/ivangdavila/electron

Use Cases

• Scaffolding new Electron projects with secure default configurations.
• Auditing existing codebases for security vulnerabilities like prototype pollution or improper IPC usage.
• Implementing native C++ modules with correct cross-compilation for Electron’s specific Node runtime.
• Configuring production packaging, including code signing for macOS and auto-update mechanisms for Windows.
• Optimizing startup performance through lazy loading and proper BrowserWindow lifecycle management.

Example Prompts

1. "I am building a desktop dashboard. Can you generate a secure main process template that implements context isolation and a strict IPC whitelist for my renderer?"
2. "My application is crashing after an Electron version upgrade. How do I use electron-rebuild to fix native module incompatibility?"
3. "I need to package my app for production. What are the best practices for minimizing bundle size and ensuring that devDependencies are excluded from the final ASAR package?"

Tips & Limitations

• Security Non-Negotiables: Always treat the renderer as an untrusted environment. Never enable nodeIntegration unless absolutely necessary, and even then, only within a dedicated, sandboxed process.
• Architecture: Remember that BrowserWindow processes are isolated. Use the contextBridge to expose only essential functionality to the frontend to minimize your attack surface.
• Native Modules: Avoid reliance on nan-based modules when possible; favor N-API modules for better long-term stability across Electron updates.
• Memory Management: Always destroy windows explicitly (win.destroy()) to prevent memory leaks, especially in applications that create and destroy child windows frequently.
• Limitations: This skill does not automatically compile native code for you, but it provides the specific command sequences and configuration changes required to ensure compilation succeeds.