code-debug-electron-platform

What problem does it solve?

It helps you diagnose and fix platform-specific Electron regressions by routing your change to the right cross-platform category (paths, keyboard accelerators, shell/spawn behavior, menus/tray/UI chrome, filesystem and line endings, and runtime quirks like deep links or single-instance handling).

Core Features & Use Cases

• Platform-specific triage: Detects which area your bug touches (like path usage or child_process spawning) and selects the matching reference to avoid cross-category “guessing.”
• Cross-OS correctness checks: Enforces rules for OS-divergent Electron APIs such as CmdOrCtrl accelerators, app.getPath for directories, safe spawn argument passing, correct .exe handling on Windows, and macOS app-menu/tray requirements.
• Change-leak detection: After applying fixes, scans for remaining category issues in the diff (e.g., one fixed path.join while other concatenations remain).

Use case example: You ship an Electron hotkey that works on macOS but fails on Windows; this Skill will route the fix to the keyboard/accelerator rules (e.g., CmdOrCtrl usage and role: preferences) and ensure the change is consistent across the codebase.

Quick Start

Ask the AI to debug your Electron regression by stating the exact symptom and the specific code locations involving paths, accelerators, spawn/child processes, menus/tray, filesystem/watcher logic, or runtime features like deep links and single-instance.