React components and a documentation site for a B2B eSIM dashboard, so the product's screens are built from one consistent set of parts.
The product was a dashboard for an eSIM business, covering plans, inventory, orders, API keys, webhooks and invoices. It needed the same tables, filters, modals and form controls on many screens, and without a shared library each screen would reinvent them slightly differently.
The library had to be quick for other developers on the project to adopt and fit the shadcn/ui setup the project already used.
Radix-based primitives generated with the shadcn CLI live in one folder. Product components are built on them, and each has a types file that defines its props contract.
As with shadcn/ui, components are copied into the product rather than installed as a package. Each docs page lists the primitives to install and shows the full component source next to a live preview. The project was private and moving fast, and versioning a package would have been overhead.
A minimal router on the History API gives each docs page its own URL, served on Vercel as a single-page app.
A typed table component: columns by accessor or custom render, row keys by field or function, columns resizable by drag with minimum widths, and an accordion layout on phones with the actions pulled out.
Multi-facet filtering with removable chips, each with an accessible label.
Typed variants and six positions from lookup tables, auto-hide with timer cleanup, an alert role and a labelled close button.
Summary cards with Recharts graphs for the dashboard's overview screens.
Copying gave the project full control and no release process. The cost appeared in the docs: component source was pasted into each page by hand, so docs and components could drift apart.
Some components, like the filter, are shaped around the eSIM product's facets rather than fully generic. That shipped the screens sooner, at the price of reuse outside this product.