t3-code-patterns

Enforce T3 Turbo monorepo coding patterns across database, ESLint, and Terraform configurations.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/leonardoacosta/central-claude --skill t3-code-patterns
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: t3-code-patterns
Source: https://github.com/leonardoacosta/central-claude/tree/main/skills/t3-code-patterns
Command: npx skills add https://github.com/leonardoacosta/central-claude --skill t3-code-patterns

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, project-aligned source of truth for T3 Turbo monorepo conventions to prevent runtime errors, migration mistakes, inconsistent schema naming, and avoidable ESLint and deployment issues across teams.

Core Features & Use Cases

  • Database import and connection patterns that prevent TypeScript recursion and incorrect psql usage.
  • Raw SQL naming guidance to map camelCase fields to snake_case Postgres columns and avoid query errors.
  • Migration and schema workflow rules that enforce Drizzle generate usage and block ad-hoc SQL drift.
  • Environment and Terraform path conventions to ensure reliable deployments and CI behavior.
  • Type ownership, null-narrowing guards, Stripe API type checking, E2E environment usage, and ESLint whitelist decorator guidance for consistent developer experience.

Quick Start

Audit the repository for T3 code pattern violations and provide a prioritized list of concrete fixes.

Frequently Asked Questions about t3-code-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce consistent database schema naming in a T3 monorepo?

Run a repository audit to check for T3 code pattern violations, generating a prioritized list of concrete fixes for schema naming, migration workflows, and ESLint configurations.

Why does my Drizzle migration workflow break in a T3 Turbo monorepo?

Drizzle migrations break when ad-hoc SQL drift occurs. Enforce Drizzle migration generation usage and block ad-hoc SQL drift to prevent migration mistakes and runtime errors across teams.

What is the correct environment variable format for Postgres connections in T3?

The correct format requires using POSTGRES_URL. Enforcing this environment variable convention ensures reliable database connections and consistent CI behavior across deployments.

How do I configure ESLint rules and whitelist exceptions in a T3 monorepo?

Configure ESLint rules by applying documented whitelist decorator guidance for exceptions. This maintains a consistent developer experience and prevents avoidable linting issues across the repository.

Does this T3 code patterns skill work with Terraform and Stripe type checks?

Yes, it applies Terraform layout conventions for reliable deployments and performs Stripe API type checking. It ensures environment paths and type ownership are correctly configured in development and CI.

What are the limitations of enforcing T3 monorepo conventions?

Limitations involve strict adherence requirements to Drizzle migration generation and documented ESLint whitelist exceptions. Deviating from these T3 Turbo patterns results in flagged violations during repository audits.