Deno

# MISSION: Scaffold "Deno" 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 **Deno**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Deno
- **What It Does**: Deno is a Rust-based runtime for JavaScript, TypeScript, and WebAssembly that embeds the V8 engine on Tokio, ships secure-by-default permissions, and bundles Deno.Kv, the Cache API, and npm compatibility into one binary.
- **Domain & Category**: Secure JavaScript & TypeScript Runtime
- **Production Scale**: 20+ people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: A single Cargo workspace embeds V8 directly in Rust so the CLI, its Web API extensions, and npm compatibility ship as one statically-linked binary instead of relying on a separate Node.js toolchain.
- **Live Website Reference**: https://deno.com
- **Source Repository**: https://github.com/denoland/deno
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Rust, TypeScript, V8, Tokio, SQLite
- **Primary Language(s)**: Rust, TypeScript, JavaScript
- **License of the reference repo**: MIT
- **Backend & APIs**: Rust — Implements the CLI, module graph resolution, permissions model, and every extension crate in the Cargo workspace.; V8 — Default JavaScript and WebAssembly engine, embedded through the deno_v8 facade crate and exposed as the workspace v8 dependency.; Tokio — Async runtime driving the CLI and runtime crates network, filesystem, and subprocess I/O.; TypeScript — Implements the CLI-facing bootstrap and runtime JS/TS layer that gets precompiled into the V8 snapshot.
- **Data & persistence**: SQLite — Backs Deno.Cache and local Deno.Kv storage via the bundled denokv_sqlite and rusqlite crates.
- **Infrastructure & deploy**: GitHub Actions — Runs CI, ecosystem/node-compat test suites, and the cargo/npm publish and release-tagging pipelines.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/denoland/deno @ abd2207)
1. **One Cargo workspace splits the CLI from ~70 extension and lib crates**: Cargo.toml lists cli, runtime, every ext/* Web API implementation (fetch, crypto, kv, webgpu, node, …) and every libs/* helper (npm, node_resolver, lockfile, eszip) as separate workspace members with independently versioned deno_* crates, so an extension can be compiled, tested, and released without touching the CLI binary.
2. **V8 is the default engine but QuickJS is a feature-gated alternative**: cli/Cargo.toml defines a default v8 feature (deno_core/v8, v8/v8) alongside an opt-in quickjs feature (deno_core/quickjs, v8/quickjs), letting the same deno_core abstraction target either JS engine without a source-level fork of the CLI.
3. **Deno.Kv and the Cache API share one bundled SQLite backend**: The workspace pulls in denokv_sqlite with default features disabled to avoid a second bundled SQLite, and ext/kv plus ext/cache implement the Deno.Kv and Cache Web API surfaces on top of it, so both features ship without an external database dependency.
4. **The runtime JS layer is precompiled into a V8 snapshot at build time**: runtime/snapshot.rs and the cli/snapshot crate (deno_snapshots) build a startup snapshot from runtime/js and cli/js during compilation; an hmr feature flag disables snapshotting so the JS sources are loaded from disk instead, for faster local iteration on the runtime layer.
5. **npm compatibility is isolated into dedicated resolver and installer crates**: libs/npm, libs/npm_cache, libs/npm_installer, libs/npmrc, and libs/node_resolver implement npm registry resolution, the global npm cache, and Node-style module resolution as standalone crates consumed by cli/lib, keeping Node/npm compatibility logic out of the core module graph code.
6. **Desktop embedding gets its own C-ABI runtime crate**: cli/rt_desktop/Cargo.toml builds denort_desktop as a cdylib (crate-type cdylib) depending on the laufey crate, producing a libdenort shared library that desktop apps can embed, separate from the denort executable built by cli/rt.
---
## 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 (SQLite): 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.