unset.sh Brand guide
Contract v0.1.1

unset.sh / shared foundations

The Unset design system.

A common visual language for the app, chat, documentation, and renderer. Quiet surfaces, clear hierarchy, and colour with a purpose.

Contract v0.1.1 · shared foundation

This guide follows the brand repository. For package availability, check the release history. Each application adopts an exact version and validates its own integration.

Start with clarity

Use type, spacing, and structure to make the next action easy to find.

Keep colour meaningful

Neutral controls. Distinct links. Feedback that explains itself.

Share the decisions

Use named roles so each repository follows the same foundation.

Identity

Selected direction

Keep the existing mark and let the interface do the work. The identity is carried by careful typography, restrained geometry, and consistent details.

Unset three-ring markUnset three-ring markunset.sh
Existing mark · original proportions preserved

Use the original asset

Keep the rings, spacing, and proportions intact. Leave space around the mark and place it on a clear surface.

Download the current SVG

Keep the asset family together

The brand repository already contains logo variants, favicons, and app icons. Verify small sizes and theme behaviour when applying them. This specimen preserves the existing mark.

Colour

Working values

Graphite neutrals support the content. Pacific and lavender belong to links; success, warning, and error each have their own role.

Showing dark appearance. Switch themes to compare the same roles.

Foundation

Links

Link-state specimens. Real links use the browser’s visited state; primary buttons and information messages remain neutral.

Feedback

Every state combines readable text, a symbol, and colour. These are static specimens, not live notifications.

Explore alerts · Try the toast examples

Typography

Working recipes

The interface typeface carries headings, prose, labels, and controls. The monospace typeface distinguishes code, identifiers, and short technical details.

Interface typeface

A place to make your own.

Shared typography gives every surface a familiar voice.

Build hierarchy with size, weight, and spacing. Keep reading widths comfortable, labels explicit, and paragraphs easy to follow.

Aa Bb Cc & 0123456789

Reading and interface

This guide uses 1rem body text with generous line height. It keeps longer prose to a comfortable measure and lets content reflow.

Code and identifiers

mika.unset.sh
color.ground
brand@0.1.1

Moss & clayTypeScript
// A small space, made your own.
const profile = {
  name: 'Mika Rowan',
  published: true
};

View the typography specimen · Explore syntax and code blocks

The shared heading scale and renderer-specific type sizes are marked provisional in the contract. Keep those choices explicit when adopting the package.

Icons

Tabler 3.52.0

Use Tabler outline icons with a consistent 2px stroke. Keep glyph size separate from the size of its button or touch target.

16pxInline detail
20pxAction or status
24pxStandalone symbol

Decorative icons are hidden from assistive technology. Meaning comes from visible text or the control’s accessible name.

Browse Tabler Icons · Tabler Svelte documentation · Icon licence

Components

66 main entries

The live gallery applies the same roles to real shadcn-svelte components. Open a family to try its controls, states, and both appearances.

shadcn-svelte component documentation

Default controls are 40px high; an icon inside is usually 16px or 20px. Compact sizes, meaningful labels, and focus behavior are part of each recipe.

Browse all components

The gallery covers the main catalogue, not every possible variant or third-party component. Each application still needs integration and accessibility checks.

Use the system

Version 0.1.1

The contract gives people and tools the same named decisions. Edit a colour, typeface, or component recipe once, regenerate the shared output, and review the result here. Stable role names keep consuming repositories consistent.

  1. Read the role. Use color.ground for a page canvas and color.link for an unvisited content link.
  2. Check its status. Working values are ready to review. Provisional values are candidates, not stable defaults.
  3. Consume one version. Pin the contract and matching assets. Import the package styles and assets rather than copying values by hand.

Import the foundation

The base CSS works in any web interface. Add the Tailwind and shadcn adapters only in applications that use them; the renderer can read the JSON contract directly.

Shared stylesheetCSS
@import "@unset-sh/brand/tokens.css";

.page {
  background: var(--ground);
  color: var(--ink);
  font-family: var(--font-sans);
}

For a Tailwind v4 interface, install tw-animate-css, then add the shadcn adapter and token mapping. The optional recipes supply the shared component refinements shown in the gallery.

Tailwind and shadcn-svelteCSS
@import "tailwindcss";
@import "tw-animate-css";
@import "@unset-sh/brand/tokens.css";
@import "@unset-sh/brand/shadcn.css";
@import "@unset-sh/brand/tailwind.css";
@import "@unset-sh/brand/recipes.css";

@custom-variant dark (&:where([data-theme="dark"], [data-theme="dark"] *));

The adapter targets the gallery’s pinned Vega markup. Set the root appearance and class as shown; data-recipes="true" opts into the shared refinements.

Root elementHTML
<html class="style-vega" data-theme="dark" data-recipes="true">

Use data-theme="light" for the light appearance. Check the consuming component version and markup: CSS updates styling, not copied shadcn component source or behavior.

Loading the contract…

Token values for the selected appearance
RoleValueStatusCopy value
Query the same contractjq
jq '.tokens[] | select(.id == "color.link")' contract.json

Publishing makes a new version available. Each consuming repository updates its pinned dependency, runs its checks, and rebuilds before that version reaches users.