react-query-and-trpc

react-query-and-trpc is a cursor rule for Cursor from iHildy/jules-task-queue. It costs 0 tokens per session (4,012 once invoked), scanned A, original, MIT.

Project rules for using React Query with tRPC in a Next.js TypeScript application. React Query manages data fetched by a web interface, while tRPC connects that interface to server procedures with shared types.

In plain words
What is it for?
Use it when adding or changing React data queries, tRPC calls, TypeScript types, or related tests.
Why use it?
It gives consistent guidance for organizing data fetching, performance, security, and tests in the project's stated technology stack.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when adding or changing React data queries, tRPC calls, TypeScript types, or related tests.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ihildy/jules-task-queue/react-query-and-trpc
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/iHildy/jules-task-queue

Made for: Cursor.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for react-query-and-trpc

README.md
[![agentmods](https://agentmods.dev/badge/rules/ihildy/jules-task-queue/react-query-and-trpc/github.svg)](https://agentmods.dev/rules/ihildy/jules-task-queue/react-query-and-trpc)
Your own site
<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/react-query-and-trpc"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/react-query-and-trpc/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for react-query-and-trpc

Your own site · 80×15
<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/react-query-and-trpc"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/react-query-and-trpc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 4,012 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.04012
Opus 5.5 $0.00000 $0.01605
Sonnet 5.5 $0.00000 $0.00802
Haiku 4.5 $0.00000 $0.00401

Measured 13d ago against content hash a15053bbe07a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

react-query-and-trpc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/react-query-and-trpc.mdc · 524 lines

How it starts

The opening of the file, as written. The whole thing — 524 lines — stays where its author put it; the contents beside it link to each section on GitHub.

react-query with tRPC Best Practices

This document outlines the best practices for using react-query in React applications, covering various aspects such as code organization, performance considerations, security, and testing.

Project Tech Stack:

ALWAYS USE THE FOLLOWING IN CONJUNCTION WITH EACHOTHER TO HAVE A SAFE CODEBASE WHERE WE CAN MOVE FAST AND BREAK NOTHING

  • Next.js
  • Typescript + ESlint
  • Zod + Prisma + tRPC + React Query
  • Prisma (supabase) + Redis
  • ShadCN + TailwindCSS v4
  • Vitest Unit Tests

1. Code Organization and Structure

Compared to our classic React Query Integration this client is simpler and more TanStack Query-native, providing factories for common TanStack React Query interfaces like QueryKeys, QueryOptions, and MutationOptions. We think it's the future and recommend using this over the classic client, read the announcement post for more information about this change.

Quick example query

import { useQuery } from '@tanstack/react-query';
import { useTRPC } from './trpc';

function Users() {
  const trpc = useTRPC();

  const greetingQuery = useQuery(trpc.greeting.queryOptions({ name: 'Jerry' }));

  // greetingQuery.data === 'Hello Jerry'
}

Usage

The philosophy of this client is to provide thin and type-safe factories which work natively and type-safely with Tanstack React Query. This means just by following the autocompletes the client gives you, you can focus on building just with the knowledge the TanStack React Query docs provide.

export default function Basics() {
  const trpc = useTRPC();
  const queryClient = useQueryClient();

  // Create QueryOptions which can be passed to query hooks
  const myQueryOptions = trpc.path.to.query.queryOptions({ /** inputs */ })
  const myQuery = useQuery(myQueryOptions)
  // or:
  // useSuspenseQuery(myQueryOptions)
  // useInfiniteQuery(myQueryOptions)

  // Create MutationOptions which can be passed to useMutation
  const myMutationOptions = trpc.path.to.mutation.mutationOptions()
  const myMutation = useMutation(myMutationOptions)

  // Create a QueryKey which can be used to manipulated many methods
  // on TanStack's QueryClient in a type-safe manner
  const myQueryKey = trpc.path.to.query.queryKey()

  const invalidateMyQueryKey = () => {
    queryClient.invalidateQueries({ queryKey: myQueryKey })
  }

  return (
    // Your app here
  )
}

Read the full file on GitHub · 524 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 524 lines · 4,012 tokens per session scan A a15053bbe07a

Subscribe to this mod's changes

react-query-and-trpc is a cursor rule published in the GitHub repository iHildy/jules-task-queue (17 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,012 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-02.