Run /tanstack-intent first for installed Router/Query API syntax. This skill owns local URL/data policy. See REFERENCE.md for shapes and SETUP.md for install.

Router + Query

Router loaders start server fetches after navigation intent; Query owns cache/refetch/invalidation/GC; components observe with useQuery/useSuspenseQuery.

Route-known inputs use one pipeline: validateSearch -> loaderDeps -> one queryOptions builder -> loader and observer. Return only query-driving fields. Components use useLoaderDeps, not parallel search reads. Share route-context options only when installed Intent guidance supports it.

Critical data: await ensureQueryData, observe with useSuspenseQuery.
Deferred route data: start in loader, observe with useQuery plus loading/empty/error.
Interaction-only data may start in components.
Query loaders use defaultPreloadStaleTime: 0 and createRootRouteWithContext.

tanstack-router

Router + Query

Navigation lifetimes