tanstack/choose-ecosystem-integrations
packages/cli/skills/choose-ecosystem-integrations/SKILL.md
Map tanstack ecosystem partner metadata to installable add-on ids using tanstack ecosystem --json, tanstack create --list-add-ons --json, and tanstack create --addon-details --json. Covers exclusive categories, provider options, and router-only compatibility constraints.
$ install --global
skillsauthnpx skillsauth add tanstack/cli choose-ecosystem-integrationsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 24, 2026, 8:45 PM1.8s1 file scanned
SKILL.md
- name:
- choose-ecosystem-integrations
- description:
- >
- type:
- composition
- library:
- tanstack-cli
- library_version:
- 0.62.1
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 --json
Core Patterns
Map partner intent to add-on ids explicitly
npx @tanstack/cli ecosystem --category database --json
npx @tanstack/cli create --list-add-ons --json
Inspect option surfaces before final provider choice
npx @tanstack/cli create --addon-details drizzle --json
npx @tanstack/cli create --addon-details prisma --json
Enforce one choice per exclusive category
npx @tanstack/cli create my-app \
--framework react \
--add-ons clerk,drizzle \
--deployment cloudflare \
-y
Common 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 -y
Correct:
npx @tanstack/cli create --addon-details prisma --json
npx @tanstack/cli create my-app --add-ons prisma -y
Optionized 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 -y
Correct:
npx @tanstack/cli create my-app --add-ons clerk -y
Exclusive 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 -y
Correct:
npx @tanstack/cli create my-app --router-only -y
Router-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
References
- Authentication providers
- Data layer providers
- Deployment targets
Related Skills
tanstack/query-docs-library-metadata
development
VerifiedTrustedCommunity
Retrieve machine-readable context with tanstack libraries, tanstack doc, tanstack search-docs, tanstack create --list-add-ons --json, and --addon-details for agent-safe discovery and preflight validation.
1,230SKILL.mdUpdated Apr 15, 2026
tanstack/maintain-custom-addons-dev-watch
development
VerifiedTrustedCommunity
Build and iterate custom add-ons/templates with tanstack add-on init, add-on compile, add-on dev, and tanstack create --dev-watch, including sync loop preconditions, watch-path validation, and project metadata constraints.
1,230SKILL.mdUpdated Apr 15, 2026
tanstack/create-app-scaffold
tools
VerifiedTrustedCommunity
Scaffold a TanStack app with tanstack create using --framework, --template, --toolchain, --deployment, --add-ons, and --router-only. Covers flag compatibility, non-interactive defaults, and intent-preserving command construction.
1,230SKILL.mdUpdated Apr 15, 2026
tanstack/add-addons-existing-app
data-ai
VerifiedTrustedCommunity
Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.
1,230SKILL.mdUpdated Apr 15, 2026