Tanstack start testing

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

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

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

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.

SKILL.md

1.6 KB, as published. Nobody here has run it

TanStack Start Testing

Select the smallest meaningful check

Read ../../docs/testing-and-debugging.md. Map the changed behavior to its owning boundary and reproduce the failure before editing when possible.

Test pure validators and domain logic.
Test server functions, middleware, or server routes through their public contract.
Test route matching, params, search, loaders, and boundaries.
Run typecheck, configured lint, and production build.
Reproduce browser-visible behavior and inspect console and network output.

Use the project's existing runner and conventions. Ask before installing a test framework or changing configuration.

Cover failure paths

Include malformed input, authentication, authorization, cross-tenant access, dependency failure, redirect, not-found, status/header behavior, hydration mismatch, direct load, and client navigation as relevant.

Diagnose without masking

Trace the first actionable error through route, loader, endpoint, middleware, and dependency. Compare development and production when import protection, tree shaking, SSR, or adapter output is involved. Do not add catch-all fallbacks or suppress warnings to make a test pass.

Report the reproduction, expected result, checks run, observed evidence, and remaining unverified paths.