Update to TanStack

{
  "description": "Introduce, add, debug, or migrate TanStack DB for reactive collections, live queries, and optimistic local updates.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 96
    }
  ],
  "name": "tanstack-db",
  "skill_md_contents": "---\nname: tanstack-db\ndescription: Introduce, add, debug, or migrate TanStack DB for reactive collections, live queries, and optimistic local updates.\n---\n\n# TanStack DB\n\nReactive collections, live queries, and optimistic local updates.\n\nUse it for: Views that join or filter shared collections, optimistic writes, or synced local data.\n\nUsually unnecessary for: A simple remote read that Query already handles. DB is not a hosted database.\n\n## Install and try\n\nUse the project's framework and package manager. These examples target the current official documentation checked on September 30, 2026. Match installed versions before copying them into an existing project.\n\n```sh\nnpm install @tanstack/db\n```\n\nMinimal example, run in a TypeScript module:\n\n```ts\nimport { createCollection, localOnlyCollectionOptions } from '@tanstack/db'\ntype Todo = { id: string; text: string }\nconst todos = createCollection(localOnlyCollectionOptions<Todo>({\n  id: 'todos', getKey: todo => todo.id,\n}))\ntodos.insert({ id: '1', text: 'Ship the app' })\ntodos.update('1', draft => { draft.text = 'Shipped' })\nconsole.log(todos.get('1')?.text)\n```\n\nThis example is memory-only. Persistence requires a collection adapter. New SSR work uses stable collectionOptions descriptors and a request-scoped DbClient. Match the installed DB version before adopting that newer API. For remote writes, supply real handlers and test failure rollback.\n\n## Implement, debug, or migrate\n\nRead the project's package manifest and lockfile before changing dependencies. Load version-matched TanStack Intent guidance with `npx @tanstack/intent@latest list`, then `npx @tanstack/intent@latest load` followed by a concrete identifier returned by the list. Do not invent skill names or assume every version includes skills. If no relevant skill is packaged, use the installed version's official docs and source. Current web docs can describe a newer API than the lockfile.\n\nFor an existing project, reproduce the failure and change the smallest relevant integration. For migration, read the version-specific migration guide and preserve behavior through a small verified slice before migrating the rest. Run the project's relevant build and checks, then verify the user-visible feature. Do not add unrelated TanStack packages.\n\nIn ChatGPT without a shell or repository tools, use the connected documentation tools and provide the code and exact commands for the user to run. Never claim files were edited, packages installed, or checks passed without execution evidence.\n\n[Official docs](https://tanstack.com/db/latest/docs/overview) · [Version-matched guidance](https://tanstack.com/intent/latest/docs/overview)\n"
}