Umami

# MISSION: Scaffold "Umami" 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 **Umami**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Umami
- **What It Does**: Privacy-focused, open-source web analytics platform and Google Analytics alternative built with Next.js, React, and PostgreSQL.
- **Domain & Category**: Web Analytics
- **Production Scale**: Solo
- **Development Mode**: HYBRID
- **Architectural Rationale**: Umami provides cookie-free, GDPR-compliant website metrics and session replays with simple self-hosting and zero data monetization.
- **Live Website Reference**: https://umami.is
- **Source Repository**: https://github.com/umami-software/umami
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: TypeScript, Next.js, React, Prisma, PostgreSQL, ClickHouse, Redis, Docker
- **Primary Language(s)**: TypeScript, JavaScript, CSS, Dockerfile, Shell
- **License of the reference repo**: MIT
- **Frontend**: Next.js — Full-stack application framework serving analytics dashboards and API collection routes; React — Interactive analytics interface rendering timeseries charts, maps, and conversion funnels
- **Backend & APIs**: TypeScript — Type-safe codebase powering tracker compilation, collection APIs, and MCP servers
- **Data & persistence**: Prisma — ORM client managing database models, migrations, and read replicas for analytics entities; PostgreSQL — Primary relational persistence layer storing accounts, websites, events, and sessions; ClickHouse — High-volume columnar analytical store used in enterprise deployments for event queries; Redis — In-memory cache for visitor sessions, IP anonymization salts, and rate limiting
- **Infrastructure & deploy**: Docker — Production alpine container images packaging Next.js standalone builds and database scripts
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/umami-software/umami @ ec0ff50)
1. **Dual Persistence Support for PostgreSQL and ClickHouse**: Decouples relational query models through Prisma while offering high-throughput columnar event ingestion via native ClickHouse drivers for large deployments.
2. **Standalone Rollup Build for Privacy-First Tracker Script**: Compiles a lightweight, zero-dependency tracking snippet (under 3KB) using Rollup that collects analytics without setting persistent user cookies.
3. **Built-in Model Context Protocol Server**: Exposes analytics stats, real-time traffic queries, and metric aggregations to AI agents through a dedicated MCP server package (@umami/mcp).
4. **Session Replay Integration with rrweb**: Incorporates a privacy-conscious DOM session recorder in src/recorder using rrweb to capture user navigation funnels and playback sessions.
---
## 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**:
   - Utilize Next.js 15 App Router: default to React Server Components (RSC) for data fetching. Handle mutations through Server Actions with Zod validation. Keep 'use client' directives restricted strictly to interactive leaf components.
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 (Prisma, PostgreSQL, ClickHouse, 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.