@clef-sh/design
v0.1.10
Published
Internal Clef design tokens (Tailwind v4 @theme + TS mirror). Implementation detail of the @clef-sh/* workspaces — not a public API.
Readme
@clef-sh/design
Implementation detail — not a public API.
This package is published to npm so the
@clef-sh/*workspaces (the Clef local UI, Clef Cloud) can share one set of design tokens. It is not intended for external consumption. Token names, file structure, and module shape can change in any release — including patch versions — without a deprecation cycle. If you depend on this from outside the Clef organization, expect breakage.
Single source of truth for the Clef design system. Both Clef Cloud and the
Clef local UI (packages/ui) import from this package so token edits land
in one place.
What's here
src/theme.css— Tailwind v4@themeblock.@importfrom any Tailwind v4 stylesheet to inherit the full color / type / radius scale.src/theme.ts— TypeScript mirror of the same values. Exists for inline-style call sites that need a hex literal at runtime (legacy surfaces during migration; computed colors for SVG fills, etc.).
Usage
Tailwind v4 (preferred)
@import "tailwindcss";
@import "@clef-sh/design/theme.css";Then use the generated utility names: bg-ink-850, text-ash-dim,
border-edge, shadow-plate, etc.
TS (during migration / for dynamic colors)
import { theme, radius, shadow } from "@clef-sh/design";
const fill = theme.gold500;What's NOT here
- Component primitives (
.clef-plate,.clef-stat, etc.) — those live in the consuming surface's own stylesheet. This package ships tokens only. - Icons — see
lucide-reactin the consuming package.
Editing tokens
Update both theme.css and theme.ts in lockstep. They mirror each other
1:1 by design; CI does not enforce parity yet (a check is on the
post-migration cleanup list).
