What is electron-desktop?

Project rules for building an Electron desktop application with React and Vite. Electron combines a web interface with a desktop process, while a preload layer safely connects the two.

Use them when changing Electron main or preload code, configuring Vite, sharing code between desktop and web versions, or running the desktop development setup.

They clarify which code belongs in the desktop process, preload layer, or user interface. This helps avoid unsafe access to operating-system features and configuration mistakes during development.

electron-desktop — Cursor rule by trueLoving

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add rules/trueloving/pixuli/electron-desktop

Clone the repo

git clone --depth 1 https://github.com/trueLoving/Pixuli

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 217 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00217
Opus 5	$0.00000	$0.00109
Sonnet 5	$0.00000	$0.00043
Haiku 4.5	$0.00000	$0.00022

Measured 3d ago against content hash c321e5dece47, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

electron-desktop scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/electron-desktop.mdc · 23 lines

What it actually says