Tanstack start rendering

Skill MakFly/superpowers-tanstack-start/skills/tanstack-start-rendering

Open-source Claude Code plugin and Agent Skills for TanStack Start: type-safe routing, server functions, SSR, middleware, authentication, testing, and deployment.

Install

npx -y skills add MakFly/superpowers-tanstack-start --skill tanstack-start-rendering

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

TanStack Start Rendering

Choose from requirements

Read ../../docs/rendering.md. Record SEO, first-render, personalization, interactivity, cache, runtime, and deployment requirements before selecting a mode.

Use SSR for request-time HTML.
Use static prerendering for bounded public routes known at build time.
Use ISR only with explicit safe cache semantics.
Use SPA mode when a client-rendered shell is acceptable.
Use selective SSR when route branches need different behavior.
Use deferred hydration when HTML should render now but interaction can activate later.
Use RSC only with the project's supported build integration and explicit serialization constraints.

Preserve correctness

Keep the first client render consistent with server HTML. Do not suppress hydration warnings until the mismatch is understood. Never publicly cache user-specific output. Ensure SPA rewrites preserve server-function and server-route paths.

Verify both paths

Test direct requests and client navigation. Inspect server HTML, hydration console output, streamed responses, cache headers, CDN behavior, JavaScript-disabled flows, deferred interactions, and production chunks as applicable.

Report the selected mode, rejected alternatives, cache boundary, and runtime evidence.