From c2b0a4fea2143d024cf95d9c6e18be50e6ccd587 Mon Sep 17 00:00:00 2001
From: James Griffin <james@unsupervised.ca>
Date: Tue, 7 Apr 2026 10:55:33 -0300
Subject: [PATCH] Add claude configuration about tests

---
 .claude/memory/feedback_tests.md | 14 ++++++++++++++
 .claude/settings.json            |  5 ++++-
 2 files changed, 18 insertions(+), 1 deletion(-)
 create mode 100644 .claude/memory/feedback_tests.md

diff --git a/.claude/memory/feedback_tests.md b/.claude/memory/feedback_tests.md
new file mode 100644
index 0000000..e3dd961
--- /dev/null
+++ b/.claude/memory/feedback_tests.md
@@ -0,0 +1,14 @@
+---
+name: Always include tests with changes
+description: All code changes must include appropriate tests; never ship untested code
+type: feedback
+---
+
+All changes (new features, bug fixes, refactors) must include tests as part of the same implementation. Do not ship code without accompanying tests.
+
+**Why:** User explicitly called out that tests were missing from Issue #1 implementation and expects tests to always accompany changes going forward.
+
+**How to apply:**
+- Go backend: add `_test.go` files alongside changed packages, using `httptest` for handler tests and a real (or in-memory) DB for store tests
+- Frontend: add `.test.tsx` files alongside new/changed pages and components using React Testing Library
+- Tests go in the same PR/commit as the code they cover — never as a follow-up
diff --git a/.claude/settings.json b/.claude/settings.json
index dbfe41f..e668cac 100644
--- a/.claude/settings.json
+++ b/.claude/settings.json
@@ -6,7 +6,10 @@
       "Bash(go build ./...)",
       "Bash(go vet ./...)",
       "Bash(go test -count=1 -v -coverprofile=coverage.out ./...)",
-      "Bash(go tool cover -func=coverage.out)"
+      "Bash(go tool cover -func=coverage.out)",
+      "Bash(tea issue:*)",
+      "Bash(go test:*)",
+      "Bash(npm test:*)"
     ]
   }
 }