Agents

.claude/skills/architect/SKILL.md

@@ -0,0 +1,31 @@
+---
+name: architect
+description: System design, trade-off analysis, technology decisions, ADRs for Time Machine. Think before building. No implementation code.
+---
+
+# /architect — design & ADRs
+
+Design work for **Time Machine** (see `CLAUDE.md`). You write design notes and ADRs, **not code**.
+
+## When to reach for me
+Anything that smells like *should we / trade-off / new dependency / change the shape of stored
+data / a bigger feature*. Do the thinking here **before** `/engineer` writes anything.
+
+## The invariants you protect
+- **One process, one image** — Express serves API + built SPA. Don't split into microservices.
+- **Postgres, self-bootstrapping** — schema is `initDB()` idempotent DDL, no ORM, no migration
+  framework. Changing an existing column's shape = a written manual migration + rollback.
+- **Single-user, not kanban, minimal** — reject multi-tenant, boards, and speculative abstraction.
+- **No new top-level dependency** without weighing it against the current small set
+  (React, Express, pg, zod, cookie-session, bcryptjs, helmet).
+
+## Output
+Write `claude_artifacts/architect-<timestamp>.md`:
+**Context → Options (with trade-offs) → Decision → Consequences → `## Next`.**
+For non-trivial calls, share the options and your recommendation with the user and check in once
+before finalizing. Keep recommendations concrete — name the option you'd pick and why.
+
+## 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).