// the find
BearStudio/start-ui-web
🚀 Start UI [web] is an opinionated UI starter from the 🐻 BearStudio Team with ⚙️ Node.js, 🟦 TypeScript, ⚛️ React, 📦 TanStack Start, 💨 Tailwind CSS, 🧩 shadcn/ui, 📋 React Hook Form, 🔌 oRPC, 🛠 Prisma, 🔐 Better Auth, 📚 Storybook, 🧪 Vitest, 🎭 Playwright
A full-stack TypeScript starter built around TanStack Start, oRPC, Prisma, Better Auth, and shadcn/ui — BearStudio's actual production stack for client work. It ships with a working books CRUD demo, magic-link auth, file uploads via MinIO, i18n, Storybook for every UI component, and both Vitest browser tests and Playwright E2E. The target is teams who want to skip the first two weeks of wiring and start from something that already works.
The form layer is unusually complete — every common input type (combobox, OTP, date picker, file upload, checkbox group) has its own typed field-controller wrapper, Storybook story, and browser spec. Most starters leave this as an exercise for the reader. The dual-app layout (app/ for end users, manager/ for admins) maps directly to how real client projects are structured and is baked into routing from the start rather than bolted on later. The dev email setup is genuinely useful: Maildev catches all outbound email locally, and there's a live preview endpoint for every template with locale and prop overrides — you can iterate on email design without a real SMTP server. oRPC gives you end-to-end type safety from server procedure to client call, plus an OpenAPI doc endpoint at /api/openapi/app that you'd otherwise have to write by hand.
TanStack Start is still pre-1.0 in practice — the API has shifted significantly across minor versions and you're accepting that some upgrade will break your routing or loader patterns in ways the changelog underrepresents. oRPC is even newer; it's well-designed but has roughly zero Stack Overflow coverage, and if you hit an edge case you're reading source code. Better Auth handles the magic-code flow well but if you need anything beyond email auth and basic sessions (SAML, device trust, org-level permissions), you'll be writing it yourself or waiting for the library to mature. The local dev setup requires Docker for three containers (Postgres, MinIO, Maildev), and MinIO in local dev means you need an S3-compatible service in production — the README doesn't address this production gap, so the file upload feature is one of those things that works locally and then needs a separate decision before you can deploy.