Colour theme

Tsugite

A design-system reference built like joinery: pieces meet through contracts that fit exactly — and refuse what doesn't.

Joints, not glue

Tsugite (継手) are the joints of Japanese carpentry: pieces cut to meet so precisely that no nails are needed, and a wrong assembly will not fit. Tsugite brings that idea to the front end. Every interface is a contract, and what a contract does not allow does not exist.

Colour by context, not by prop

A component shouldn't need a prop for every place it can appear. A section steps into a theme — one attribute — and everything inside reads it through one chain.

See the color system

Contrast that is checked, not hoped for

Light, dark and both contrast modes are generated from one source, and their contrast is tested at build. A colour change that breaks WCAG should fail a test, not a reader.

See a test bench

A baseline that always works

The page should work in every browser, with or without JavaScript. Enhancements sit behind support gates, and each colour is authored once in oklch, with its sRGB fallback computed from it.

Watch it resolve

One rule at a time

In ordinary CSS, why a button is blue is usually a sum — cascade order, specificity, breakpoints and inheritance at once. Tsugite aims for one active rule per property, and one you can point at.

  • Gates, not overrides. A property is declared only where it applies. At 1100px there is one padding rule, not three stacked on each other.
  • One hop per layer. A component reads the theme, the theme reads a semantic token, the token reads a raw value. “Why blue?” is a chain you can follow in the inspector.
  • Attributes are the API. Every value of every axis has its own gate, the off value included, so no rule guesses at what is missing.
  • Nobody styles someone else’s class. A composition places its own parts; the button inside a Teaser does not know it is there.