Actix Web

# MISSION: Scaffold "Actix Web" 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 **Actix Web**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Actix Web
- **What It Does**: Actix Web is a fast, pragmatic Rust web framework with its own HTTP/1 and HTTP/2 implementation, extractors, middleware, optional routing macros, WebSockets, static files, multipart and the awc HTTP client.
- **Domain & Category**: Rust Web Framework
- **Production Scale**: 1M+ MAU
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Actix Web owns its HTTP stack in actix-http and keeps router, codegen, files, multipart, test utilities and the awc client in one workspace, so the whole request path, TLS options and public API are versioned and semver-checked together.
- **Live Website Reference**: https://actix.rs
- **Source Repository**: https://github.com/actix/actix-web
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Rust, Actix-web, Tokio, WebSockets, OpenSSL, GitHub Actions
- **Primary Language(s)**: Rust, Shell, Just
- **License of the reference repo**: Apache-2.0
- **Backend & APIs**: Rust — Implementation language for every crate; the workspace sets edition 2021 and a minimum Rust version of 1.88.; Actix-web — The actix-web crate (version 4 in its manifest): App, HttpServer, extractors, middleware and routing macros.; actix-http — Own HTTP/1.x and HTTP/2 implementation (h2 behind the http2 feature) with compression and WebSocket protocol support.; Tokio — Underlying async runtime; the README lists full Tokio compatibility and #[actix_web::main] or #[tokio::main] entry points.; WebSockets — ws feature in actix-http plus client WebSockets in awc; actix-web-actors is kept only as a deprecated crate.; OpenSSL — Optional TLS backend next to several Rustls versions (0.20 to 0.23), each behind its own feature flag.
- **Infrastructure & deploy**: GitHub Actions — Workflows for CI, lint, coverage, benchmarks, post-merge checks and semver checks on public APIs.; just — justfile collects local development and release recipes; scripts/ holds bump and publish helpers.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/actix/actix-web @ 30c831f)
1. **Own HTTP stack in actix-http instead of building on Hyper**: actix-http/Cargo.toml describes the crate as "HTTP types and services for the Actix ecosystem" and implements HTTP/1.x itself, with HTTP/2 through the h2 crate behind the http2 feature, WebSocket framing behind ws, and brotli, gzip and zstd compression as features. The framework controls its whole request path rather than delegating to Hyper.
2. **One workspace for server, router, client, files, multipart and test crates**: The root Cargo.toml lists actix-web, actix-http, actix-router, actix-web-codegen, actix-files, actix-multipart, actix-multipart-derive, actix-test, actix-http-test and the awc HTTP client as members, and [patch.crates-io] points every one of them at its local path so cross-crate changes are tested together.
3. **Routing macros are optional sugar over a standalone router**: actix-router is a separate crate for resource path matching, with regex-based matching behind a unicode feature and regex-lite otherwise. actix-web-codegen supplies the #[get("/path")] style attribute macros, enabled by the default macros feature, so routes can be registered with or without macros.
4. **TLS backends selected per version through feature flags**: actix-http and awc expose openssl plus separate rustls-0_20, rustls-0_21, rustls-0_22 and rustls-0_23 features, so applications can match the Rustls version used elsewhere in their dependency tree instead of being forced onto one.
5. **API stability checked in CI**: semver-checks.yml runs alongside ci.yml and lint.yml, each crate lists allowed external types under package.metadata.cargo_check_external_types, and actix-web keeps MIGRATION-1.0 through MIGRATION-4.0 guides, which shows how much weight the project puts on not breaking the public API within a major version.
---
## 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: 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.