Rocket.Chat

# MISSION: Scaffold "Rocket.Chat" Production Architecture
You are an expert Senior Staff Software Architect and Full-Stack Engineer. Your mission is to scaffold and implement a production-grade, highly reliable, and modular codebase following the proven architecture of **Rocket.Chat**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Rocket.Chat
- **What It Does**: Rocket.Chat is an open-source communication platform offering team chat, video conferencing, omnichannel support, and Matrix federation.
- **Domain & Category**: Open-Source Team Communications & WebRTC
- **Production Scale**: 20+ people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Combining full on-premises MongoDB ownership with real-time WebSockets gives enterprise organizations secure, private communication without third-party surveillance.
- **Live Website Reference**: https://rocket.chat
- **Source Repository**: https://github.com/RocketChat/Rocket.Chat
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: TypeScript, React, Node.js, MongoDB, WebRTC, Docker
- **Primary Language(s)**: TypeScript, JavaScript, HTML
- **License of the reference repo**: NOASSERTION
- **Frontend**: React — Renders the team communication channels, direct messaging views, and admin console.; Fuselage — Rocket.Chat design system providing UI primitives, iconography, and layout components.; WebRTC — Facilitates direct peer-to-peer audio and video calling within conference channels.
- **Backend & APIs**: TypeScript — Strictly typed language governing API endpoints, business logic, and database schemas.; Node.js — Server runtime managing REST HTTP routers and persistent WebSocket connections.; Meteor — Application foundation providing real-time data sync and accounts management.
- **Data & persistence**: MongoDB — Primary document datastore storing messages, channel metadata, and user accounts via oplog.; Redis — Distributed pub/sub messaging bus synchronizing real-time events across horizontal instances.
- **Infrastructure & deploy**: Docker — Multi-stage Dockerfile packaging the compiled production Node application container.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/RocketChat/Rocket.Chat @ d5b085d)
1. **MongoDB change streams and oplog tailing for low-latency message distribution**: Rocket.Chat uses MongoDB replica set oplog tailing and change streams to broadcast document updates across horizontal application nodes, delivering sub-second real-time chat sync.
2. **Progressive migration from Meteor DDP to standard REST and WebSockets**: The architecture actively migrates legacy Meteor DDP publish/subscribe endpoints into high-performance REST APIs and typed WebSocket subscriptions, improving throughput and reducing memory overhead.
3. **Fuselage design system for consistent cross-platform presentation**: The interface in apps/meteor/ is built with Fuselage (@rocket.chat/fuselage), an internal design system that guarantees visual consistency, dark mode compatibility, and accessibility standards.
4. **Omnichannel routing engine for unified customer support bridging**: Rocket.Chat integrates an omnichannel subsystem that routes customer inquiries from WhatsApp, Livechat, Instagram, and SMS into unified agent queues with automated assignment rules.
5. **Matrix protocol federation for secure decentralized communication**: Federation capabilities allow Rocket.Chat workspaces to communicate across domains and federate with external Matrix homeservers, supporting decentralized communications without proprietary lock-in.
---
## 4. NON-NEGOTIABLE ARCHITECTURAL GUARDRAILS
1. **Monorepo & Modular Separation**:
   - Structure as a Turborepo monorepo with strict package boundaries:
     - `apps/web`: Application UI, routing, layouts, and server endpoints.
     - `packages/ui`: Shared design tokens, CSS variables, and Radix UI primitive components.
     - `packages/db`: Database schemas, client singleton, declarative migrations, and seed scripts.
     - `packages/config`: Shared TypeScript, ESLint, and build configurations.
2. **Strict Type Safety & Zero `any` Policy**:
   - Enable `strict: true`, `noImplicitAny: true`, and `strictNullChecks: true`.
   - Validate ALL external inputs, API request bodies, and query parameters with **Zod** schemas before execution.
3. **Frontend & Rendering Guidelines**:
   - Isolate interactive UI state to leaf components. Keep core pages lightweight and performant.
4. **Design System & Aesthetics**:
   - Keep every color, radius, shadow and font in a single token file (CSS variables) and consume tokens everywhere; never hardcode hex values in components.
   - Prefer crisp 1px borders and one subtle shadow scale over blurry default shadows. Pair one sans-serif for body/headings with one monospace for tags, badges, metrics, and code.
5. **Data Layer & Reliability**:
   - Write declarative schema definitions with foreign keys, composite indexes on queried filters, and automated timestamp triggers.
   - Use connection pooling and prepared statements for serverless database execution.
---
## 5. STEP-BY-STEP SCAFFOLDING ROADMAP
- **Phase 1: Workspace & Root Config**: Initialize package manager, monorepo configuration (`turbo.json`, `tsconfig.base.json`, `package.json`).
- **Phase 2: Database Schema & Client**: Set up the data layer (MongoDB, Redis): client, connection pool, models, and migration scripts.
- **Phase 3: Design Tokens & UI Primitives**: Build accessible `Button`, `Input`, `Card`, `Badge`, and layout wrappers inside `packages/ui`.
- **Phase 4: Core Application Routes & Handlers**: Implement primary authentication, user session handling, and application routes.
- **Phase 5: Quality Assurance & Build Verification**: Run `tsc --noEmit`, ESLint, Prettier, and smoke test suites to ensure zero compilation or runtime errors.
---
## 6. EXECUTION INSTRUCTIONS
1. Review all specifications, architectural guardrails, and stack choices above.
2. Present the full monorepo directory tree structure.
3. Systematically generate the complete, production-ready codebase according to the 5-phase roadmap above — starting with the root workspace setup, followed by the database schema, UI design system package, and full-stack application routes until the repository is fully scaffolded and ready to run.