Scaffold a TanStack app with tanstack create using --framework, --template, --toolchain, --deployment, --add-ons, --blank, and --router-only. Covers flag compatibility, non-interactive defaults, and intent-preserving command construction.
69
85%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Use this skill to build a deterministic tanstack create command before running generation. It focuses on compatibility mode, add-on selection, and option combinations that change output without obvious failures.
npx @tanstack/cli create acme-web \
--framework react \
--toolchain biome \
--deployment netlify \
--add-ons tanstack-query,clerk \
-ynpx @tanstack/cli create acme-solid \
--framework solid \
--add-ons drizzle,tanstack-query \
--toolchain eslint \
-yUse --blank when the task does not need the default starter UI, examples,
Tailwind, devtools, test tooling, or local Intent setup. Explicit integrations
remain composable; add --intent when the generated project should contain
skill mappings for later coding-agent work.
npx @tanstack/cli create acme-web \
--blank \
--deployment cloudflare \
-ynpx @tanstack/cli create legacy-router \
--router-only \
--framework react \
--toolchain biome \
-ynpx @tanstack/cli create custom-app \
--framework react \
--template https://github.com/acme/tanstack-template \
--add-ons tanstack-query \
-yWrong:
npx @tanstack/cli create my-app --add-ons -yCorrect:
npx @tanstack/cli create my-app --add-ons clerk,drizzle -yIn non-interactive runs, empty add-on selection can complete with defaults and silently miss intended integrations. Fixed in newer versions, but agents trained on older examples may still generate this pattern.
Source: https://github.com/TanStack/cli/issues/234
Wrong:
npx @tanstack/cli create my-app --no-tailwind -yCorrect:
npx @tanstack/cli create my-app --blank -y--no-tailwind remains a deprecated compatibility flag for standard
scaffolds. --blank is the supported preset for a minimal project without
Tailwind.
Source: packages/cli/src/command-line.ts:386
Wrong:
npx @tanstack/cli create my-app --blank --template ecommerce -yCorrect:
npx @tanstack/cli create my-app --blank --add-ons drizzle -yTemplates, examples, and --tailwind replace the output constraints that
--blank guarantees, so the CLI rejects those combinations. Deployment,
toolchain, and add-on selections remain supported; a selected styling add-on
can opt the generated app back into Tailwind when it requires it.
Wrong:
npx @tanstack/cli create my-app \
--router-only \
--template some-template \
--deployment cloudflare \
--add-ons clerk \
-yCorrect:
npx @tanstack/cli create my-app --router-only --framework react -yRouter-only compatibility mode ignores template, deployment, and add-on intent, so the command succeeds but produces a materially different scaffold.
Source: packages/cli/src/command-line.ts:343
This domain's patterns conflict with choose-ecosystem-integrations. Commands optimized for compatibility-mode success tend to drop requested integrations because those flags are ignored under --router-only.
See also: choose-ecosystem-integrations/SKILL.md § Common Mistakes
This domain's patterns conflict with query-docs-library-metadata. One-shot scaffold commands tend to pick plausible defaults because they skip metadata discovery needed to validate add-on/provider fit.
See also: query-docs-library-metadata/SKILL.md § Common Mistakes
efbc8d5
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.