# Choose Ecosystem Integrations

Map tanstack ecosystem partner metadata to installable add-on ids using tanstack...

- Repository: https://github.com/TanStack/cli (1304 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add TanStack/cli --skill choose-ecosystem-integrations -g -a claude-code -y`
Codex: `npx skills add TanStack/cli --skill choose-ecosystem-integrations -g -a codex -y`
Cursor: `npx skills add TanStack/cli --skill choose-ecosystem-integrations -g -a cursor -y`
Gemini CLI: `npx skills add TanStack/cli --skill choose-ecosystem-integrations -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

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

```bash
npx @tanstack/cli ecosystem --json
npx @tanstack/cli create --list-add-ons --json
```

## Core Patterns

### Map partner intent to add-on ids explicitly

```bash
npx @tanstack/cli ecosystem --category database --json
npx @tanstack/cli create --list-add-ons --json
```

### Inspect option surfaces before final provider choice

```bash
npx @tanstack/cli create --addon-details drizzle --json
npx @tanstack/cli create --addon-details prisma --json
```

### Enforce one choice per exclusive category

```bash
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:
```bash
npx @tanstack/cli add <partner-id-from-ecosystem>
```

Correct:
```bash
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:
```bash
npx @tanstack/cli create my-app --add-ons prisma -y
```

Correct:
```bash
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:
```bash
npx @tanstack/cli create my-app --add-ons clerk,workos -y
```

The rest: https://github.com/TanStack/cli/blob/HEAD/packages/cli/skills/choose-ecosystem-integrations/SKILL.md