create-t3-turbo

Orchestrates build tasks across multiple applications and packages using Turborepo's distributed task graph execution with automatic caching. Analyzes package dependencies declared in turbo.json to determine task ordering, parallelizes independent builds, and caches outputs to avoid redundant compilation. Supports incremental builds by detecting file changes and only re-executing affected tasks in the dependency graph.

Implements a type-safe RPC layer using tRPC that shares TypeScript types between server (Next.js API routes) and clients (web and mobile) without code generation. The @acme/api package exports router definitions with Zod validators from @acme/validators, ensuring request/response validation at compile-time and runtime. Both Next.js and Expo applications import the same tRPC client, receiving full IDE autocomplete and type checking for API calls.

Configures Next.js app for deployment to Vercel with automatic builds triggered by git pushes. Environment variables are managed through Vercel's dashboard or .env.local files, with separate configurations for development, preview, and production environments. Turborepo caching is integrated with Vercel's build system to skip rebuilding unchanged packages, reducing deployment times.

Configures Expo app for deployment to iOS and Android using EAS Build and EAS Submit services. Manages app signing certificates, provisioning profiles, and build configurations through EAS. Supports over-the-air (OTA) updates via Expo Updates, allowing code changes to be deployed without app store review. Environment variables are managed through eas.json and EAS secrets.

Defines GitHub Actions workflows in .github/workflows/ci.yml that run on every pull request and push to main branch. Executes linting (ESLint), type checking (TypeScript), and tests across all packages using Turborepo's task execution. Caches dependencies and build artifacts to speed up workflow runs. Blocks merging if any checks fail, enforcing code quality standards.

Centralizes ESLint and Prettier configuration in tooling/eslint and tooling/prettier directories, with shared rules and formatting settings applied to all packages and apps. Each package extends the base configuration, ensuring consistent code style and linting rules across the monorepo. Prettier is integrated with ESLint to auto-fix formatting issues during development and CI/CD.

Manages database schema using Drizzle ORM's TypeScript-first approach, where schema definitions in @acme/db package generate both SQL migrations and TypeScript types. The schema is defined as TypeScript objects (e.g., users table with columns), and Drizzle generates type-safe query builders that infer column types at compile-time. Migrations are generated from schema changes and can be applied to PostgreSQL/MySQL/SQLite databases.

Provides a @acme/ui package exporting React components styled with Tailwind CSS that work on both web (Next.js) and mobile (Expo/React Native). Components use conditional rendering and platform-specific imports to adapt layouts for web and native platforms. Tailwind configuration is centralized in tooling/tailwind and consumed by both apps, ensuring consistent design tokens (colors, spacing, typography) across platforms.

The @acme/auth package provides authentication logic (session creation, token validation, user context) that is consumed by both Next.js and Expo apps through a shared authentication context. Handles session persistence, token refresh, and user state synchronization across platform-specific storage (localStorage on web, AsyncStorage on mobile). Integrates with the tRPC API layer to validate sessions server-side and return authenticated user data.

Centralizes TypeScript compiler options in tooling/typescript and extends them across all packages and applications using TypeScript's extends mechanism. Each package (api, auth, db, ui, validators) and app (nextjs, expo) inherits base compiler settings (strict mode, module resolution, target) while allowing package-specific overrides. This ensures consistent type checking across the monorepo and prevents type errors from propagating between packages.

Uses pnpm workspaces and the workspace:* protocol to link local packages during development, automatically resolving @acme/api, @acme/db, @acme/auth, @acme/ui, and @acme/validators as symlinks to their source directories. When packages are published to npm, pnpm automatically converts workspace:* references to concrete version numbers. This enables zero-latency local development while maintaining proper versioning for published packages.

Integrates tRPC into Next.js 15's App Router using server components and API routes, enabling server-side rendering with type-safe data fetching. The nextjs app imports tRPC client from @acme/api and uses it in server components to fetch data at build-time or request-time, with automatic type inference. API routes are generated from the tRPC router and handle client requests, with session validation middleware protecting authenticated endpoints.

Integrates tRPC client into Expo Router's file-based routing system, enabling type-safe API calls from mobile screens. The expo app imports tRPC client from @acme/api and uses it in React Native components with hooks (useQuery, useMutation), handling loading and error states. Expo Router manages navigation between screens while tRPC handles data fetching, with automatic type inference for API responses.

The @acme/validators package exports Zod schemas that define request and response shapes for all tRPC procedures. These schemas are used both server-side (in tRPC router definitions to validate inputs) and client-side (for runtime validation of responses). Zod provides runtime type checking and generates TypeScript types automatically, ensuring validation logic is defined once and reused across web and mobile.