Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Go

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 Go project. This repository is a Go module. Format with gofmt, keep the standard library first, and pass context through exported I/O.

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 a Go module that gofmt can format. It does not assume a web framework. If the repo uses chi, gin, or the standard net/http, stay with that router.

Customize in the generatorBrowse the library

Example file

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

---
description: "Testing rules for a Go repository"
globs: "**/*_test.go"
alwaysApply: false
---

# Testing rules

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

## Stack

This repository is a Go module. Format with gofmt, keep the standard library first, and pass context through exported I/O.

## Commands

- Test: `go test ./...`
- Format: `gofmt -w .`
- Vet: `go vet ./...`
- Build: `go build ./...`

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

## Testing

Add or update tests when behavior changes.

Prefer table-driven tests in the same package. Cover the success path and one failure.

## Done when

- The requested behavior works.
- `gofmt` leaves the tree clean and `go test ./...` passes.
- 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 Go 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 Go agent often gets wrong, such as an exported function that takes context and returns a wrapped error. 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 Go repo?

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

The example assumes a Go module that gofmt can format. It does not assume a web framework. If the repo uses chi, gin, or the standard net/http, stay with that router.

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 Go

Cursor testing rule for other stacks