Skip to content
vibespell

.cursor/rules/security.mdc

Cursor security rule for Laravel

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 Laravel project. This repository is a Laravel application. Routes stay thin, Eloquent owns persistence, and schema changes go through migrations. Use Artisan for the commands the repo already expects.

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 Laravel with Eloquent and migrations. It does not assume Inertia, Livewire, or a particular admin package. If the repo uses one of those, follow it instead of adding a second UI stack.

Customize in the generatorBrowse the library

Example file

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

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

# Security rules

Attach these rules when editing auth, config, or secret-handling code in this Laravel repository.
This repository is a Laravel application. Routes stay thin, Eloquent owns persistence, and schema changes go through migrations. Use Artisan for the commands the repo already expects.

## Secrets and trust

- Leave CSRF protection on for web routes.
- Mass-assign only through `$fillable` or `$guarded` the model already uses.
- Do not log request bodies that contain passwords or tokens.

## Errors

- Fail at the boundary. Do not swallow errors.
- Throw or return a validation error for bad input. Let unexpected exceptions hit the project's exception handler.

## Done when

- Untrusted input is validated before a side effect.
- No secret was added to source, logs, or a client bundle.
- `php artisan test` passes, and a new migration is included when the schema changed.

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 Laravel 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 Laravel agent often gets wrong, such as a form request that rejects a bad payload before the controller runs. 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 Laravel repo?

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

The example assumes Laravel with Eloquent and migrations. It does not assume Inertia, Livewire, or a particular admin package. If the repo uses one of those, follow it instead of adding a second UI stack.

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 Laravel

Cursor security rule for other stacks