Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Laravel

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 Laravel project. This repository is a Laravel application. Routes stay thin, Eloquent owns persistence, and schema changes go through migrations. Use Artisan for the commands the repo already expects.

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 Laravel with Eloquent and migrations. It does not assume Inertia, Livewire, or a particular admin package. If the repo uses one of those, follow it instead of adding a second UI stack.

Customize in the generatorBrowse the library

Example file

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

---
description: "Testing rules for a Laravel repository"
globs: "**/*Test.php"
alwaysApply: false
---

# Testing rules

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

## Stack

This repository is a Laravel application. Routes stay thin, Eloquent owns persistence, and schema changes go through migrations. Use Artisan for the commands the repo already expects.

## Commands

- Dev server: `php artisan serve`
- Tests: `php artisan test`
- Migrate: `php artisan migrate`

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

## Testing

Add or update tests when behavior changes.

Cover the Form Request or the action with the repo's Pest or PHPUnit suite. Include one rejection and one success.

## Done when

- The requested behavior works.
- `php artisan test` passes, and a new migration is included when the schema changed.
- 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 Laravel 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 Laravel agent often gets wrong, such as a form request that rejects a bad payload before the controller runs. 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 Laravel repo?

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

The example assumes Laravel with Eloquent and migrations. It does not assume Inertia, Livewire, or a particular admin package. If the repo uses one of those, follow it instead of adding a second UI stack.

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 Laravel

Cursor testing rule for other stacks