Add dotclaude configuration files

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-26 17:16:27 -07:00
parent c10636b330
commit 491a45dd43
37 changed files with 2737 additions and 0 deletions
@@ -0,0 +1,14 @@
+---
+alwaysApply: true
+---
+
+# Testing
+
+- Write tests that verify behavior, not implementation details.
+- Run the specific test file after changes, not the full suite — faster feedback.
+- If a test is flaky, fix or delete it. Never retry to make it pass.
+- Prefer real implementations over mocks. Only mock at system boundaries (network, filesystem, clock).
+- One assertion per test. If the name needs "and", split it.
+- Test names describe behavior: `should return empty array when input is empty`, not `test1`.
+- Arrange-Act-Assert structure. No logic (if/loops) in tests.
+- Never `expect(true)` or assert a mock was called without checking its arguments.