skills.rest
iptodays
iptodaysCOMMUNITY
Explore all skills by this author →
𝕏@iptodaysGitHub

client-standards

Standardize Electron and Vue 3 desktop app architecture, IPC, and platform rules.

Updated Apr 11, 2026
Search Tags:#typescript#architecture#cross-platform#electron#vue3#ipc#desktop-apps
One-click install
npx skills add https://github.com/iptodays/skills --skill client-standards
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-standards
Source: https://github.com/iptodays/skills/tree/main/client-standards
Command: npx skills add https://github.com/iptodays/skills --skill client-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear standard for building Electron and Vue 3 desktop applications so teams can avoid inconsistent architecture, fragile IPC, and platform-specific bugs.

Core Features & Use Cases

  • Main Process Architecture: Organizes core infrastructure, window management, business services, and IPC boundaries into predictable layers.
  • IPC Communication Standards: Defines channel naming, handler patterns, response envelopes, logging, and unsubscribe behavior for safe cross-process messaging.
  • Platform and Native Module Guidance: Covers platform detection, graceful fallback behavior, single-instance locking, custom title bars, and Rollup handling for native modules.
  • Use Case: Use this Skill when developing a cross-platform Electron desktop client with a Vue 3 renderer, shared TypeScript code, and strict communication rules between main and renderer processes.

Quick Start

Ask the Skill to review your Electron + Vue 3 desktop app and produce architecture, IPC, and platform guidance that follows these standards.

Frequently Asked Questions about client-standards

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

FAQPage Schema
How do I structure IPC communication in an Electron and Vue 3 desktop app?▼

Standardize IPC communication in Electron and Vue 3 apps by enforcing async ipcMain.handle workflows, unified response formats, strict channel naming, and proper listener cleanup for safe cross-process messaging.

What is the best way to manage native modules in a cross-platform Electron desktop application?▼

Handle native modules in cross-platform Electron apps by externalizing them via Rollup, applying platform detection, and establishing graceful fallback behavior to prevent platform-specific crashes.

How do I organize the main process architecture for a production Electron client?▼

Organize Electron main process architecture by layering core infrastructure, window management, business services, and IPC boundaries into predictable structures for robust desktop application development.

Does this standard support single-instance locking and custom title bars in Electron?▼

Yes, the standard provides specific guidance for implementing single-instance behavior locking and custom title bars alongside platform detection rules for cross-platform Electron desktop applications.

Why do I need strict rules for listener cleanup and IPC responses in Vue 3 desktop apps?▼

Strict listener cleanup and unified IPC response formats prevent memory leaks and fragile messaging, ensuring stable cross-process communication between Electron main and Vue 3 renderer layers.

Related Skills

Explore More Software Engineering Skills→
Auto-PluginAuto-Plugin
920

milkup-dev

Manage the milkup Electron Markdown editor development environment with Vite, esbuild, and pnpm.

Official
Advanced
brendadeeznuts1111brendadeeznuts1111

electron-base

Build secure Electron desktop apps with Vite, React, and TypeScript.

Community
Advanced
Gentleman-ProgrammingGentleman-Programming
618

hexagonal-architecture-layers-java

Enforce hexagonal architecture boundaries across Java Domain, Application, and Infrastructure layers.

Official
Advanced
miles990miles990
20

desktop-apps

Develop cross-platform desktop applications using Electron and Tauri frameworks.

Community
Intermediate