Electron desktop app rules
Electron rules for agents: sandboxed renderers, narrow contextBridge APIs, sender-checked IPC, deny-by-default windows, CSP and fuses, with a static security check.
- 1 1 Rules
- 1 1 Skills
- – 0 MCP
The desktop loadouts start from the same rule: the window shows untrusted web content, and only the native side may touch files, the shell or the network. For Electron that means contextIsolation, sandboxed renderers, narrow preload APIs and IPC handlers that check the sender, plus a Playwright suite that drives the real app and fails if any of that is weakened. For Tauri 2 it means capability files that grant each window only what it needs.
Every one installs for Claude Code, Codex CLI, Cursor, Gemini CLI, Antigravity CLI and GitHub Copilot unless its card says otherwise.
Electron rules for agents: sandboxed renderers, narrow contextBridge APIs, sender-checked IPC, deny-by-default windows, CSP and fuses, with a static security check.
Playwright tests that drive the real Electron app: secure webPreferences, no Node in the renderer, IPC round trips, input validation and blocked navigation.
Tauri 2 rules and a permissions skill: capabilities for named windows, scoped fs and http, no shell execute, a CSP kept, plus a checker that flags wide grants.
Looking for something narrower? Search within Desktop apps or filter everything.