start▌

Best practices for full-stack React development with TanStack Start, covering server functions, middleware, SSR, and authentication. \n \n Organizes 31 rules across 10 categories (server functions, security, middleware, authentication, SSR, error handling, and more) with priority levels to guide implementation order \n Covers critical patterns for server-side logic, input validation, secure session management, and client-server boundary handling \n Includes middleware composition, selective SSR

Guides cold start strategy for AI/SaaS products: getting first users and traction when you have zero. The cold start problem is overcoming the chicken-and-egg barrier; most startups fail due to poor distribution, not product quality. For indie hacker context (first 100 users, Build in Public, Pieter Levels tactics), see indie-hacker-strategy.

TanStack Start is a full-stack React framework built on TanStack Router, powered by Vite and Nitro (via Vinxi). It provides server-side rendering, streaming, server functions (RPC), middleware, API routes, and deploys to any platform via Nitro presets.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Full-stack TanStack Start app generator for Cloudflare Workers with SSR, file-based routing, and integrated auth. \n \n Generates complete project structure from scratch (no templates): React 19, Tailwind v4, shadcn/ui frontend; TanStack Start server functions; D1 + Drizzle backend; better-auth with Google OAuth and email/password \n Handles database schema creation, migrations, and per-request Drizzle client setup with D1-specific patterns (text PKs, integer timestamps, foreign key constraints)

Automate Marshroom cart issue setup with branch creation, status tracking, and context injection. \n \n Reads the Marshroom state file, filters cart issues matching the current repository, and creates a feature or hotfix branch with standardized naming ( Feature/#N or HotFix/#N ) \n Mandatory state.json update: sets issue status to running via marsh start command or atomic jq write, with verification to ensure the update succeeds \n Injects issue body as context so the agent understands the full