maaz519
5abee1b5b7
Versioned, per-topic project memory (index + entries): IIOS overview, the generic-safety rule, run/test + the replay.spec flake workaround, recent features (Supabase auth, reactions/pins/saves, mentions, media, notifications), the chat-web consumer, and workflow conventions. CLAUDE.md points to it as the accumulating-notes companion to the canonical rules. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
20 lines
1.2 KiB
Markdown
20 lines
1.2 KiB
Markdown
---
|
|
name: feedback_workflow
|
|
description: Working conventions — commits, prod flags, TDD, rebuild-before-restart
|
|
metadata:
|
|
type: feedback
|
|
---
|
|
|
|
- **Commits:** conventional (`feat:`/`fix:`/`docs:`/`chore:`), git email
|
|
**`maaz@insigniaconsultancy.com`**, co-author every commit with Claude. The user commits
|
|
directly to `main` in this project (fine); branch only if asked.
|
|
- **⚠ `IIOS_DEV_TOKENS` MUST be `0`/unset in production** — it exposes `/v1/dev/*` (unauth token
|
|
minting, chaos, retention sweep). The single most important prod-hardening flag.
|
|
- **TDD** — write the failing spec first; verify it fails; implement; verify it passes.
|
|
- **Rebuild before restart** — after backend changes, `nest build` then restart from `dist`;
|
|
`lsof -ti :3200 | xargs kill -9` first or the old build keeps serving (stale-dist bites).
|
|
- **New kernel capability = a generic primitive only** — add domain meaning in OPA policy + the
|
|
app, never the kernel. See [[feedback_generic_safety]].
|
|
- The user prefers **direct, fast iteration** (implement → verify end-to-end → commit), not
|
|
heavyweight multi-agent/spec ceremony. Include "how to test" in summaries; report failures honestly.
|