Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

tanstack-start-rendering

Étoiles0

Forks0

Mis à jour10 juillet 2026 à 00:14

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.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

MakFly

MakFly/superpowers-tanstack-start

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

2 fichiers

SKILL.md

readonly

Plus depuis ce dépôt

même dépôt

tanstack-start-auth

MakFly/superpowers-tanstack-start

Design, implement, audit, or debug authentication and authorization in TanStack Start. Use for sessions, cookies, login, logout, OAuth state and PKCE, password reset, CSRF, rate limiting, protected routes, RBAC, tenant isolation, secret handling, or auth tests.

2026-07-100

tanstack-start-deployment

MakFly/superpowers-tanstack-start

Prepare, review, or debug TanStack Start production builds and deployments. Use for Vite or Rsbuild output, Cloudflare Workers, Netlify, Railway, Nitro, Node, Docker, Bun, Vercel, Appwrite, environment wiring, assets, CDN caching, early hints, observability, health checks, or production-only failures.

2026-07-100

tanstack-start-middleware

MakFly/superpowers-tanstack-start

Design, implement, review, or debug TanStack Start middleware and server routes. Use for request middleware, server-function middleware, typed context, global middleware, CSRF, request or response transforms, API endpoints, webhooks, health routes, HTTP methods, headers, status codes, or route conflicts.

2026-07-100

tanstack-start-routing

MakFly/superpowers-tanstack-start

Design, implement, review, or debug TanStack Start and TanStack Router routes. Use for file-route structure, root routes, layouts, params, search validation, loaders, loader dependencies, navigation, preloading, pending states, errors, not-found behavior, or route-tree generation.

2026-07-100

tanstack-start-server-functions

MakFly/superpowers-tanstack-start

Implement, secure, review, or debug TanStack Start server functions. Use for createServerFn handlers, input validation, request context, redirects, not-found results, raw responses, progressive enhancement, streaming, static functions, cancellation, serialization, or server-only data access.

2026-07-100

tanstack-start-testing

MakFly/superpowers-tanstack-start

Create verification plans, write tests, review coverage, or diagnose TanStack Start failures. Use for validators, server functions, middleware, server routes, route loaders, rendering, hydration, production builds, browser scenarios, ESLint Start rules, or evidence-first debugging.

2026-07-100

name	tanstack-start-rendering
description	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.

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.