What problem does it solve? TanStack Start modules are isomorphic by default, so code runs in both server and client bundles — causing secret leaks, DB-in-loader bugs, undefined env vars on edge runtimes, and hydration mismatches. This Skill provides the mental model and boundary APIs to place code in the correct environment. ## Core Features & Use Cases - Boundary API Reference: Covers createServerFn, createServerOnlyFn, createClientOnlyFn, createIsomorphicFn, <ClientOnly>, useHydrated(), and server-only/client-only import markers with a decision framework for choosing between them. - Environment Variable Safety: Explains VITE_/PUBLIC_ client exposure versus process.env server reads, and why env must be read per request rather than at module scope. - Copy-Paste Templates: Complete working examples of every boundary pattern, including loaders calling server functions and hydration-safe rendering. - Use Case: You discover an API secret visible in the browser bundle. Use this Skill to move the secret access into a createServerFn handler and remove the public prefix from the variable. ## Quick Start Ask the agent to review your TanStack Start route loaders and move any database or secret access into createServerFn handlers.