UI Libraries
Two React component libraries built on Base UI: the warm, friendly Ink UI and FigUI in the style of Figma UI3.
- 2025.07.12 β Present
- Solo design & development
I designed and built two React component libraries on Base UI. Both grew out of other projects.
Ink UI
Ink UI began as the internal component library of Flowingto and was later extracted and open sourced. It is styled with Tailwind CSS v4 and lives at ink-ui.com.
The design is organized around warmth and friendliness: warm grays and orange as the primary colors, with generous corner radii. The goal is an interface that feels more personal and approachable, which makes it a better fit for consumer products than for dense, data-heavy admin panels or dashboards.
Color
Ink UI does not use Tailwind's default stone palette. The gray is adjusted by hand so that it is only slightly warmer than a neutral gray, close to the feeling of paper. The primary orange and the secondary red are also handpicked, and are less saturated than Tailwind's colors of the same name. Every color is expanded into a scale in OKLCH space to keep the visual result consistent.
gray
orange
red
States
shadcn/ui expresses component states mainly by layering transparency over a base color, for example hover:bg-primary/90. That approach has two limits: the resulting color can only move in one direction, so hover cannot darken in light mode and lighten in dark mode; and hover and active cannot be given separate semantic colors. On top of the shadcn/ui theme, Ink UI adds dedicated tokens for the different states of a surface color. Each state can then be controlled precisely, which covers most of the interaction cases in a design system.
--background
--card
--primary
--secondary
--accent
--destructive
Each state is derived from its base color by mixing toward --foreground with color-mix, so the same formula darkens hover in light mode and lightens it in dark mode. Switching the theme shows the difference. secondary is the exception: it is a translucent tint composited over the background, so its hover and active states raise the alpha instead.
Motion and details
Motion favors smooth, natural transitions. Micro-interactions stay restrained: they add polish without pulling attention away from the content. These include:
- the transition when a button enters its loading state;
- text alignment in a menu when only one item has an icon;
- menu and select triggers keeping their hover state while the panel is open;
- spacing kept above and to the right of the scroll bar.
FigUI
FigUI grew out of building Annotation Toolkit and lives at figui.dev. To keep the plugin consistent with Figma's native experience, I looked at the existing plugin component libraries, and none of them met the need: some still followed the UI2 styles, and some were implemented as Web Components rather than React components.
Design tokens
Ink UI's colors had to be tuned one by one; FigUI's colors must not be tuned at all. Its colors, radii, shadows and type are taken directly from the styles of Figma's web app. Radii come in three steps of 2px, 5px and 13px, and body text is 11px Inter at weight 450. Figma uses semantic tokens there, but I wanted to rebuild the components entirely the Tailwind way, so with the help of AI I transcribed them into Tailwind's atomic tokens, keeping the original values of the gray, blue and other scales. Since the goal is a complete replica, there was no reason to keep Tailwind's default colors: I cleared them all from the theme, so components can only use Figma's scales.
Inputs
General-purpose component libraries rarely include the inputs found in Figma's properties panel, yet those are what plugin interfaces use most. FigUI adds several Figma-specific controls: a number input whose value changes as you drag left or right on its X or Y label, a color input made of a swatch, a hex value and an opacity field, and an input group that merges several inputs into one row. Drag-to-scrub is built on the ScrubArea of Base UI's NumberField; while dragging, the input shows a blue ring and the cursor becomes a left-right arrow, matching Figma's behavior.
A plugin panel built with FigUI, light theme on the left and dark on the right. The position, height and fill rows all use Figma-specific inputs
Status
29
Ink UI components
16
FigUI components
59
GitHub stars combined
Both libraries are open source. Ink UI serves mainly as the component library for my own projects and is used beyond Flowingto as well. FigUI is used by Annotation Toolkit and is listed on Base UI's community page.