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>
21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
---
|
|
name: reference_chat_web_consumer
|
|
description: chat-web is the reference consumer app that drives IIOS feature work
|
|
metadata:
|
|
type: reference
|
|
---
|
|
|
|
**chat-web** (separate repo, `~/Documents/insignia-work/chat-web`) is the reference app on IIOS —
|
|
a 1:1 + group chat UI (Vite + React + TanStack Router/Query + socket.io-client + supabase-js).
|
|
It's frontend-only; IIOS provides identity, threads, messages, realtime, reactions, mentions,
|
|
media, notifications.
|
|
|
|
Feature work usually spans **both repos**: a generic primitive/port in iios + the app UI in
|
|
chat-web. The layer split we follow: **service** owns storage/auth/governance, the **SDK layer**
|
|
(`chat-web/src/lib/*`, mirrors `@insignia/iios-kernel-client`) owns client plumbing
|
|
(e.g. `uploadMedia`/`mediaUrl`, `registerPush`), the **app** owns rendering.
|
|
|
|
chat-web uses real Supabase login (`VITE_SUPABASE_URL` + anon key in its `.env`); identity =
|
|
email. Run it with `pnpm dev`. Commit both repos with git email `maaz@insigniaconsultancy.com`.
|
|
Related: [[project_recent_features]].
|