tanstack-devtools · oakoss — Claude Code skill: what it does, how to install
tanstack-devtools guides AI coding agents in configuring Query cache, Router, and Form debugging panels across React applications.
MIT 125 installs ★ 29 updated 2026-08-17
npx skills add oakoss/agent-skills --skill tanstack-devtools -a claude-codeWhat tanstack-devtools does
This skill guides coding assistants through setting up debugging interfaces for TanStack projects. It covers standalone options like ReactQueryDevtools and TanStackRouterDevtools, as well as unified panel setups via TanStackDevtools plugins. Included reference tables detail trigger placement, panel slide direction, hotkeys, and Vite plugin integration.
The guide highlights critical integration snags. It stops agents from mounting components outside QueryClientProvider, passing redundant router props within active providers, or mixing standalone panels with unified dashboards.
Without framework adapters or outside React environments, these patterns will not function. Devtools are tree-shaken in production builds, so inspecting live production state requires an explicit opt-in via ReactQueryDevtoolsInProd.
What it helps with
- embed Query cache inspector inside application layouts
- configure unified TanStackDevtools panels with keyboard shortcuts
- integrate Vite devtools plugin for bundle stripping in production
- set up lazy loading for developer inspection tools
Example prompts for the agent
- Set up ReactQueryDevtools inside our main QueryClient provider
- Configure unified TanStackDevtools in Vite with the router plugin
- Check our router root component to fix duplicate devtools panels
How to install tanstack-devtools
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-devtools -a claude-code2Manually: put the files in place
~/.claude/skills/tanstack-devtools/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tanstack-devtools/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-devtools -a codex2Manually: put the files in place
.agents/skills/tanstack-devtools/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-devtools -a cursor2Manually: put the files in place
.cursor/skills/tanstack-devtools/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install oakoss/agent-skills skills/tanstack-devtools2Manually: put the files in place
.github/skills/tanstack-devtools/SKILL.md1Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-devtools -a gemini-cli2Platform CLI
gemini skills install https://github.com/oakoss/agent-skills --path skills/tanstack-devtoolsManually: put the files in place
.devin/skills/tanstack-devtools/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add oakoss/agent-skills --skill tanstack-devtools -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-devtools
How to install tanstack-devtools in Claude Code?
Run npx skills add oakoss/agent-skills --skill tanstack-devtools -a claude-code in your terminal.
What does tanstack-devtools do?
It gives your agent accurate configuration rules and common mistake checklists for TanStack Query, Router, and Form inspection panels.
Can I run standalone and unified devtools together?
No, the skill explicitly advises choosing one strategy because rendering both creates duplicated panels on your screen.
Source text
SKILL.md · MIT
---
name: tanstack-devtools
description: 'TanStack DevTools for debugging Query, Router, and Form state in React apps. Use when setting up devtools, debugging cache state, or inspecting route trees. Use for devtools, react-query-devtools, router-devtools, form-devtools, debug, inspect, cache-viewer.'
license: MIT
metadata:
author: oakoss
version: '1.1'
source: 'https://tanstack.com/devtools/latest/docs'
user-invocable: false
---
# TanStack DevTools
## Overview
TanStack DevTools provides debugging panels for inspecting Query cache state, Router route trees, and Form field state in React applications. There are two approaches: **standalone devtools** per library (`ReactQueryDevtools`, `TanStackRouterDevtools`) and the **unified TanStack Devtools** panel that combines all libraries into a single interface with plugin architecture.
**When to use:** Setting up devtools for TanStack libraries, debugging query cache behavior, inspecting route matching, monitoring form field state, or combining multiple TanStack devtools into one panel.
**When NOT to use:** Production debugging (devtools are tree-shaken in production by default), non-React frameworks without adapter support, or custom state management unrelated to TанStack libraries.
## Quick Reference
| Pattern | API | Key Points |
| -------------------------- | ----------------------------------------- | --------------------------------------------------- |
| Query devtools (floating) | `<ReactQueryDevtools />` | Auto-connects to nearest QueryClient |
| Query devtools (embedded) | `<ReactQueryDevtoolsPanel />` | Embed in custom layout |
| Router devtools (floating) | `<TanStackRouterDevtools />` | Place in root route component |
| Router devtools (embedded) | `<TanStackRouterDevtoolsPanel />` | Requires `router` prop outside provider |
| Form devtools | `<ReactFormDevtoolsPanel />` | Plugin for unified devtools |
| Unified devtools | `<TanStackDevtools plugins={[...]} />` | Single panel for all TanStack libraries |
| Vite plugin | `devtools()` in vite config | Source injection, enhanced logs, production removal |
| Production devtools | `ReactQueryDevtoolsInProd` | Opt-in for production environments |
| Lazy loading | `React.lazy(() => import(...))` | Reduce bundle size in development |
| Open hotkey | `config={{ openHotkey: ['Shift', 'D'] }}` | Keyboard shortcut for unified panel |
## Unified Devtools Config
| Option | Type | Purpose |
| ---------------- | ------------------------------------------------------------------------------------------------- | -------------------------------- |
| `position` | `'top-left' \| 'top-right' \| 'bottom-left' \| 'bottom-right' \| 'middle-left' \| 'middle-right'` | Trigger button location |
| `panelLocation` | `'top' \| 'bottom'` | Panel slide direction |
| `theme` | `'dark' \| 'light'` | Panel color scheme |
| `defaultOpen` | `boolean` | Open panel on load |
| `hideUntilHover` | `boolean` | Hide trigger until hover |
| `openHotkey` | `KeyboardKey[]` | Toggle panel shortcut |
| `inspectHotkey` | `KeyboardKey[]` | Source inspector shortcut |
| `requireUrlFlag` | `boolean` | Only activate with URL parameter |
## Common Mistakes
| Mistake | Correct Pattern |
| ------------------------------------------------------- | ---------------------------------------------------------------------------- |
| Importing devtools in production bundle | Standalone devtools auto-tree-shake; use `React.lazy` for code-splitting |
| Passing `router` prop when inside RouterProvider | Omit `router` prop; devtools auto-detect context |
| Using `ReactQueryDevtools` position for panel placement | `buttonPosition` controls logo position; `position` controls panel edge |
| Mixing standalone and unified devtools | Choose one approach; both rendering causes duplicate panels |
| Rendering devtools outside QueryClientProvider | Place `ReactQueryDevtools` inside provider or pass `client` prop |
| Using `TanStackRouterDevtools` outside route tree | Place in root route component or pass `router` prop explicitly |
| Forgetting Vite plugin for unified devtools | Add `devtools()` from `@tanstack/devtools-vite` to vite config |
| Using unified devtools without framework adapter | Install both `@tanstack/react-devtools` and library-specific plugin packages |
## Delegation
- **Devtools setup review**: Use `Task` agent to verify correct placement and configuration
- **Bundle size analysis**: Use `Explore` agent to check devtools are tree-shaken in production
- **Code review**: Delegate to `code-reviewer` agent
> If the `tanstack-query` skill is available, delegate query-specific debugging patterns to it.
> Otherwise, recommend: `npx skills add oakoss/agent-skills --skill tanstack-query`
>
> If the `tanstack-router` skill is available, delegate route debugging patterns to it.
> Otherwise, recommend: `npx skills add oakoss/agent-skills --skill tanstack-router`
>
> If the `tanstack-form` skill is available, delegate form state management and validation patterns to it.
## References
- [Query devtools setup, modes, and options](references/query-devtools.md)
- [Router devtools setup, route inspection, and options](references/router-devtools.md)
- [Form devtools and unified devtools patterns](references/form-devtools.md)
© oakoss · MIT · oakoss/agent-skills
Similar skills
All skills for Frontend and UI →tanstack-devtools by other authors comes first.