Build a full-stack TanStack Start app on Cloudflare Workers from scratch — SSR, file-based routing, server functions, D1+Drizzle, better-auth, Tailwind v4+shadcn/ui. Use whenever the user mentions TanStack Start, asks to scaffold a full-stack Cloudflare app with SSR, wants an SSR dashboard, or asks for a React 19 + Cloudflare Workers app with file-based routing and server functions — even if they don't name TanStack Start specifically. No template repo — Claude generates every file fresh per pro
Detected risks:
The tanstack-start skill builds a complete full-stack TanStack Start application on Cloudflare Workers from scratch, generating every file fresh rather than cloning a template. The stack includes TanStack Start v1 (SSR, file-based routing, and server functions via Nitro), React 19 with Tailwind v4 and shadcn/ui, D1 with Drizzle, and better-auth (Google OAuth and email/password).
It provides the full project file tree, runtime and dev dependencies with versions, and scripts, then walks through gathering project info, initializing config (a vite.config.ts with the Cloudflare plugin first, wrangler.jsonc, tsconfig, and a .dev.vars with a generated auth secret), defining the Drizzle schema with D1-specific rules (integer timestamps, text primary keys, and bound-parameter limits), configuring better-auth, and generating routes, components, and server functions. It highlights critical Cloudflare details such as importing env from cloudflare:workers rather than process.env and creating the Drizzle client per request.
It is most useful for developers who want a working, opinionated full-stack React app on Cloudflare Workers with SSR, authentication, and a database, scaffolded file by file.
A complete full-stack TanStack Start app on Cloudflare Workers with SSR, file-based routing, server functions, D1 and Drizzle, better-auth, and Tailwind v4 with shadcn/ui.
No. It generates every file fresh per project rather than cloning a template or running a scaffold command.
TanStack Start v1 and React 19 on Cloudflare Workers, with D1 and Drizzle for data and better-auth for Google OAuth and email/password authentication.
Putting the Cloudflare Vite plugin first, using nodejs_compat, importing env from cloudflare:workers instead of process.env, and creating the Drizzle client per request.
D1 conventions like integer Unix timestamps, text primary keys, keeping bound parameters under 100 per query, and applying migrations locally and remotely via wrangler.
Quick Setup:
.claude/skills/Repository
jezweb/claude-skills