What problem does it solve? TanStack Start RSCs behave differently from Next.js App Router patterns, and stale docs, wrong cache ownership, and slot misuse cause subtle bugs. This Skill provides current API guidance, decision rules, and debugging paths for building RSCs correctly in TanStack Start apps. ## Core Features & Use Cases - Primitive selection: Decide between renderServerComponent, createCompositeComponent, and low-level Flight stream APIs based on whether client slots are needed. - Cache and refresh ownership: Choose between Router loader cache, TanStack Query (with structuralSharing: false), or HTTP cache, and wire invalidation to the correct owner. - Debugging and review: Triage setup failures, slot bugs, stale data, serialization errors, and SSR mode issues using dedicated reference docs. - Use Case: When migrating a Next.js App Router page to TanStack Start, use this Skill to translate 'use client' boundaries into Composite Component slots and server actions into explicit POST createServerFn calls. ## Quick Start Ask the AI to implement a TanStack Start route that renders a server component through a loader and explain which cache owner should handle its refresh.