A headless library where every part is a slot you can replace, and everything you don't replace renders as finished, accessible HTML. Ship on day one, match your design system on day forty, never fork.
import { DataTable } from"slotsmith"// It works, and it already looks finished.
<DataTable data={users} columns={columns} />
Two kinds of parts
Element parts
Root · Table · Row · Cell …
Plain DOM props, state as data-* attributes. Drop in shadcn, MUI or Chakra primitives unchanged.
Widget parts
Checkbox · Pagination · Empty …
Semantic props like checked and pageIndex. Your components, through a few-line adapter.
Data table
21 parts · TanStack v9
Built on TanStack Table v9, with 24 replaceable parts. Drag rows to reorder them, several at once, across tree levels and between tables; edit it like a spreadsheet; and pick from six ready-made themes.
Client or server sorting and pagination
Selection that survives server pages
Spreadsheet mode: cell editors, copy and paste, fill, undo
One date, several, or a range, with 15 replaceable parts. Type the date or pick it from a full keyboard grid, with bounds and blocked dates, presets, and ISO values in the format and time zone you choose.
slotsmith-ai is an MCP server for coding agents such as Claude Code, Cursor and VS Code Copilot. It hands them the exact props, slots, fallback markup and MUI, shadcn and Chakra adapter recipes for the slotsmith version you have installed, and warns when the versions differ. No guessed props, no invented slot names.
Fallbacks shipIf the built-in look isn't production-ready, it isn't done.
Uncontrolled firstNo required state to render anything.
Every string a labelTranslation and RTL are props, not a fork. 18 ready-made language packs ship in, Arabic included and right-to-left aware.
AccessibleKeyboard paths, ARIA and focus live in the fallbacks.
No runtime depsOnly the peer a component is built on.
Why I built it
Styled kits hand you someone else's design language; headless kits hand you a blank page and a week of rebuilding the obvious. After shipping the same tables and pickers across client projects, I wanted the middle: behaviour plus named parts, each with a fallback worth shipping.
This is only the beginning
Four components today. More are on the way: new components, better versions of the ones that exist, and ideas that make everyday programming easier. Same rules for all of them: headless logic, replaceable parts, fallbacks good enough to ship.