table-state
This skill builds on @tanstack/table-core#core and this package's getting-started skill.
State Mental Model
TanStack Table is primarily a state coordinator. Keep state internal unless another system needs to read, persist, or drive it. Without initialState, atoms, state, or on[State]Change, the table owns all registered slices.
table.baseAtomsare internal writable atoms initialized from resolved initial state.table.atomsare readonly derived atoms for the active owner of each registered slice.table.storecombines those atoms into one readonly flat store.
The Alpine adapter proxies the table and subscribes it to the store. Reads inside x-text, x-for, x-if, bound attributes, x-effect, or Alpine getters are reactive automatically; event handlers read the current value when invoked. State is feature-based, so missing state or methods usually mean the feature was not registered. Keep features, columns, and source data stable; expose changing reactive data through a getter rather than filtering, mapping, or slicing inside table options.