Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Remix

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 Remix project. This repository is a Remix app. Data loads in loaders, mutations happen in actions, and forms work without a custom client fetch.

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 Remix with loaders and actions. It does not assume Vite versus the classic compiler, or a particular CSS system. Follow the remix.config or vite.config the repo has.

Customize in the generatorBrowse the library

Example file

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

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

# Testing rules

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

## Stack

This repository is a Remix app. Data loads in loaders, mutations happen in actions, and forms work without a custom client fetch.

## Commands

- Dev server: `npm run dev`
- Typecheck: `npm run typecheck`
- Tests: `npm test`

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

## Testing

Add or update tests when behavior changes.

Call the loader or action with a Request in a unit test. Cover the invalid form case.

## Done when

- The requested behavior works.
- The route loader and action typecheck, and the form still works without JavaScript if it did before.
- 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 Remix 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 Remix agent often gets wrong, such as a loader that returns data the route renders without useEffect. 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 Remix repo?

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

The example assumes Remix with loaders and actions. It does not assume Vite versus the classic compiler, or a particular CSS system. Follow the remix.config or vite.config the repo has.

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 Remix

Cursor testing rule for other stacks