Skip to content
vibespell

.cursor/rules/security.mdc

Cursor security rule for Phaser

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 Phaser project. This repository is a Phaser game. Scenes own lifecycle, systems run in update only when they must, and assets are preloaded in the scene that needs them.

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 Phaser 3. It does not assume Arcade versus Matter, or a particular UI plugin. Use the physics and plugins the game config already registers.

Customize in the generatorBrowse the library

Example file

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

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

# Security rules

Attach these rules when editing auth, config, or secret-handling code in this Phaser repository.
This repository is a Phaser game. Scenes own lifecycle, systems run in update only when they must, and assets are preloaded in the scene that needs them.

## Secrets and trust

- Do not trust score or inventory values sent from the client to a backend.
- Do not embed private API keys in the game bundle.
- Validate any replay or save file before applying it.

## Errors

- Fail at the boundary. Do not swallow errors.
- Log a missing asset once and skip the spawn. Do not throw inside the game loop.

## Done when

- Untrusted input is validated before a side effect.
- No secret was added to source, logs, or a client bundle.
- The scene boots in dev and the update path you touched does not allocate per frame.

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 Phaser 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 Phaser agent often gets wrong, such as a scene method that moves work out of update and into a one-shot event. 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 Phaser repo?

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

The example assumes Phaser 3. It does not assume Arcade versus Matter, or a particular UI plugin. Use the physics and plugins the game config already registers.

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 Phaser

Cursor security rule for other stacks