multiplatform-desktop-skill

Diagnose cross-platform regressions in Electron, React, and TypeScript desktop apps.

234|36|Updated May 15, 2026
One-click install
npx skills add https://github.com/St0ff3l/fileterm --skill multiplatform-desktop-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multiplatform-desktop-skill
Source: https://github.com/St0ff3l/fileterm/tree/main/.agents/skills/multiplatform-desktop-skill
Command: npx skills add https://github.com/St0ff3l/fileterm --skill multiplatform-desktop-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Building Electron desktop apps often leads to inconsistent behavior across macOS, Windows and Linux, where fixes for one platform silently break another, and platform-specific details like title bars, system trays, exit flows and font rendering are easy to mishandle without structured guidance.

Core Features & Use Cases

  • Layered cross-platform debugging: Guides you to check main, preload, renderer, assets and build layers separately to avoid cross-platform regressions.
  • Platform-specific rule enforcement: Provides clear, non-negotiable rules for macOS vs Windows title bars, tray icons, exit flows and font packaging to prevent misapplied platform semantics.
  • Use Case: When working on FileTerm, use this skill to fix a Windows-specific title bar layout regression without breaking macOS's native hiddenInset title bar behavior, or to resolve tray icon visibility issues across all three desktop OSes.

Quick Start

Use the multiplatform-desktop-skill to resolve the inconsistent window close confirmation behavior between macOS and Windows in the FileTerm desktop app.

Frequently Asked Questions about multiplatform-desktop-skill

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

FAQPage Schema
How do I fix Electron cross-platform compatibility issues across macOS, Windows, and Linux?

Fix Electron cross-platform compatibility issues by checking main, preload, renderer, assets, and build layers separately to isolate regressions. This structured debugging approach prevents platform-specific fixes from silently breaking behavior on other operating systems.

Why does my Electron title bar layout break on Windows when it works on macOS?

Electron title bar layout breaks across platforms when native semantics are misapplied. Enforce non-negotiable platform-specific rules for macOS hiddenInset behavior versus Windows layout to resolve these inconsistent UI regressions.

What is the best way to manage platform-specific resources in a layered Electron React TypeScript app?

The best way to manage platform-specific resources in a layered Electron app is to separate main, preload, and renderer processes. This architecture enforces consistent system capability access and unified platform detection across operating systems.

Can I use this cross-platform validation workflow for production Electron desktop apps with system tray icons?

Yes, this cross-platform validation workflow targets production Electron desktop apps and specifically resolves system tray icon visibility issues across macOS, Windows, and Linux using separated platform-specific resource management.

How do I resolve inconsistent window close confirmation behavior between macOS and Windows in Electron?

Resolve inconsistent window close confirmation behavior by enforcing platform-specific exit flow rules. This treats macOS and Windows exit semantics separately within the main process to ensure reliable cross-platform behavior.