Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Astro

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 Astro project. This repository is an Astro site. Pages ship zero client JavaScript unless an island needs it. Content lives in content collections when the repo already uses 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 Astro. It does not assume React, Vue, or a particular UI framework for islands. Use the integration already in astro.config.

Customize in the generatorBrowse the library

Example file

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

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

# Testing rules

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

## Stack

This repository is an Astro site. Pages ship zero client JavaScript unless an island needs it. Content lives in content collections when the repo already uses them.

## Commands

- Dev server: `npm run dev`
- Build: `npm run build`
- Check: `npm run check`

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 helper or a content schema. Do not require a browser for a markdown change.

## Done when

- The requested behavior works.
- `npm run build` succeeds for the routes you touched.
- 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 Astro 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 Astro agent often gets wrong, such as a page that renders content on the server instead of fetching it in a client island. 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 Astro repo?

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

The example assumes Astro. It does not assume React, Vue, or a particular UI framework for islands. Use the integration already in astro.config.

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 Astro

Cursor testing rule for other stacks