tanstack-cli · oakoss — Claude Code skill: what it does, how to install
tanstack-cli configures TanStack library build tooling, Vite dual ESM/CJS outputs, and conventional-commit publishing.
MIT 115 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill tanstack-cli -a claude-codeWhat tanstack-cli does
This skill guides agents in configuring JavaScript and TypeScript libraries according to TanStack project conventions. It provides patterns for @tanstack/vite-config, covering dual ESM and CJS compilation alongside TypeScript declaration emission. It also provides workflows for @tanstack/publish-config to automate releases across branch channels like main, beta, and alpha.
Designed strictly for package maintainers, it does not support full-stack application builds or alternative bundlers. It requires pnpm v8+, Node.js v18.17+, Git CLI, and Vite as a peer dependency. Packaging issues are caught using publint --strict immediately following vite build.
What it helps with
- configure dual ESM/CJS library builds with Vite
- set up TypeScript declaration bundling and exclusions
- automate versioning and publishing from conventional commits
- validate package export mappings with publint
Example prompts for the agent
- Configure a library build using @tanstack/vite-config with entry ./src/index.ts
- Validate package.json exports and mergeConfig setup for Vite
- Set up branchConfigs for automated publishing using @tanstack/publish-config
How to install tanstack-cli
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-cli -a claude-code2Manually: put the files in place
~/.claude/skills/tanstack-cli/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tanstack-cli/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-cli -a codex2Manually: put the files in place
.agents/skills/tanstack-cli/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-cli -a cursor2Manually: put the files in place
.cursor/skills/tanstack-cli/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/tanstack-cli2Manually: put the files in place
.github/skills/tanstack-cli/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-cli -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/tanstack-cliManually: put the files in place
.devin/skills/tanstack-cli/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-cli -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tanstack-cli
How to install tanstack-cli in Claude Code?
Run npx skills add oakoss/agent-skills --skill tanstack-cli -a claude-code to install it into ~/.claude/skills/tanstack-cli/SKILL.md.
What does tanstack-cli do?
It equips the agent with guidelines to build libraries via Vite and manage npm releases using TanStack Config conventions.
Can I use this skill on npm or yarn projects?
No, the tooling explicitly requires pnpm v8 or newer; npm and yarn are unsupported.
Source text
SKILL.md · MIT
---
name: tanstack-cli
description: >
TanStack Config for shared build tooling, Vite plugins, and package configuration across TanStack projects.
Use when configuring TanStack library builds or contributing to TanStack packages.
Use for tanstack-config, tanstack-cli, vite-plugin, package-config, library-build.
license: MIT
metadata:
author: oakoss
version: '1.0'
source: 'https://tanstack.com/config/latest'
user-invocable: false
---
# TanStack Config
## Overview
TanStack Config provides opinionated tooling to build, version, and publish JavaScript/TypeScript packages with minimal configuration and consistent results. It uses Vite for library builds with automatic dual ESM/CJS output and type generation, plus automated publishing with conventional-commit-based versioning.
**When to use:** Building TanStack libraries or packages that follow TanStack conventions, contributing to TanStack open-source projects, setting up dual ESM/CJS library builds with Vite, automating package publishing with conventional commits.
**When NOT to use:** Application builds (use framework-specific tooling), non-library projects, projects not using pnpm, projects that need non-Vite build pipelines.
## Quick Reference
| Pattern | API / Package | Key Points |
| ------------------ | --------------------------------------------------- | ------------------------------------------------------- |
| Vite build config | `tanstackViteConfig()` from `@tanstack/vite-config` | Merge with `defineConfig` via `mergeConfig` |
| Entry point | `entry: './src/index.ts'` | Single file or array of entry files |
| Source directory | `srcDir: './src'` | Used for declaration file generation |
| CJS output | `cjs: true` (default) | Generates `.cjs` and `.d.cts` alongside ESM |
| External deps | `externalDeps: [/^@internal\//]` | Auto-detected from `package.json`, extend with patterns |
| Bundled deps | `bundledDeps: ['tiny-invariant']` | Bundle instead of externalize |
| Exclude from types | `exclude: ['./src/**/*.test.ts']` | Patterns to skip during type generation |
| Custom tsconfig | `tsconfigPath: './tsconfig.build.json'` | Override default tsconfig for builds |
| Declaration hook | `beforeWriteDeclarationFile(path, content)` | Transform `.d.ts` content before write |
| Publish automation | `publish()` from `@tanstack/publish-config` | Conventional commits drive versioning |
| Branch configs | `branchConfigs: { main, beta, alpha }` | Control prerelease and stable channels |
| Package list | `packages: [{ name, packageDir }]` | Monorepo package definitions |
| Build script | `vite build && publint --strict` | Standard build with strict linting |
## Common Mistakes
| Mistake | Correct Pattern |
| ------------------------------------------------ | -------------------------------------------------------------------------- |
| Missing `"type": "module"` in `package.json` | Set `"type": "module"` for ESM-first builds |
| Using `defineConfig` alone without `mergeConfig` | Use `mergeConfig(defineConfig({...}), tanstackViteConfig({...}))` |
| Forgetting `entry` or `srcDir` options | Both are required for `tanstackViteConfig` to work |
| Missing `exports` field in `package.json` | Define `import` and `require` conditions with types |
| Not awaiting `publish()` promise | Handle with `.then()` and `.catch()` for error reporting |
| Using npm or yarn instead of pnpm | pnpm is the only supported package manager |
| Omitting `publint --strict` from build script | Add `publint --strict` after `vite build` to catch packaging issues |
| Setting `tag` without `v` prefix | Manual version tags must start with `v` (e.g., `v1.0.0`) |
| Wrong commit type for release level | `fix`/`refactor`/`perf` = patch, `feat` = minor, `BREAKING CHANGE` = major |
## Requirements
- Node.js v18.17+
- pnpm v8+
- Git CLI
- GitHub CLI (pre-installed on GitHub Actions)
- Vite (peer dependency for build config)
- publint (recommended for build validation)
## Delegation
- **Build configuration review**: Use `Task` agent to verify Vite config and `package.json` exports
- **Publishing workflow setup**: Use `Explore` agent to check CI/CD integration patterns
- **Package validation**: Run `publint --strict` after builds to catch packaging issues
## References
- [Configuration and Vite plugin setup](references/configuration.md)
- [Publishing and version management](references/publishing.md)
© oakoss · MIT · oakoss/agent-skills
Similar skills
All skills for Frontend and UI →tanstack-cli by other authors comes first.