Starlight

# MISSION: Scaffold "Starlight" 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 **Starlight**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Starlight
- **What It Does**: Starlight is a documentation website framework built on Astro, optimized for high performance, accessibility, and SEO.
- **Domain & Category**: Documentation Portal
- **Production Scale**: Solo
- **Development Mode**: CLASSIC
- **Architectural Rationale**: Leveraging Astro static rendering delivers 100/100 Lighthouse performance with zero JavaScript by default and built-in client-side WebAssembly search.
- **Live Website Reference**: https://starlight.astro.build
- **Source Repository**: https://github.com/withastro/starlight
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Astro, TypeScript, Tailwind CSS, MDX, pnpm, Playwright
- **Primary Language(s)**: TypeScript, Astro, CSS
- **License of the reference repo**: MIT
- **Frontend**: Astro — Island architecture framework rendering zero-JavaScript static HTML by default.; TypeScript — Strict type safety across configuration schemas, route data, and component interfaces.; Tailwind CSS — Optional documentation styling integration provided by @astrojs/starlight-tailwind.; MDX — Rich content format enabling interactive UI components inside technical documentation.
- **Backend & APIs**: Pagefind — Static client-side search engine indexed at build time without external server compute.
- **Infrastructure & deploy**: pnpm — Monorepo workspace package manager linking packages, themes, and example documentation sites.; Playwright — End-to-end browser test automation in docs/ verifying accessibility and cross-browser layouts.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/withastro/starlight @ 6cf72a2)
1. **Zero-JS baseline architecture powered by Astro Island Architecture**: Starlight renders documentation pages as pure static HTML and CSS by default. Client JavaScript is only downloaded when interactive islands (such as search or theme toggles) explicitly require it.
2. **Offline-first, client-side search via Pagefind WASM**: Rather than requiring external third-party search SaaS (like Algolia), Starlight embeds Pagefind (packages/starlight/package.json) to generate static search indexes during the build that run locally via WebAssembly.
3. **Expressive Code integration for syntax highlighting and code blocks**: Starlight integrates astro-expressive-code natively, providing editor frame chrome, line highlighting, terminal window chrome, and copy buttons without runtime client dependencies.
4. **Strict Zod schema validation for frontmatter and navigation**: Document frontmatter metadata, sidebar navigation hierarchies, and internationalization tables are validated at build time using strict Zod schemas (packages/starlight/src/schema.ts).
5. **Multi-lingual content tracking and internationalization via Lunaria**: The documentation workspace utilizes Lunaria (docs/lunaria.config.ts) to track translation progress across dozens of languages, reporting out-of-date localized documentation pages automatically.
---
## 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**:
   - Leverage Astro's Island Architecture: keep pages static (.astro) by default for zero-JS baseline and instant Google search indexing. Hydrate interactive React components with 'client:load' or 'client:visible' only where needed for user state.
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.