electron-development

Coordinate Electron app changes across renderer, main/preload, and embedded NestJS server.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Yusufkotavom/AiToEarn --skill electron-development-yusufkotavom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: electron-development
Source: https://github.com/Yusufkotavom/AiToEarn/tree/main/skills/electron-development
Command: npx skills add https://github.com/Yusufkotavom/AiToEarn --skill electron-development-yusufkotavom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams coordinate Electron app changes across multiple project areas (renderer, main/preload, and the embedded NestJS server), reducing drift and rework.

Core Features & Use Cases

  • Scope delineation for renderer, main/preload, and server API changes.
  • Guardrails to maintain API compatibility and build integrity.
  • Consistent testing and lint checks as part of the workflow.

Quick Start

Identify the change scope (renderer, main/preload, or server) and follow the workflow to implement and validate updates.

Frequently Asked Questions about electron-development

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

FAQPage Schema
How do I coordinate Electron app changes across renderer and server?

Coordinating Electron app changes requires delineating scope across renderer, main/preload, and embedded NestJS server areas to reduce drift. This workflow enforces API compatibility checks and build guardrails to maintain Vite + Electron build integrity.

What is the best way to maintain API compatibility in an Electron and NestJS workflow?

Maintaining API compatibility in an Electron and NestJS workflow involves enforcing scope validation and guardrails during modifications. This ensures build integrity and consistent testing across UI and backend updates.

How do I validate Vite and Electron build safety when updating the main process?

Validating Vite and Electron build safety involves applying scope delineation and guardrails when updating the main/preload process. Consistent lint checks and testing are enforced to catch build issues.

Can I use this workflow to update both the embedded NestJS server and the Electron renderer?

Yes, you can use this workflow to update the embedded NestJS server and the Electron renderer. It coordinates changes across project source, electron, and server directories while enforcing API compatibility checks.

Why do I need scope delineation for Electron renderer and main process modifications?

Scope delineation for Electron renderer and main process modifications is needed to reduce drift and rework across project areas. It ensures targeted API compatibility checks and build guardrails are applied correctly.