Skip to content
SOLIDSLATE

Offering

Slate Design System

Most design systems are a Figma file that engineering ignores. Slate is a real component library, in code and in design, kept in sync, documented, and adopted by your teams. We tailor it to your brand and hand it over as something you own and can extend.

  • Design and code in sync
  • Accessible components
  • Themeable to your brand

1 source

Tokens drive both design and code

AA

WCAG 2.2 conformance on every component

Yours

Delivered as a package you own and extend

What you get

In the box

A coded component library

React components, typed, tested and documented in Storybook, published as a package your apps consume.

Design tokens and a Figma library

One set of tokens driving both design and code, so colour, type and spacing never drift.

Accessibility built in

Components that meet WCAG 2.2 AA out of the box: focus management, keyboard support, semantics.

Adoption support

Migration guidance, workshops and pairing, so your teams actually switch to it.

How it works

From kickoff to adoption

Audit your current UI

We catalogue what you have, find the inconsistencies, and agree the component set worth building.

Build the core

Tokens, primitives and the twenty components that cover most of your screens, shipped as a versioned package.

Wire it to design

The Figma library and the code library share tokens, with a process to keep them aligned.

Hand over and extend

Documentation, contribution guidelines and a couple of your engineers trained to own it.

FAQ

Slate Design System FAQ

We already have a Figma design system. Do we start over?

No. We build on what works, fix what does not, and add the coded side that is usually missing. The goal is one system your designers and engineers both use.

Which framework does the component library use?

React by default, with Tailwind for styling and Radix primitives for behaviour. If your stack is Vue or Angular, we adapt the approach.

Can our team maintain it after you leave?

That is the point of the handover: documented contribution process, a versioning and release setup, and pairing so your engineers have shipped components before we go.

Ready for a design system your engineers use?

Tell us what you're working on. We come back within two business days with a point of view and next steps.