Instrument is monochrome, dense and calm, like a well-made tool. Colour is kept for meaning, hierarchy comes from weight rather than size, and depth is drawn with hairline shadows instead of borders. Everything is plain values (OKLCH colours, pixels, milliseconds), shipped as plain CSS, so it works with React, Vue, Svelte, server-rendered HTML or anything else.

Structure

Principles The eight ideas that decide everything the specs don't cover. Start here
Foundations Colour, typography, space and size, radius, depth, motion, iconography, theming
Components Button, input, badge, chip, tabs, card, dialog, menu, tooltip, toast, banner, empty state, loading, stat, page header, navigation, table. Each has a spec (values, states, rules) and working CSS
Patterns App shell, lists, detail views, settings, marketing pages
Content Voice and copy: sentence case, how errors, successes and empty states are written
Accessibility The baseline every screen meets

Files

File What it is
tokens.css Every foundation as a CSS custom property, for light and dark, plus a minimal base
components.css Every component as plain CSS classes, built only from tokens, with all states
demo.html Every component on one page, with a theme switcher. Serve the folder and open it
adapters/theme.js System, light and dark switching in plain JavaScript, plus a one-line no-flash snippet
adapters/tailwind-v4.css Optional. Maps the tokens to Tailwind utilities, using shadcn/ui's names

Using it in a new project

  1. Load Inter (<link rel="stylesheet" href="https://rsms.me/inter/inter.css">, or self-host it).
  2. Include tokens.css, then components.css, before your own styles.
  3. Add the no-flash snippet from adapters/theme.js to <head>, and wire your theme setting to setTheme().
  4. Build behaviour (popovers, focus trapping, keyboard handling) on a headless library or native elements. The CSS reads state from the ARIA attributes they already set.
  5. (Optional) On Tailwind v4, import adapters/tailwind-v4.css after the tokens to use them as utilities.
  6. Lay screens out with the patterns, and check each one against the list below before shipping.

Review checklist

  • Is colour used only to carry meaning?
  • Is hierarchy built from weight and colour, with no new sizes added to product UI?
  • Do raised surfaces use depth tokens rather than borders plus a heavy shadow?
  • Are controls 32px tall, with gaps of 6–8px inside them?
  • Does motion use the named easings, last 300ms or less, and respect reduced motion?
  • Does every coloured element have its dark value, and has the screen been checked on near-black?
  • Do the busy, disabled, empty and error states tell the truth, and are they all designed?
  • Is the copy in sentence case, are errors written as "Couldn't …", and do empty states teach?
  • Does the small-screen layout work: no sideways panning, chips scroll, dialogs fit?
  • Does every non-obvious value have a note saying why?

Changing it

Change values, keep reasons. Every non-obvious value in tokens.css and components.css carries a comment saying why it is that value. When you change one, update the comment and the matching spec in the docs.

sesan.studio