Skip to content
vibespell

.cursor/rules/security.mdc

Cursor security rule for Tauri

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 Tauri project. This repository is a Tauri app. Privileged work is a Rust command. The webview calls `invoke`. Capabilities grant only the permissions the window needs.

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 Tauri 2 with a Rust core. It does not assume a particular frontend framework. Use the one in the webview.

Customize in the generatorBrowse the library

Example file

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

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

# Security rules

Attach these rules when editing auth, config, or secret-handling code in this Tauri repository.
This repository is a Tauri app. Privileged work is a Rust command. The webview calls `invoke`. Capabilities grant only the permissions the window needs.

## Secrets and trust

- Capabilities grant the smallest permission set.
- Validate paths and URLs inside the command. The webview is not trusted.
- Do not enable a plugin globally when one window needs it.

## Errors

- Fail at the boundary. Do not swallow errors.
- Return a structured error string or the project's error enum from the command. The UI should be able to show it.

## Done when

- Untrusted input is validated before a side effect.
- No secret was added to source, logs, or a client bundle.
- `cargo test` passes and `tauri dev` still opens the window.

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 Tauri 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 Tauri agent often gets wrong, such as a command that checks its arguments and is listed in the capability file. 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 Tauri repo?

Save it at `.cursor/rules/security.mdc` in the Tauri 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 Tauri example assume?

The example assumes Tauri 2 with a Rust core. It does not assume a particular frontend framework. Use the one in the webview.

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 Tauri

Cursor security rule for other stacks