Skip to content
vibespell

.cursor/rules/security.mdc

Cursor security rule for Nuxt

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 Nuxt project. This repository is a Nuxt 3 app. Data for a page comes from useAsyncData or a server route. Auto-imports match the project. Do not add a second meta-framework.

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 Nuxt 3. It does not assume Nuxt UI, Pinia, or a particular database. Use what nuxt.config already wires up.

Customize in the generatorBrowse the library

Example file

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

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

# Security rules

Attach these rules when editing auth, config, or secret-handling code in this Nuxt repository.
This repository is a Nuxt 3 app. Data for a page comes from useAsyncData or a server route. Auto-imports match the project. Do not add a second meta-framework.

## Secrets and trust

- Private runtime config never reaches the client.
- Validate server-route bodies. Do not trust the client.
- Keep auth checks in the server route, not only in middleware UI redirects.

## Errors

- Fail at the boundary. Do not swallow errors.
- Throw a createError with a status code for expected failures so the error page can render.

## Done when

- Untrusted input is validated before a side effect.
- No secret was added to source, logs, or a client bundle.
- `npm run build` succeeds and the page loads with JavaScript disabled if it is a content page.

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 Nuxt 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 Nuxt agent often gets wrong, such as a page whose data comes from useAsyncData instead of onMounted. 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 Nuxt repo?

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

The example assumes Nuxt 3. It does not assume Nuxt UI, Pinia, or a particular database. Use what nuxt.config already wires up.

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 Nuxt

Cursor security rule for other stacks