superpowers-tanstack-start

Design, implement, audit, or debug authentication and authorization in TanStack Start. Use for sessions, cookies, login, logout, OAuth state and PKCE, password reset, CSRF, rate limiting, protected routes, RBAC, tenant isolation, secret handling, or auth tests.

Prepare, review, or debug TanStack Start production builds and deployments. Use for Vite or Rsbuild output, Cloudflare Workers, Netlify, Railway, Nitro, Node, Docker, Bun, Vercel, Appwrite, environment wiring, assets, CDN caching, early hints, observability, health checks, or production-only failures.

Design, implement, review, or debug TanStack Start middleware and server routes. Use for request middleware, server-function middleware, typed context, global middleware, CSRF, request or response transforms, API endpoints, webhooks, health routes, HTTP methods, headers, status codes, or route conflicts.

Choose, implement, review, or debug TanStack Start rendering behavior. Use for SSR, selective SSR, SPA mode, static prerendering, ISR, streaming, deferred hydration, hydration mismatches, React Server Components, SEO output, or caching interactions.

Design, implement, review, or debug TanStack Start and TanStack Router routes. Use for file-route structure, root routes, layouts, params, search validation, loaders, loader dependencies, navigation, preloading, pending states, errors, not-found behavior, or route-tree generation.

Implement, secure, review, or debug TanStack Start server functions. Use for createServerFn handlers, input validation, request context, redirects, not-found results, raw responses, progressive enhancement, streaming, static functions, cancellation, serialization, or server-only data access.

Create verification plans, write tests, review coverage, or diagnose TanStack Start failures. Use for validators, server functions, middleware, server routes, route loaders, rendering, hydration, production builds, browser scenarios, ESLint Start rules, or evidence-first debugging.

Plan and execute non-trivial TanStack Start features, refactors, upgrades, or migrations. Use when a task crosses routing, server functions, rendering, data access, build configuration, or deployment boundaries and needs an evidence-first implementation plan with explicit verification.