Skip to content
vibespell

.cursor/rules/security.mdc

Cursor security rule for Django

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 Django project. This repository is a Django project. Models, views, and templates follow the apps that already exist. Schema changes go through migrations, and you do not skip migrations.

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 Django with the ORM and migrations. It does not assume Django REST framework. If DRF is installed, use serializers. Otherwise stay with the views and forms the project already uses.

Customize in the generatorBrowse the library

Example file

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

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

# Security rules

Attach these rules when editing auth, config, or secret-handling code in this Django repository.
This repository is a Django project. Models, views, and templates follow the apps that already exist. Schema changes go through migrations, and you do not skip migrations.

## Secrets and trust

- Leave CSRF protection on for browser forms.
- Do not set DEBUG and a wildcard ALLOWED_HOSTS in production settings.
- Authorize in the view. A hidden template button is not a permission.

## Errors

- Fail at the boundary. Do not swallow errors.
- Use Django's validation and a 4xx response for bad input. Let unexpected exceptions hit the configured logging.

## Done when

- Untrusted input is validated before a side effect.
- No secret was added to source, logs, or a client bundle.
- `python manage.py check` is clean and the migration list matches the model change you made.

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 Django 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 Django agent often gets wrong, such as a model change that includes the migration, not only the model field. 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 Django repo?

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

The example assumes Django with the ORM and migrations. It does not assume Django REST framework. If DRF is installed, use serializers. Otherwise stay with the views and forms the project already uses.

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 Django

Cursor security rule for other stacks