What problem does it solve? Deploying a TanStack Start app requires choosing the correct adapter, wiring the right Vite plugin order, matching package.json scripts to the build output, and avoiding the classic production bug of reading process.env at module scope, which breaks on edge runtimes and can leak secrets into client bundles. ## Core Features & Use Cases - Per-host adapter configs: Complete vite.config.ts templates for Cloudflare Workers (@cloudflare/vite-plugin + wrangler.jsonc), Netlify (@netlify/vite-plugin-tanstack-start), and Nitro-based targets (Vercel, Node, Docker, Bun, Railway). - Static prerendering: Configure tanstackStart({ prerender }) with routes globs, crawlLinks, and autoStaticPathsDiscovery, including which route types are excluded from auto-discovery. - Production env-var rules and checklist: Enforce per-request process.env reads, correct plugin ordering, React 19 pinning for Bun, and a pre-deploy checklist. - Use Case: You are shipping a TanStack Start app to Cloudflare Workers and your secrets are undefined in production. This Skill identifies the module-scope env read, fixes the plugin order, and provides the full wrangler.jsonc and deploy scripts. ## Quick Start Deploy my TanStack Start app to Cloudflare Workers and fix my vite.config.ts and wrangler setup.