Skip to content
vibespell

.cursor/rules/security.mdc

Cursor security rule for Electron

A focused Cursor `.mdc` rule for auth, secrets, and untrusted input. It attaches when those files change, instead of repeating security policy in every chat. This copy is written for a Electron project. This repository is an Electron app. The main process owns Node and the system. The renderer is a web page. They talk through a preload bridge, not through nodeIntegration.

The example uses a balanced, readable style, pragmatic tests, and comments only where the intent is not obvious. Open the generator to make the agent stricter, switch to test-first, quiet the comments, or pick a different file.

The example assumes Electron with a preload script. It does not assume a particular renderer framework. Keep the one the window already loads.

Customize in the generatorBrowse the library

Example file

Balanced strictness, readable style, pragmatic tests. Download name: security.mdc

---
description: "Security rules for a Electron repository"
globs: "**/*{auth,Auth,secret,config,Config}*"
alwaysApply: false
---

# Security rules

Attach these rules when editing auth, config, or secret-handling code in this Electron repository.
This repository is an Electron app. The main process owns Node and the system. The renderer is a web page. They talk through a preload bridge, not through nodeIntegration.

## Secrets and trust

- contextIsolation stays on. nodeIntegration stays off.
- Validate and constrain every IPC argument.
- Do not follow redirects to untrusted origins from the main window.

## Errors

- Fail at the boundary. Do not swallow errors.
- Reject a bad IPC payload with an error the renderer can show. Do not crash the main process for bad input.

## Done when

- Untrusted input is validated before a side effect.
- No secret was added to source, logs, or a client bundle.
- The app boots in dev and the IPC you added rejects a malformed payload.

Add it to the project

  1. 01

    Copy a starting file

    Copy the example Cursor security rule on this page, or open the generator if you want different testing, strictness, or comment rules.

  2. 02

    Save it at .cursor/rules/security.mdc

    Save it at `.cursor/rules/security.mdc` in the Electron repo. Narrow the globs if your auth and config files live in a known folder.

  3. 03

    Start a fresh agent session

    Rules files are read when a session starts. A chat that is already open may still be using the old instructions.

  4. 04

    Give it one small task

    Ask for one change a Electron agent often gets wrong, such as an IPC channel that validates its payload in the main process. If it ignores the file, confirm the path and start a new session.

Questions about this file

Where do I put Cursor security rule in a Electron repo?

Save it at `.cursor/rules/security.mdc` in the Electron repo. Narrow the globs if your auth and config files live in a known folder.

Which tools read this Cursor security rule?

Cursor loads `.cursor/rules/security.mdc` for files that match its globs. Pair it with the always-on project rule. It is not a substitute for code review.

What does the Electron example assume?

The example assumes Electron with a preload script. It does not assume a particular renderer framework. Keep the one the window already loads.

Does VibeSpell upload my repository?

No. Recipe pages are static, and the generator builds the file in your browser from the options you pick. Your source code never leaves the machine.

Other files for Electron

Cursor security rule for other stacks