Skip to content

The base layer

Every Khaeli product, and every design system Khaeli builds for a client, stands on @khaeli/foundation.

@khaeli/foundation is the one base layer, and it fixes the structure of every screen: the control, the radii, the type roles, focus and motion. A product, or a client, brings its palette and its typefaces, and nothing else. Each section below shows one thing the foundation fixes.

One control height

Every single-line control is 30px tall on desktop, so tabs, a field, a select, a toggle and a button line up in any row. The height is the foundation's, and no product changes it.

The same screen under two brands

Palette
Harbour studio
  • Home
  • Invoices
  • Customers
  • Payments
  • Settings

INV-2050

Sent

Kestrel Print Co

Switch the palette: the fill, the switch, the checkbox, the link, the focus ring and the current destination's icon take the client's primary, and nothing else moves. The layout, the control, the radii, the type, the neutrals and the status colours are the foundation's under every brand.

Two weights and the type roles

Invoice INV-2049caption, regular
Oakline Joinerytitle, medium
£2,400.00heading, medium
Staircase survey, 30 hoursbody, regular
Due 12 December, by bank transferfootnote, regular

Text is set in a role of one scale, never in a size of its own, and in one of two weights, regular and medium. Bold and semibold render medium, and every class of the scale is on Headings.

Focus that only a keyboard shows

Click a control and no ring is drawn; press Tab and each one shows where the keyboard is. Every Registry component draws focus this way, in the product's accent, so no screen styles its own.

What a product sets, and what it never changes

  • A product sets the primary family, the tints, the chart series and the three font families.
  • It never changes the control height, the radius ladder, the type scale and its two weights, the spacing unit, the motion tokens, the neutrals or the status colours.

Theming names every token a product may set and shows the override.

Who decides a screen

  1. @khaeli/foundation decides structure and how components behave.
  2. The product's own design.md decides what that product chose, with each exception it takes and why.
  3. House Taste, the rules on the pages that follow, decides what a screen holds, where colour appears and what moves, wherever that file is silent.

Where two differ the earlier one holds, accessibility is traded for none of them, and the Finish Review checks a built screen in this order.