Sn

Snø UI

Open source React components

Foundation in progress

UI components you can personalize without forking your future.

Snø UI is a React-first component library built around design tokens and a structured update path, so teams can shape their own look without copying component code into every app.

See the systemCurrent scope
Model
Library first
Contract
Tokens over forks
Scope
Lean v1 foundation

Live proof

One component, one contract, two themes

Default system

The package default stays lean and opinionated.

Same component, branded tokens

A wrapper can change tokens without replacing the component.

Consumer shape

import 'sno-ui/styles.css'
import { Button } from 'sno-ui'

<Button>Default button</Button>
Why this exists

Snø UI is not a code generator and not a locked-down black box.

The product direction sits in the middle: install maintained components, customize them through a protected system, and keep moving with upstream updates.

Customize through tokens

Change the visual system through variables instead of editing component internals.

Keep updates possible

Use the package as a maintained base layer, then compose app-specific wrappers on top.

Start with a lean contract

Prove the architecture on a tiny surface before expanding the component set.

How the system works

Keep the component. Change the variables.

The current architecture is intentionally small, but the pattern is already in place: semantic tokens set the design language, component tokens inherit from them, and the React component stays stable.

  1. 1

    Install the package and import one stylesheet.

  2. 2

    Use the component as-is with sane defaults.

  3. 3

    Override semantic or component tokens when the brand changes.

Current state

The foundation is real, but still intentionally narrow.

The goal of this stage is to prove the architecture on one component before the library expands. That keeps the system honest.

Token-driven button foundation is working.

Package exports compiled CSS and typed React components.

Landing page is now a real consumer of the library.

Docs depth, theming guides, and more components come next.