Skip to content
vibespell

.cursor/rules/testing.mdc

Cursor testing rule for Kotlin

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 Kotlin project. This repository is an Android app in Kotlin. Match Compose or Views, whichever the module uses. Keep disk and network work off the main thread.

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 Kotlin on Android. It does not assume Compose, Hilt, or a particular navigation library unless the Gradle module already depends on them.

Customize in the generatorBrowse the library

Example file

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

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

# Testing rules

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

## Stack

This repository is an Android app in Kotlin. Match Compose or Views, whichever the module uses. Keep disk and network work off the main thread.

## Commands

- Unit tests: `./gradlew test`
- Lint: `./gradlew lint`
- Assemble: `./gradlew assembleDebug`

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

## Testing

Add or update tests when behavior changes.

Add a JVM unit test for the ViewModel or use case. Use instrumented tests only when you need the framework.

## Done when

- The requested behavior works.
- `./gradlew test` passes for the module you 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 Kotlin 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 Kotlin agent often gets wrong, such as a ViewModel that exposes state and does not hold an Activity reference. 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 Kotlin repo?

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

The example assumes Kotlin on Android. It does not assume Compose, Hilt, or a particular navigation library unless the Gradle module already depends on them.

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 Kotlin

Cursor testing rule for other stacks