Tanstack start routing

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

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

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

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.

SKILL.md

1.7 KB, as published. Nobody here has run it

TanStack Start Routing

Inspect the route contract

Read ../../docs/routing-and-data.md. Inspect the source route files, generated route tree, router context, and the exact URL being changed. Confirm whether the task affects direct requests, client navigation, or both.

Implement typed URL state

Express hierarchy with the existing file-route conventions.
Validate path and search inputs at the route boundary.
Declare every loader input in loader dependencies.
Keep secrets and direct database access out of isomorphic loaders.
Use server functions for protected server work.
Use typed links, navigation, redirects, and route APIs.
Provide deliberate pending, error, and not-found behavior.

Treat beforeLoad as navigation and context control. Enforce protected-data access again in the server function or server route.

Control performance

Parallelize independent loader work. Use preloading only when its network and compute cost is justified. Verify automatic or explicit code splitting in production output instead of assuming it occurred.

Verify

Run route-tree generation and typecheck. Test valid and invalid params/search, direct load, client navigation, loader invalidation, pending state, error boundary, and not-found state. Use browser verification for navigation-visible changes.

Return the route contract, data flow, verification results, and any unresolved URL or cache behavior.