From fbae75b957121f02e81b667fe99928e36d7a1980 Mon Sep 17 00:00:00 2001 From: pi Date: Sun, 5 Apr 2026 21:13:03 +1200 Subject: [PATCH] chore(cursor): add scoped-fixes rule for minimal changes Made-with: Cursor --- .cursor/rules/scoped-fixes.mdc | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 .cursor/rules/scoped-fixes.mdc diff --git a/.cursor/rules/scoped-fixes.mdc b/.cursor/rules/scoped-fixes.mdc new file mode 100644 index 0000000..115e164 --- /dev/null +++ b/.cursor/rules/scoped-fixes.mdc @@ -0,0 +1,18 @@ +--- +description: Fix only the issue or task the user gave; no refactors unless requested +alwaysApply: true +--- + +# Scoped fixes (no overscoping) + +1. **Change only what is needed** to satisfy the user’s *current* request (bug, error, feature, or explicit follow-up). Prefer the smallest diff that fixes it. + +2. **Refactors:** Do **not** refactor (restructure, rename, extract functions, change abstractions, or “make it nicer”) **unless the user explicitly asked for a refactor**. A bug fix may touch nearby lines only as much as required to correct the bug. + +3. **Do not** rename, reformat, or “clean up” unrelated code; do not add extra error handling, logging, or features you were not asked for. + +4. **Related issues:** If you spot other problems (missing functions, wrong types elsewhere, style), you may **mention them in prose** — do **not** fix them unless the user explicitly asks. + +5. **Tests and docs:** Add or change tests or documentation **only** when the user asked for them or they are strictly required to verify the requested fix. + +6. **Multiple distinct fixes:** If the user reported one error (e.g. a single `TypeError`), fix **that** cause first. Offer to tackle follow-ups separately rather than bundling.