CLI
Compose a TanStack app, then keep every choice inspectable.
TanStack CLI turns the current library catalog, docs, templates, and add-on metadata into project files developers and agents can both understand.
application
add-ons
deployment
generated plan
7 files+package.json
+src/routes/__root.tsx
+src/styles.css
+vite.config.ts
+src/db/index.ts
+drizzle.config.ts
+.cta.json
.cta.json
app shape, add-ons, and deployment
Add-on contract
An integration is more than a dependency.
Add-ons can declare files, packages, environment variables, options, ordering hooks, dependencies, and conflicts. The CLI has enough structure to compose them deliberately instead of pasting setup snippets in sequence.
database / drizzle
A composable unit with enough metadata to participate in the whole project plan.
- files
- Create and patch owned project files
- dependencies
- Install runtime and development packages
- environment
- Declare required keys and example values
- options
- Ask only the questions this integration needs
- hooks
- Run composition work at explicit phases
- relationships
- Express dependencies and conflicts
JSON
- 8 current results
- router · framework/react
- source URLs included
Machine-readable context
The same catalog works for humans and agents.
Search documentation or inspect TanStack libraries, add-ons, and ecosystem entries from the terminal. JSON output preserves names, versions, categories, and source links without asking an agent to scrape a website.
Open composition
Start from TanStack’s catalog—or publish your own.
A template owns the project baseline. Add-ons layer focused capabilities on top. Both stay inspectable, so teams can host private building blocks or contribute integrations without turning project generation into a black box.
Template
Owns the starting application, package manager, file layout, and default conventions.
Add-on
Adds one capability through declared files, packages, options, and composition rules.
preview files → review plan → generate source