Agents

2026-08-29 12:55:39 +03:00
parent e637634c59
commit 9868b18818
37 changed files with 2038 additions and 0 deletions
@@ -0,0 +1,38 @@
+---
+name: engineer
+description: Write any Time Machine code — React 18 components, Express routes, TS, SQL wiring, config. Reads patterns first, self-reviews via /reviewer.
+---
+
+# /engineer — implementation
+
+Write client or server code for **Time Machine** (see `CLAUDE.md`). Read the neighbouring file
+and match it before typing.
+
+## Map
+- **Client** `client/src/` — React 18 function components + hooks, TS strict. Views live in
+  `components/`; shared logic in `lib/` (`api.ts` = the only path to the server, `dates.ts` =
+  local `YYYY-MM-DD` math). Styling = plain CSS via the tokens in `styles.css` (`--ink`,
+  `--surface`, `--accent`, `--work`, `--home`, radii, shadows) — no hard-coded hex, no second
+  styling system. Optimistic updates must roll back on error.
+- **Server** `server/` — Express, TS strict, ESM with explicit `.js` import extensions. Validate
+  every request with a **zod** schema from `server/schemas.ts` (add new contracts there so
+  they're unit-testable). Every query is **`user_id`-scoped and parameterised**. Async handlers
+  are safe (`express-async-errors` loaded); errors only at boundaries; never leak internals.
+- **Dates** are local calendar strings end to end — don't add UTC conversions (`db.ts` keeps
+  the DATE type a raw string on purpose).
+
+## Definition of done
+1. `npm run typecheck` clean.
+2. `npm test` (+ `npm --prefix client test` for client work) green.
+3. `npm run build` if you touched the build surface.
+4. Spawn `/reviewer`; fix every critical/major.
+5. Route specialised surfaces: SQL → `/dba`, auth/secrets → `/security`, Docker/deploy →
+   `/devops`, visual → `/designer`, coverage → `/tester`.
+
+## Autonomy
+Trivial one-liner → just do it. Non-trivial → short plan, one check-in, execute, show result.
+
+## 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).