Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for SvelteKit

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 SvelteKit project. This repository is a SvelteKit app. Load data in load functions, mutate through form actions, and write new components with Svelte 5 runes.

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 SvelteKit with Svelte 5 runes (`$state`, `$derived`, `$props`). It does not assume a database or an auth library. If the repo is still on Svelte 4 stores, follow the local style instead of rewriting it.

Customize in the generatorBrowse the library

Example file

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

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

# Testing rules

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

## Stack

This repository is a SvelteKit app. Load data in load functions, mutate through form actions, and write new components with Svelte 5 runes.

## Commands

- Dev server: `npm run dev`
- Production build: `npm run build`
- Typecheck: `npm run check`
- 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.

Use the runner the repo already has. Test load functions and form actions as data, and add a browser test only for a real interaction.

## Done when

- The requested behavior works.
- `npm run check` is clean for the files you touched, and the route still loads in `npm run dev`.
- 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 SvelteKit 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 SvelteKit agent often gets wrong, such as a page whose data comes from a load function rather than onMount. 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 SvelteKit repo?

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

The example assumes SvelteKit with Svelte 5 runes (`$state`, `$derived`, `$props`). It does not assume a database or an auth library. If the repo is still on Svelte 4 stores, follow the local style instead of rewriting 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 SvelteKit

Cursor testing rule for other stacks