How to use
- Copy the installation command and review the source package before installing it in your own agent environment.
- Check the source document for required tools, credentials and supported hosts.
- Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/tanstack/cli --skill choose-ecosystem-integrationsBefore you start
- Installation does not include a model subscription, API allowance or permission to access your files.
- Repository stars and installation counts describe activity, not an independent quality or security test.
Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.
This skill requires familiarity with scaffold and discovery workflows. Read create-app-scaffold and query-docs-library-metadata first.
Choose Ecosystem Integrations
Use this skill at the seam between user requirements and valid CLI integration choices.
Setup
npx @tanstack/cli ecosystem --json
npx @tanstack/cli create --list-add-ons --jsonCore Patterns
Map partner intent to add-on ids explicitly
npx @tanstack/cli ecosystem --category database --json
npx @tanstack/cli create --list-add-ons --jsonInspect option surfaces before final provider choice
npx @tanstack/cli create --addon-details drizzle --json
npx @tanstack/cli create --addon-details prisma --jsonEnforce one choice per exclusive category
npx @tanstack/cli create my-app \
--framework react \
--add-ons clerk,drizzle \
--deployment cloudflare \
-yCommon Mistakes
HIGH Treat ecosystem partner id as add-on id
Wrong:
npx @tanstack/cli add <partner-id-from-ecosystem>Correct:
npx @tanstack/cli ecosystem --json
npx @tanstack/cli create --list-add-ons --json
npx @tanstack/cli add <mapped-addon-id>ecosystem includes partners that are not directly installable add-ons, so direct reuse of partner ids can fail late in add/apply flows.
Source: tanstack ecosystem --json output + tanstack create --list-add-ons --json output
HIGH Skip addon-details before choosing provider
Wrong:
npx @tanstack/cli create my-app --add-ons prisma -yCorrect:
npx @tanstack/cli create --addon-details prisma --json
npx @tanstack/cli create my-app --add-ons prisma -yOptionized providers can default silently, producing the wrong data-layer stack for the requested integration.
Source: tanstack create --addon-details prisma --json
HIGH Select multiple exclusive integrations together
Wrong:
npx @tanstack/cli create my-app --add-ons clerk,workos -yCorrect:
npx @tanstack/cli create my-app --add-ons clerk -yExclusive categories permit only one active choice, so multi-select commands can drop or replace intended providers.
Source: packages/create/src/frameworks///info.json
CRITICAL Assume router-only supports deployment integration
Wrong:
npx @tanstack/cli create my-app --router-only --deployment cloudflare -yCorrect:
npx @tanstack/cli create my-app --router-only -yRouter-only mode ignores deployment integration, so the command succeeds without applying the intended ecosystem target.
Source: packages/cli/src/command-line.ts:349
HIGH Tension: Compatibility mode vs explicit intent
This domain's patterns conflict with create-app-scaffold. Integration planning tends to over-assume command intent is preserved, but compatibility mode silently strips integration flags.
See also: create-app-scaffold/SKILL.md § Common Mistakes
HIGH Tension: Single-command convenience vs integration precision
This domain's patterns conflict with query-docs-library-metadata. Integration choices tend to drift when discovery metadata is skipped in favor of one-shot scaffold commands.
See also: query-docs-library-metadata/SKILL.md § Common Mistakes
