Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Phaser

A Cursor `.mdc` rule can attach only when you touch tests. This variant keeps testing policy out of the always-on project rule so day-to-day edits stay quieter. 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: testing.mdc

---
description: "Testing rules for a Phaser repository"
globs: "**/*.{test,spec}.ts"
alwaysApply: false
---

# Testing rules

Attach these rules when editing tests in this Phaser repository.
The always-on project rule still lives in `.cursor/rules/project.mdc`. This file does not repeat it.

## Stack

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.

## Commands

- Dev: `npm run dev`
- Tests: `npm test`
- Build: `npm run build`

Use the script the repo already defines when it differs from the command above.

## Testing

Add or update tests when behavior changes.

Test pure game rules outside Phaser. Boot a scene only when lifecycle is the bug.

## Done when

- The requested behavior works.
- The scene boots in dev and the update path you touched does not allocate per frame.
- The diff stays inside the task.
- You list anything you could not run.

Add it to the project

  1. 01

    Copy a starting file

    Copy the example Cursor testing rule on this page, or open the generator if you want different testing, strictness, or comment rules.

  2. 02

    Save it at .cursor/rules/testing.mdc

    Save it at `.cursor/rules/testing.mdc` in the Phaser repo, next to the always-on project rule. Leave `alwaysApply` false so it only joins test edits.

  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 testing rule in a Phaser repo?

Save it at `.cursor/rules/testing.mdc` in the Phaser repo, next to the always-on project rule. Leave `alwaysApply` false so it only joins test edits.

Which tools read this Cursor testing rule?

Cursor loads `.cursor/rules/testing.mdc` when a file matches its globs. It does not replace `project.mdc`. Keep the always-on rule for stack conventions.

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 testing rule for other stacks