TanStack data loading

The first argument selects the mode. With no mode argument, infer it: a request to audit, find waterfalls or review existing code is audit; a request to rediscover or bust the cache is refresh; anything else is writing.

• audit [--fix] [path] — read references/audit.md before starting, and run it over path.
• refresh [path] — rerun Discovery for the app containing path, write the result, and stop.
• Writing — apply the rules below to the code being written or reviewed, within path if given.

Every mode starts with Discovery. The rules branch on what it records: if you guess the backend shape, you apply the wrong server function rules and the wrong write rules.

Available scripts

• scripts/discovery.py — read and write the discovery cache at <repo-root>/.draekien/tanstack-data-loading/discovery.json, one discovery entry per app root; versions prints the installed @tanstack versions. --help lists the exit codes.

Discovery

App root. The nearest ancestor of path (or of the current directory) whose package.json depends on @tanstack/react-start. If none matches, or the task spans several apps, ask the user which app.

Read. Run the script from this skill's directory, passing the app root relative to the repo root (. for a single-package repo):