TanStack Query Agent Rules

Asynchronous state management and data fetching for web applications.

Overview

TanStack Query's ten-line AGENTS.md points to the contributor guide and requires one topic per change. Contributors must understand and verify any generated code they touch.

Documents

├── 
└── 

Techniques in this file

01 / Pointing at the source of truth

Apply one contributor contract to human and assisted work

The file requires reading CONTRIBUTING.md before analysis or changes. It explicitly applies the same development, testing, pull-request, and changeset requirements to AI-assisted work.

Source excerpt starting at line 3.
Before analyzing or changing this repository, read and follow[`CONTRIBUTING.md`](./CONTRIBUTING.md). Its contribution, development, testing,pull request, and changeset requirements apply to AI-assisted work as well ashuman-authored work.

02 / Behavioral framing

Pair narrow scope with responsibility for generated code

The final paragraph combines a one-topic change boundary with understanding and verifying generated code. It also directs the pull request description to the existing template.

Source excerpt starting at line 8.
Keep every change focused on one topic. Understand and verify all generatedcode, run the required checks, and provide a concise pull request descriptionthat follows the repository template.

Ideas for your repo

  1. Apply shared contribution requirements to AI-assisted changes explicitly.
  2. Keep each change focused on one topic.
  3. Require understanding and verification of generated code.
Sponsored byModem

Give your agents the whole story.

These instructions explain how to work in TanStack Query. Modem shows your agents what customers said, who is affected, and what changed.

See how Modem works