RustDesk

# MISSION: Scaffold "RustDesk" 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 **RustDesk**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: RustDesk
- **What It Does**: RustDesk is an open-source remote desktop client and protocol, written in Rust with a Flutter UI, that connects two peers via a rendezvous/relay server or a self-hosted one.
- **Domain & Category**: Remote Desktop Infrastructure
- **Production Scale**: 6-20 people
- **Development Mode**: CLASSIC
- **Architectural Rationale**: A shared Rust core (libs/hbb_common) keeps the client and the separate rustdesk-server protocol implementation in sync, while Flutter gives one UI codebase across desktop and mobile targets.
- **Live Website Reference**: https://rustdesk.com
- **Source Repository**: https://github.com/rustdesk/rustdesk
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Rust, Flutter, Dart, WebRTC, Docker
- **Primary Language(s)**: Rust, Dart
- **License of the reference repo**: AGPL-3.0
- **Frontend**: Flutter — Renders the desktop and mobile UI (connection manager, session view, settings) on top of the native Rust core.; GTK — Provides native GTK bindings for Linux tray icon and windowing integration.
- **Backend & APIs**: Rust — Implements the core engine: screen capture, input injection, clipboard, audio and the connection/session state machine.; WebRTC — hbb_common is built with the webrtc feature for ICE-based NAT traversal between peers.
- **Infrastructure & deploy**: Docker — Provides a reproducible Debian-based container with vcpkg and the Rust toolchain for building Linux binaries.; GitHub Actions — Builds and tests the Rust core and Flutter clients across desktop and mobile targets on every change.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/rustdesk/rustdesk @ 0b3a1dd)
1. **Workspace splits shared server code from client-only platform code**: libs/hbb_common holds the codec, config and tcp/udp wrapper shared with the separate rustdesk-server project, while libs/base is explicitly reserved for protobuf, filesystem and platform code "that only RustDesk itself uses," per the comment at the top of libs/base/Cargo.toml.
2. **DRM screen capture is loaded at runtime, never link-time linked**: libs/scrap/Cargo.toml documents that the drm feature dlopens libdrmtap.so.0 at a commit pinned by DRMTAP_SHA in build.py instead of depending on the libdrmtap-sys crate, "which would defeat the dlopen model," so a missing library falls back to PipeWire instead of failing to build.
3. **Legacy Sciter UI is kept only as a deprecated fallback to Flutter**: src/ui holds the older Sciter-based interface, marked obsolete in the README, while flutter/lib is the primary GUI built and shipped through flutter-build.yml; new features target Flutter only.
4. **Cross-platform dependencies are forked under the rustdesk-org GitHub org**: Cargo.toml pulls cpal, arboard, rdev, tao, wallpaper, keepawake and several other crates from git branches under github.com/rustdesk-org instead of crates.io, so platform-specific patches (for example the osx-screencapturekit branch of cpal) ship without waiting on upstream releases.
5. **libxdo is replaced by an in-repo stub to drop a hard runtime dependency**: The [patch.crates-io] section of Cargo.toml redirects libxdo-sys to libs/libxdo-sys-stub, a dynamic-loading wrapper so RustDesk builds and runs on Wayland-only systems that lack libxdo installed at compile or link time.
6. **Codec and capture backends are compiled in per platform via Cargo features**: Cargo.toml defines hwcodec, vram, mediacodec and drm as opt-in features layered on scrap, so a given build only links the hardware video paths its target platform needs instead of every backend at once.
---
## 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.