react/client-to-server

What problem does it solve?

This Skill solves the challenge of migrating a TanStack React Table from client-side data processing (sorting, filtering, pagination) to server-side processing so you render only the server-returned slice while keeping pagination and controls correct.

Core Features & Use Cases

• Manual mode conversion for server-owned operations: Set manualPagination, manualSorting, manualFiltering, manualGrouping, and manualExpanding for the operations the server owns.
• Correct pager behavior with rowCount: Provide rowCount from the server so getPageCount() and next/previous paging work accurately.
• Drop redundant row model factories: Remove the matching _rowModels entry (e.g., omit paginatedRowModel) so the client does not re-slice or re-compute server-paginated results.
• External slice state wiring: Own the relevant state slices via external atoms (useCreateAtom + options.atoms) or via controlled state + on*Change so data fetching can key off the slice and refetch automatically.

Quick Start

Tell an AI to convert your existing @tanstack/react-table v9 client table to server-side manual mode by setting the appropriate manual* flags, removing the corresponding factories from _rowModels, wiring slice state to your fetcher, and passing the server rowCount so pagination renders correctly.