Executive Summary: Solving the Fragmented Ecosystem Problem
The Design Engineering Lab is a live technical laboratory for Agentic Engineering Workflows. This project addresses the “Context-Switching Tax” in large-scale EdTech by creating a “Single Source of Truth” monorepo that unifies shared UI packages with live documentation. It has evolved into a masterclass in Architecture-Over-Code, where I leverage Next.js 16.1 and Turborepo to create a high-integrity environment for AI-assisted development .
The Engineering Problem: The Maintenance & Documentation Gap
Traditional learning platforms often suffer from “documentation drift”—where pattern libraries and production code live in separate repositories. This fragmentation forces engineers to flip between projects to update single styles, leading to massive technical debt and slowed deployment cycles. In 2026, where AI can generate code in seconds, the bottleneck is no longer writing the code, but governing the system it lives in .
The Solution: High-Integrity Monorepo Architecture
I architected the Lab using a Turborepo monorepo to consolidate the portfolio site, documentation, and UI component library into a single, automated workspace.
- Single Source of Truth: All UI components (Atoms and Molecules) are housed in a shared package. Updates to a component like the
GlitchHeader reflect instantly across the entire ecosystem without manual syncing or repo-switching.
- Systemic Governance: By establishing strict architectural constraints and Type-safe interfaces, I created a “closed-loop” environment where AI agents (Cursor/Gemini) can reliably scaffold production-ready features .
The Innovation: AI-Native Engineering Workflow (Cursor/Gemini)
The Lab serves as a proving ground for Agentic Scaffolding. Instead of manual “vibe coding,” I utilize a custom Prompt Infrastructure-as-Code strategy:
- 3x Velocity Metric: By providing AI agents with the full context of the monorepo, I have achieved a 3x increase in traditional engineering velocity .
- Output Verification: AI handles the implementation “grunt work” (scaffolding and boilerplate), while I personally govern the architectural integrity, ensuring every component meets WCAG 2.2 AA accessibility and TypeScript safety standards.
Technical Implementation: Atomic Design & SCSS Modules
The UI follows a strict Atomic Design hierarchy (LayoutAtoms, Molecules, and Organisms) to ensure maximum reusability in EdTech environments. To protect the brand’s “Futurist Cartoon” identity, I used SCSS Modules for encapsulated styling, ensuring that design tokens like 4px charcoal linework remain consistent across all apps in the monorepo.
Integrated Documentation: The System-First Manual
A critical feature is the /docs site, which embeds Storybook 8 directly into the documentation app. This provides a live playground for testing interactive effects—such as system-state “Glitch” animations or physics-based hover states—before they are ever deployed to production.