Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Roblox

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 Roblox project. This repository is a Roblox experience in Luau. The server owns the truth. Clients request actions through remotes, and every remote validates its arguments.

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 Luau with the project's Rojo or Studio layout. It does not assume a particular framework such as Knit unless the repo already uses it.

Customize in the generatorBrowse the library

Example file

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

---
description: "Testing rules for a Roblox repository"
globs: "**/*.spec.luau"
alwaysApply: false
---

# Testing rules

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

## Stack

This repository is a Roblox experience in Luau. The server owns the truth. Clients request actions through remotes, and every remote validates its arguments.

## Commands

- Serve: `rojo serve`
- Analyze: `Run the project's Luau analyzer, such as selene, if one is configured`

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

## Testing

Add or update tests when behavior changes.

Test pure module functions with the project's TestEZ or similar runner if it exists. Otherwise state the remote case you simulated.

## Done when

- The requested behavior works.
- The server script rejects a wrong-typed remote argument, and the client path you changed still fires.
- 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 Roblox 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 Roblox agent often gets wrong, such as a remote that checks the player and the argument types on the server. 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 Roblox repo?

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

The example assumes Luau with the project's Rojo or Studio layout. It does not assume a particular framework such as Knit unless the repo already uses 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 Roblox

Cursor testing rule for other stacks