Tanstack start deployment

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

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-deployment

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

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.

SKILL.md

1.5 KB, as published. Nobody here has run it

TanStack Start Deployment

Identify the runtime

Read ../../docs/deployment-and-observability.md and inspect the installed adapter, build tool, package scripts, runtime configuration, and hosting files. Follow current provider documentation for that exact combination.

Prepare safely

Validate required environment-variable names and non-empty presence without printing secrets.
Build production output.
Run the produced server artifact locally when supported.
Verify assets, direct routes, server functions, server routes, redirects, streaming, and cache headers.
Confirm health and observability behavior.

Do not deploy, create remote resources, modify secrets, or install an adapter without explicit approval.

Review cache and logs

Prevent public caching of personalized responses. Set Vary and validation headers intentionally. Ensure logs contain request outcomes and trace IDs without credentials, tokens, cookies, secrets, or sensitive bodies.

Report readiness

Separate local build success from deployment readiness. List the runtime path verified, required external configuration, exact commands run, and any provider behavior that remains untested.