Skill Claude CodeCodex
Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.
The official TanStack CLI - Project Scaffolding, MCP Server, Agent Skills Installation, etc
TanStack/cli is the official command-line tool for creating and managing TanStack Start and TanStack Router applications. It is for scaffolding full-stack or single-page projects and adding integrations such as authentication, databases, deployment, and monitoring. The catalogue entries provide add-ons and guidance for working with the CLI.
This repository also configures its own agents. See what cli tells them →
Skill Claude CodeCodex
Apply integrations to existing projects with tanstack add, including add-on id resolution, dependency chains, option prompts, and .cta.json project metadata preconditions.
Skill Claude CodeCodex
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 Claude CodeCodex
Scaffold a TanStack app with tanstack create using --framework, --build-tool, --template, --toolchain, --deployment, --add-ons, --blank, and --router-only. Covers flag compatibility, non-interactive defaults, and intent-preserving command construction.
Skill Claude CodeCodex needs its repo
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.
Skill Claude CodeCodex
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.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: