What problem does it solve? Structuring a T3 Turbo monorepo involves recurring decisions about when to extract packages, how to wire Turborepo task dependencies, and how to keep TypeScript project references consistent — mistakes here surface as broken builds, circular dependencies, and tools silently targeting the wrong database. ## Core Features & Use Cases - Package Extraction Rules: Decision tables for when code belongs in packages/ versus staying inline in an app, preventing premature extraction. - Turborepo and pnpm Configuration: Canonical turbo.json task graphs, workspace filtering commands, and dotenvx run --overload env-loading patterns that stop stray shell variables from shadowing project .env values. - Boundary Packages: Reference patterns for a schema-only packages/contracts (one runtime dependency) and a pino + OpenTelemetry packages/logger leaf package. - Use Case: When adding a new shared package to a T3 monorepo, follow the five-step checklist (package.json exports, root tsconfig paths, project references, pnpm filter install, turbo typecheck) to avoid Cannot find module errors. ## Quick Start Ask the agent to review your monorepo structure and apply the T3 monorepo patterns for package extraction, Turbo tasks, and workspace dependencies.