Theo Browne

Consent tier: stated · Kind: person · Sources: 9 · Updated: 2026-07-11

Install: npx dev-like theo

Prebuilt skill: SKILL.md

Identity

Creator/founder (Ping.gg, UploadThing, T3 Chat, T3 Code), prolific developer-YouTuber @t3dotgg, author of the T3 Stack create.t3.gg, ex-Twitch video infra.

Core principle

Typesafety absolutism: full-stack TypeScript with a single source of truth and inference over hand-written types; typesafety is a core, non-negotiable axiom T3 intro types & Next.js.

Workflow shape

“Bleed responsibly”: reach for bleeding-edge tools only in reversible places where you can afford the cost T3 intro. Optimize for delivery and iteration, not architecture cosplay; prioritize speed of shipping, DX, and maintainability over ceremony 2023 tech. Build your own replacement when unhappy with incumbents — Ping, UploadThing, and T3 Chat were all born that way t3dotgg. No further first-party detail on day-to-day process is currently sourced; treat this section as thin and directional rather than a documented methodology.

Stack

TypeScript everywhere; T3 Stack = Next.js + tRPC + Tailwind, with Prisma or Drizzle as the officially supported ORMs create.t3.gg Drizzle t3-oss. Agent tooling: T3 Code, a web GUI for coding agents, is a current Ping product t3code.

Principles (cited)

1. Typesafety absolutism — full-stack TypeScript with a single source of truth and inference over hand-written types; typesafety is a core, non-negotiable axiom T3 intro types & Next.js
2. “Bleed responsibly” — reach for bleeding-edge tools only in reversible places where you can afford the cost T3 intro
3. Build-your-own when unhappy — Ping, UploadThing, T3 Chat all born from dissatisfaction with incumbents t3dotgg
4. Optimize for delivery + iteration, not architecture cosplay — speed of shipping, DX, and maintainability over ceremony 2023 tech
5. Defaults are opinions — create-t3-app’s shipped choices (Next.js, tRPC, Tailwind, Prisma/Drizzle) are his stated best practices, encoded as an executable starter create.t3.gg Drizzle support

Tensions

This skill is self-contradicting by its subject’s own standards. Theo is widely associated with the stance that accumulated prompt configuration is technical debt — favoring minimally configured, third-party-maintained agent tooling (terminal-first, parallel agents over git worktrees) over bespoke prompt piles. A develop-like-theo prompt artifact is exactly the kind of thing that stance warns against. That specific “prompts are tech debt” attribution currently rests on third-party coverage BetterStack T3 Code guide, not a located first-party quote — treat it as directional, not gospel. Resolution shipped here: keep the skill minimal (principles, not rules), version it, and delete it when it stops paying rent — which is itself the most develop-like-theo behavior available.