Supabase Studio

# MISSION: Scaffold "Supabase Studio" 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 **Supabase Studio**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Supabase Studio
- **What It Does**: Supabase Studio is an open-source administrative dashboard for managing PostgreSQL databases, authentication, storage, and edge functions.
- **Domain & Category**: Developer Tool
- **Production Scale**: 20+ people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Centering the developer experience around PostgreSQL allows Supabase Studio to provide spreadsheet-like table editing and SQL execution directly on production databases.
- **Live Website Reference**: https://supabase.com
- **Source Repository**: https://github.com/supabase/supabase
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Next.js, React, TypeScript, PostgreSQL, Tailwind CSS, Docker, Deno
- **Primary Language(s)**: TypeScript, MDX, JavaScript
- **License of the reference repo**: Apache-2.0
- **Frontend**: Next.js — Powers application routing, server-side data fetching, and API route proxies in apps/studio.; React — Renders the Table Editor, SQL Scratchpad, Database Visualizer, and Auth user panels.; Tailwind CSS — Provides utility styling adhering to the Supabase dark theme and design system tokens.; Monaco Editor — Embedded code editor powering the SQL Scratchpad with syntax highlighting and autocompletion.
- **Backend & APIs**: TypeScript — Ensures strict type-checking across frontend interfaces, database models, and API proxies.; Deno — Serverless runtime executing Supabase Edge Functions in TypeScript at the network edge.
- **Data & persistence**: PostgreSQL — The primary database engine, extended with pgvector, PostGIS, pg_cron, and RLS policies.
- **Infrastructure & deploy**: Docker — Docker Compose orchestration suite in docker/ running local PostgreSQL, PostgREST, and Kong.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/supabase/supabase @ 66d4b4c)
1. **PostgreSQL as the central application and authorization engine**: Supabase Studio delegates authorization, table schemas, and data manipulation directly to PostgreSQL system catalogs and Row-Level Security (RLS) policies rather than custom proprietary application servers.
2. **Next.js App and Pages architecture for administrative tooling**: Studio (apps/studio) is structured as a Next.js application that combines client-side grid components (DataGrid, Table Editor) with server-side API proxy routes that interface with PostgreSQL.
3. **Interactive SQL Scratchpad with Monaco Editor and query snippets**: Studio embeds Monaco Editor (@monaco-editor/react) with customized PostgreSQL SQL language definitions, providing autocomplete, query execution history, and pre-built administrative script templates.
4. **Modular open-source service composition via Kong API gateway**: The Supabase stack in docker/ unifies independent open-source services (PostgreSQL, PostgREST, GoTrue, Realtime, Storage API) behind a single Kong API gateway proxy.
5. **Client-side state synchronization with TanStack Query and Zustand**: Studio leverages TanStack Query for caching schema catalogs and table structures, paired with Zustand stores for ephemeral UI state (sidebar collapses, active editor tabs, modal overlays).
---
## 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 (PostgreSQL): 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.