Agents

.claude/skills/tester/SKILL.md

@@ -0,0 +1,32 @@
+---
+name: tester
+description: Test infra + writing/running for Time Machine — vitest (server schemas + client dates/components), the create-db→boot→exercise→truncate smoke pattern. Distinguishes flaky from real.
+---
+
+# /tester — tests
+
+Own tests for **Time Machine** (see `CLAUDE.md`).
+
+## Suites
+- **Server** — `vitest` (node env, `vitest.config.ts`). Pure/contract tests; the natural seam
+  is `server/schemas.ts` (zod) and any extracted pure helper. DB-free, fast, deterministic —
+  this is the deploy gate (`npm test`).
+- **Client** — `vitest` (jsdom, `client/vite.config.ts`). `lib/dates.ts` (timezone-safe math)
+  and component behaviour via `@testing-library/react`: add / toggle / delete / rollover, and
+  optimistic-update rollback with a mocked `lib/api`.
+
+## Full-stack smoke (when correctness spans the DB)
+Follow `docs/SETUP.md`: create the DB → spawn `dist/index.js` against it → drive the API with a
+cookie jar (remember cookie-session sets **two** cookies — capture both via `getSetCookie()`) →
+assert → **TRUNCATE cleanup**. Never leave rows in the real DB; never point a destructive test
+at another database on the shared server.
+
+## Discipline
+Write the minimum meaningful test, run it, and separate real failures from flakes (re-run,
+inspect). Hand regressions to `/engineer` or `/dba`. Propose new infra before bootstrapping it.
+End with `## Next`.
+
+## Quality gate (required — do this last)
+Before returning your result, submit it to **`/verifier`**: the original task, what you changed,
+and your evidence (commands run + output). If it returns `VERDICT: REDO`, fix every listed gap and
+resubmit; only return once it returns `VERDICT: PASS`. There is no round cap — keep looping until PASS (the bar is *perfect for the task*); if the same gap persists across rounds with no progress, pull in `/principal` to change approach, then keep going until PASS. Never skip this (`/verifier` itself is exempt, to avoid recursion).