Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Bevy

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 Bevy project. This repository is a Bevy game. Data lives in components, behavior lives in systems, and schedules stay explicit. Do not reach for a God object.

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 Bevy. It does not assume a particular physics crate or UI crate unless Cargo.toml already depends on it.

Customize in the generatorBrowse the library

Example file

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

---
description: "Testing rules for a Bevy repository"
globs: "src/**/*.rs"
alwaysApply: false
---

# Testing rules

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

## Stack

This repository is a Bevy game. Data lives in components, behavior lives in systems, and schedules stay explicit. Do not reach for a God object.

## Commands

- Run: `cargo run`
- Test: `cargo test`
- Check: `cargo clippy --all-targets -- -D warnings`

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

## Testing

Add or update tests when behavior changes.

Test a pure system with a minimal App or a plain function. Do not boot the full game.

## Done when

- The requested behavior works.
- `cargo test` passes and `cargo clippy --all-targets -- -D warnings` is clean for non-trivial changes.
- 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 Bevy 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 Bevy agent often gets wrong, such as a system that queries the components it needs and does not spawn entities every frame by accident. 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 Bevy repo?

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

The example assumes Bevy. It does not assume a particular physics crate or UI crate unless Cargo.toml already depends on it.

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 Bevy

Cursor testing rule for other stacks