Taxonomy

# MISSION: Scaffold "Taxonomy" 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 **Taxonomy**.
---
## 1. PROJECT SPECIFICATIONS & BENCHMARK
- **Reference Architecture**: Taxonomy
- **What It Does**: An open-source Next.js 13 App Router reference app combining authentication, subscriptions, MDX docs, and a dashboard editor. Officially archived by its author.
- **Domain & Category**: Open-Source SaaS Template
- **Production Scale**: 1-5 people
- **Development Mode**: AI-AGENT
- **Architectural Rationale**: Built to demonstrate the App Router, server components, and Next.js 13 data fetching patterns in one realistic, full-featured codebase.
- **Live Website Reference**: https://tx.shadcn.com
- **Source Repository**: https://github.com/shadcn-ui/taxonomy
---
## 2. PRODUCTION TECH STACK
- **Full Stack Array**: Next.js, React, TypeScript, Prisma, NextAuth.js, Radix UI, Tailwind CSS, Stripe, Zod
- **Primary Language(s)**: TypeScript, MDX
- **License of the reference repo**: MIT
- **Frontend**: Next.js — Implements the App Router across (auth), (dashboard), (docs), (editor) and (marketing) route groups in app/.; React — Hydrates interactive UI (editor, dashboard, forms) inside the Next.js App Router.; Tailwind CSS — Styles marketing, docs, and dashboard shells via utility classes and a custom config.; Radix UI — Provides unstyled accessible primitives wrapped by the local components/ui kit.
- **Backend & APIs**: NextAuth.js — Handles GitHub and email sign-in via the Prisma adapter in lib/auth.ts.; Stripe — Implements subscription billing and webhooks via lib/stripe.ts and lib/subscription.ts.
- **Data & persistence**: Prisma — Models Post and User in prisma/schema.prisma; generated client is used by lib/db.ts.; PlanetScale — README lists PlanetScale as the MySQL-compatible target database; not directly verified in captured manifests.
- **Infrastructure & deploy**: Vercel — README and @vercel/og/@vercel/analytics dependencies suggest the app is designed to deploy on Vercel; no vercel.json is present in the captured tree.
---
## 3. KEY ARCHITECTURAL DECISIONS (audited from https://github.com/shadcn-ui/taxonomy @ 298a885)
1. **Single Next.js app hosts marketing, docs, dashboard, and auth route groups**: The app/ directory splits routes into (auth), (dashboard), (docs), (editor), and (marketing) groups so each area can have its own layout while sharing the same Next.js 13 App Router build defined in app/layout.tsx.
2. **Prisma is the single data-access layer, generated on every install**: package.json runs `prisma generate` as a postinstall script, and lib/db.ts exports a shared PrismaClient instance, making prisma/schema.prisma the sole source of truth for the Post and User models.
3. **Content lives in MDX files compiled by Contentlayer, not a CMS**: content/blog, content/docs, content/guides, content/authors, and content/pages are MDX collections processed by contentlayer.config.js into typed data consumed by the (docs) and (marketing) route groups.
4. **Radix UI primitives are wrapped into a local components/ui kit**: More than two dozen @radix-ui/react-* packages are direct dependencies in package.json, composed into project-owned wrappers under components/ui rather than pulling in a pre-styled component library.
5. **Billing runs through Stripe, config-driven from config/subscriptions.ts**: lib/stripe.ts and lib/subscription.ts implement subscription status checks against plan definitions in config/subscriptions.ts, surfaced to users through components/billing-form.tsx.
6. **Repository is officially archived and kept as a historical reference**: The README states the project has been officially archived because Next.js has changed significantly since the App Router public preview, and points readers to the Vercel Templates directory for current starters instead.
---
## 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**:
   - Utilize Next.js 15 App Router: default to React Server Components (RSC) for data fetching. Handle mutations through Server Actions with Zod validation. Keep 'use client' directives restricted strictly to interactive leaf components.
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 (Prisma, PlanetScale): 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.