Prisma

# MISSION: Scaffold "Prisma" 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 **Prisma**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Prisma
- **What It Does**: Prisma is an open-source next-generation ORM for Node.js and TypeScript that provides type-safe database access, schema migrations, and query generation.
- **Domain & Category**: Next-Generation Node.js & TypeScript ORM
- **Production Scale**: 1M+ MAU
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Declarative schema modeling combined with modular driver adapters allows Prisma to generate fully type-safe database clients that run consistently from Node servers to edge runtimes.
- **Live Website Reference**: https://www.prisma.io
- **Source Repository**: https://github.com/prisma/prisma
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: TypeScript, JavaScript, PostgreSQL, MySQL, SQLite, MongoDB, pnpm, Docker
- **Primary Language(s)**: TypeScript, JavaScript
- **License of the reference repo**: Apache-2.0
- **Frontend**: JavaScript — Client code generators, CLI formatting scripts, and telemetry reporting helpers.
- **Backend & APIs**: TypeScript — Core language power across the compiler, schema parser, AST models, and client generators.; Node.js — Primary runtime environment targeting Node.js 20.19 or higher across monorepo packages.
- **Data & persistence**: PostgreSQL — Relational target with full support for migrations, schema introspection, and connection pools.; MySQL — Supported relational database target tested continuously in docker-compose test fixtures.; SQLite — Embedded file-based database target used for lightweight development and edge runtimes.; MongoDB — Document database target managed through dedicated mongo-family and mongo-target packages.
- **Infrastructure & deploy**: pnpm — Workspace package manager managing strict dependency resolution and monorepo linking.; Docker — Docker Compose environment provisioning local PostgreSQL, MySQL, and Mongo test services.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/prisma/prisma @ 1c434a7)
1. **Tiered numeric package hierarchy enforces unidirectional architectural dependencies**: Packages in pnpm-workspace.yaml are strictly structured into numeric tiers (0-config, 1-framework, 2-sql, 3-targets, 9-public), preventing cyclic dependencies and enforcing strict layering from shared core up to public entrypoints.
2. **Driver adapter architecture enables universal serverless and edge compatibility**: Prisma Client delegates database transport to modular driver adapters (pg, @prisma/adapter-pg, @prisma/adapter-planetscale, @prisma/adapter-d1), allowing queries to execute natively on Cloudflare Workers, Vercel Edge, and Node.js without binary engines.
3. **Declarative schema modeling with deterministic type generation**: Developers define data models in schema.prisma. The generator compiles the schema AST directly into strongly typed TypeScript interfaces that provide compile-time auto-completion and type safety.
4. **Biome and dependency-cruiser for high-speed automated code quality guardrails**: The repository replaced legacy ESLint setups with Biome (biome.jsonc) for sub-second linting and formatting, backed by dependency-cruiser (dependency-cruiser.config.mjs) to enforce package boundary invariants.
5. **Comprehensive multi-engine integration test harness in Docker**: docker-compose.yaml provisions concurrent database instances for PostgreSQL, MySQL 8, MariaDB, SQL Server, and MongoDB, ensuring that query generation passes parity tests across all SQL dialects.
---
## 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 (PostgreSQL, MySQL, SQLite, MongoDB): 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.