agentleFS
wordbrickswordbricks/onequery/.agents/skills/tanstack-query-best-practices/SKILL.md

tanstack-query-best-practices

Skill17 starsChanged 6 months agoApache-2.0View on GitHub

TanStack Query (React Query) best practices for data fetching, caching, mutations, and server state management. Activate when building data-driven React applications with server state.

7 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use better-auth-best-practices, remotion-best-practices and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • anasahmed07Skill

    better-auth-best-practices

    Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

    Also in 3 projects that use this

  • VercelSkill

    remotion-best-practices

    Best practices for Remotion - Video creation in React

    Also in 3 projects that use this

  • StrayDragonSkill

    ui-ux-pro-max

    UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.

    Also in 3 projects that use this

The file

Files
SKILL.md

TanStack Query Best Practices

Comprehensive guidelines for implementing TanStack Query (React Query) patterns in React applications. These rules optimize data fetching, caching, mutations, and server state synchronization.

When to Apply

  • Creating new data fetching logic
  • Setting up query configurations
  • Implementing mutations and optimistic updates
  • Configuring caching strategies
  • Integrating with SSR/SSG
  • Refactoring existing data fetching code

Rule Categories by Priority

PriorityCategoryRulesImpact
CRITICALQuery Keys5 rulesPrevents cache bugs and data inconsistencies
CRITICALCaching5 rulesOptimizes performance and data freshness
HIGHMutations6 rulesEnsures data integrity and UI consistency
HIGHError Handling3 rulesPrevents poor user experiences
MEDIUMPrefetching4 rulesImproves perceived performance
MEDIUMParallel Queries2 rulesEnables dynamic parallel fetching
MEDIUMInfinite Queries3 rulesPrevents pagination bugs
MEDIUMSSR Integration4 rulesEnables proper hydration
LOWPerformance4 rulesReduces unnecessary re-renders
LOWOffline Support2 rulesEnables offline-first patterns

Quick Reference

Query Keys (Prefix: qk-)

  • qk-array-structure — Always use arrays for query keys
  • qk-include-dependencies — Include all variables the query depends on
  • qk-hierarchical-organization — Organize keys hierarchically (entity → id → filters)
  • qk-factory-pattern — Use query key factories for complex applications
  • qk-serializable — Ensure all key parts are JSON-serializable

Caching (Prefix: cache-)

  • cache-stale-time — Set appropriate staleTime based on data volatility
  • cache-gc-time — Configure gcTime for inactive query retention
  • cache-defaults — Set sensible defaults at QueryClient level
  • cache-invalidation — Use targeted invalidation over broad patterns
  • cache-placeholder-vs-initial — Understand placeholder vs initial data differences

Mutations (Prefix: mut-)

  • mut-invalidate-queries — Always invalidate related queries after mutations
  • mut-optimistic-updates — Implement optimistic updates for responsive UI
  • mut-rollback-context — Provide rollback context from onMutate
  • mut-error-handling — Handle mutation errors gracefully
  • mut-loading-states — Use isPending for mutation loading states
  • mut-mutation-state — Use useMutationState for cross-component tracking

Error Handling (Prefix: err-)

  • err-error-boundaries — Use error boundaries with useQueryErrorResetBoundary
  • err-retry-config — Configure retry logic appropriately
  • err-fallback-data — Provide fallback data when appropriate

Prefetching (Prefix: pf-)

  • pf-intent-prefetch — Prefetch on user intent (hover, focus)
  • pf-route-prefetch — Prefetch data during route transitions
  • pf-stale-time-config — Set staleTime when prefetching
  • pf-ensure-query-data — Use ensureQueryData for conditional prefetching

Infinite Queries (Prefix: inf-)

  • inf-page-params — Always provide getNextPageParam
  • inf-loading-guards — Check isFetchingNextPage before fetching more
  • inf-max-pages — Consider maxPages for large datasets

SSR Integration (Prefix: ssr-)

  • ssr-dehydration — Use dehydrate/hydrate pattern for SSR
  • ssr-client-per-request — Create QueryClient per request
  • ssr-stale-time-server — Set higher staleTime on server
  • ssr-hydration-boundary — Wrap with HydrationBoundary

Parallel Queries (Prefix: parallel-)

  • parallel-use-queries — Use useQueries for dynamic parallel queries
  • query-cancellation — Implement query cancellation properly

Performance (Prefix: perf-)

  • perf-select-transform — Use select to transform/filter data
  • perf-structural-sharing — Leverage structural sharing
  • perf-notify-change-props — Limit re-renders with notifyOnChangeProps
  • perf-placeholder-data — Use placeholderData for instant UI

Offline Support (Prefix: offline-)

  • network-mode — Configure network mode for offline support
  • persist-queries — Configure query persistence for offline support

How to Use

Each rule file in the rules/ directory contains:

  1. Explanation — Why this pattern matters
  2. Bad Example — Anti-pattern to avoid
  3. Good Example — Recommended implementation
  4. Context — When to apply or skip this rule

Full Reference

See individual rule files in rules/ directory for detailed guidance and code examples.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.