tanstack-storelisted

# TanStack Store ## 1. Establish the API generation and state owner Read the installed core and adapter versions, lockfile resolutions, existing store definitions, and consumers before choosing an API. This skill's modern examples target core and React **0.11.1**, verified on **2026-09-17**. TanStack still labels Store alpha; resolve newer or intermediate versions against their installed declarations rather than assuming that all `0.x` releases agree. | Evidence in the project | Path | | --- | --- | | Core 0.11.1, React 0.11.1 | Use the modern examples below. | | Core 0.9–0.10 | Signals rewrite, but newer adapter hooks may be absent; verify exports. | | Core through 0.8, explicit `Derived` / `Effect` | Read [legacy.md](./legacy.md) before changing code. | | Multiple core versions, including transitive dependencies | Follow the package resolved by each consumer; retain unrelated library internals. | Choose ownership before adding a store: | State | Preferred owner | | --- | --- | | One component's temporary UI state | Framework-local state | | Shared client-owned state or reactive calculations | TanStack Store | | Shareable navigation, filters, pagination | Router URL/search state | | Remote data, freshness, retries, mutations | Existing server-state cache, such as TanStack Query | | Synchronized collections and relational live queries | Existing data layer, such as TanStack DB | Finish this step with the resolved API generation, state owner, store lifetime, and affected