CtrlK
BlogDocsLog inGet started
Tessl Logo

add-addons-existing-app

Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/cli/skills/add-addons-existing-app/SKILL.md
SKILL.md
Quality
Evals
Security

Add Add-ons To Existing App

Use this skill when the project already exists and you need to layer add-ons safely without breaking dependency or metadata assumptions.

Setup

npx @tanstack/cli add clerk drizzle

Core Patterns

Add multiple integrations in one pass

npx @tanstack/cli add tanstack-query drizzle

Resolve candidate ids before applying

npx @tanstack/cli create --list-add-ons --json

Validate optionized add-ons before install

npx @tanstack/cli create --addon-details prisma --json

Common Mistakes

CRITICAL Run tanstack add without .cta.json

Wrong:

npx @tanstack/cli add clerk

Correct:

# Run in a project scaffolded by TanStack CLI (contains .cta.json), then:
npx @tanstack/cli add clerk

Add flows depend on persisted scaffold metadata, so commands can fail or apply incomplete config when .cta.json is missing.

Source: packages/create/src/custom-add-ons/shared.ts:158

HIGH Use invalid add-on id

Wrong:

npx @tanstack/cli add drizle

Correct:

npx @tanstack/cli add drizzle

Unknown ids stop resolution and force manual correction before any add-on work proceeds.

Source: packages/create/src/add-ons.ts:44

HIGH Ignore add-on dependency requirements

Wrong:

npx @tanstack/cli add custom-addon-with-missing-deps

Correct:

npx @tanstack/cli add required-dependency custom-addon-with-missing-deps

Add-ons with dependsOn can fail during finalization if required dependencies are not present.

Source: packages/create/src/add-ons.ts:48

MEDIUM Assume old Windows path bug still present

Wrong:

# Avoid tanstack add on Windows and patch manually

Correct:

npx @tanstack/cli add clerk

Avoiding supported workflows based on historical bug reports causes unnecessary manual drift. Fixed in newer versions, but agents trained on older threads may still avoid this path.

Source: https://github.com/TanStack/cli/issues/329

HIGH Tension: Backwards support vs deterministic automation

This domain's patterns conflict with maintain-custom-addons-dev-watch. Automation that assumes universal add flows tends to fail because legacy compatibility still relies on hidden scaffold metadata.

See also: maintain-custom-addons-dev-watch/SKILL.md § Common Mistakes

Repository
TanStack/cli
Last updated
First committed

Is this your skill?

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.