agentleFS
full-stack-skillsfull-stack-skills/electron-skills/skills/electron-egg/SKILL.md

electron-egg

Skill8 starsChanged 54 days agoApache-2.0View on GitHub

Provides comprehensive guidance for Electron EGG framework including project structure, main/renderer processes, IPC, window management, and desktop app development. Use when the user asks about Electron EGG, needs to create Electron applications with EGG, or work with Electron EGG patterns.

  • Installs packages

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill whenever the user wants to:

    line 8
  2. Distinctive:

    Create Electron desktop applications

    line 10
  3. Distinctive:

    Use Electron EGG core features

    line 11
  4. Distinctive:

    Use Electron EGG API methods

    line 14
  5. Distinctive:

    Follow the instructions, syntax, and best practices in that file

    line 132
  6. Very specific:

    All API files include links to relevant example files in the examples/ directory

    line 179
  7. Distinctive:

    Separate processes: Keep main process and renderer process code separate

    line 183
  8. Distinctive:

    Use IPC: Use IPC for inter-process communication

    line 184
  9. Distinctive:

    Security: Follow Electron security best practices

    line 186
  10. Distinctive:

    Plugin system: Use plugin system for extensibility

    line 189

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

When to use this skill

Use this skill whenever the user wants to:

  • Install and set up Electron EGG in a project
  • Create Electron desktop applications
  • Use Electron EGG core features
  • Configure Electron EGG
  • Handle main process and renderer process communication
  • Use Electron EGG API methods
  • Build and package Electron applications
  • Troubleshoot Electron EGG issues

How to use this skill

This skill is organized to match the Electron EGG official documentation structure (https://www.kaka996.com/, https://www.kaka996.com/pages/987b1c/, https://www.kaka996.com/pages/a99b72/). When working with Electron EGG:

  1. Identify the topic from the user's request:
    • Installation/安装 → examples/guide/installation.md
    • Quick Start/快速开始 → examples/guide/quick-start.md
    • Features/功能特性 → examples/features/
    • API/API 文档 → api/
  2. Load the appropriate example file from the examples/ directory:

    Guide (使用文档):

    • examples/guide/intro.md - Introduction to Electron EGG
    • examples/guide/installation.md - Installation guide
    • examples/guide/quick-start.md - Quick start guide
    • examples/guide/project-structure.md - Project structure
    • examples/guide/configuration.md - Configuration
    • examples/guide/build.md - Build and package

    Features (功能特性):

    • examples/features/main-process.md - Main process
    • examples/features/renderer-process.md - Renderer process
    • examples/features/ipc-communication.md - IPC communication
    • examples/features/window-management.md - Window management
    • examples/features/menu.md - Menu
    • examples/features/tray.md - System tray
    • examples/features/auto-updater.md - Auto updater
    • examples/features/plugin-system.md - Plugin system
  3. Follow the specific instructions in that example file for syntax, structure, and best practices

    Important Notes:

    • Electron EGG is based on Electron and Egg.js
    • Main process and renderer process separation
    • IPC communication between processes
    • Each example file includes key concepts, code examples, and key points
  4. Reference API documentation in the api/ directory when needed:

    • api/main-api.md - Main process API
    • api/renderer-api.md - Renderer process API
    • api/ipc-api.md - IPC API
    • api/window-api.md - Window API
    • api/config-api.md - Configuration API

    API Files:

    • api/main-api.md - Application class, BrowserWindow, ipcMain, app methods
    • api/renderer-api.md - ipcRenderer, contextBridge, DOM APIs
    • api/ipc-api.md - IPC communication methods and events
    • api/window-api.md - Window creation and management
    • api/config-api.md - Configuration options and environment variables
  5. Use templates from the templates/ directory:
    • templates/installation.md - Installation templates
    • templates/project-setup.md - Project setup templates
    • templates/configuration.md - Configuration templates

1. Understanding Electron EGG

Electron EGG is a desktop application development framework based on Electron and Egg.js, providing a complete development toolchain and best practices.

Key Concepts:

  • Electron: Cross-platform desktop application framework
  • Egg.js: Node.js enterprise application framework
  • Main Process: Main application process
  • Renderer Process: UI rendering process
  • IPC: Inter-process communication
  • Plugin System: Extensible plugin architecture

2. Installation

Using npm:

npm install ee-core

Using yarn:

yarn add ee-core

Using pnpm:

pnpm add ee-core

3. Basic Setup

// main.js
const { Application } = require('ee-core')

const app = new Application({
  // Configuration
})

app.start()

Doc mapping (one-to-one with official documentation)

Examples and Templates

This skill includes detailed examples organized to match the official documentation structure. All examples are in the examples/ directory (see mapping above).

To use examples:

  • Identify the topic from the user's request
  • Load the appropriate example file from the mapping above
  • Follow the instructions, syntax, and best practices in that file
  • Adapt the code examples to your specific use case

To use templates:

  • Reference templates in templates/ directory for common scaffolding
  • Adapt templates to your specific needs and coding style

API Reference

Detailed API documentation is available in the api/ directory, organized to match the official Electron EGG API documentation structure (https://www.kaka996.com/pages/a99b72/):

Main Process API (api/main-api.md)

  • Application class and methods
  • BrowserWindow creation and management
  • ipcMain IPC handling
  • Application lifecycle hooks

Renderer Process API (api/renderer-api.md)

  • ipcRenderer IPC communication
  • contextBridge for secure API exposure
  • DOM APIs available in renderer
  • Event handling

IPC API (api/ipc-api.md)

  • IPC communication methods (ipcMain, ipcRenderer)
  • Message sending and receiving
  • Async and sync IPC
  • Event handling and channels

Window API (api/window-api.md)

  • BrowserWindow creation and options
  • Window management methods
  • Window events
  • Window lifecycle

Configuration API (api/config-api.md)

  • Configuration file structure
  • App info configuration
  • Window configuration
  • Plugin configuration
  • Environment variables

To use API reference:

  1. Identify the API you need help with
  2. Load the corresponding API file from the api/ directory
  3. Find the API signature, parameters, return type, and examples
  4. Reference the linked example files for detailed usage patterns
  5. All API files include links to relevant example files in the examples/ directory

Best Practices

  1. Separate processes: Keep main process and renderer process code separate
  2. Use IPC: Use IPC for inter-process communication
  3. Handle errors: Properly handle errors in both processes
  4. Security: Follow Electron security best practices
  5. Performance: Optimize application performance
  6. Build configuration: Configure build and package properly
  7. Plugin system: Use plugin system for extensibility

Resources

Keywords

Electron EGG, electron-egg, Electron, Egg.js, desktop application, 桌面应用, 主进程, 渲染进程, IPC, 进程间通信, 窗口管理, 菜单, 系统托盘, 自动更新, 插件系统, main process, renderer process, inter-process communication, window management, menu, system tray, auto updater, plugin system

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.