Repository navigation
v0.1.0: the signature, packaged
The VERSEVA design signature, packaged. First stable baseline: everything below is the
ratified system as extracted on 2026-08-22, with zero visual change from the pre-package
Baseline. Pin this tag; main moves ahead of it.
What ships
tokens.css: the signature. Craft roles (canvas/hairline/text ladders, type trio,
4px spacing scale, radius, elevation, motion, data-viz) plus the soft-glass material
tokens (glass fills, navshell tiers, accent bloom). Dark default, one[data-theme="light"]
flip block.components.css: the component contract as framework-light CSS, every contract state,
navshell ported 1:1.tailwind.css(v4@theme inlinebridge) andtailwind.preset.cjs(v3 preset).verseva-hex-gate: builds fail on any hex not drawn from tokens (hex-okmarks
ratified exceptions,--allowskips vendored paths).docs/: tokens.md, component-contract.md (including view-first-edit-on-intent),
laws.md (the 13 signature laws), theming.md (brand themes, the onboarding checklist).board/(repo clone only): the live render of the whole system with per-theme
switching and live WCAG ratios;npm run board, then open/board/.
Install (pinned)
npm i -D "git+ssh://git@github.com/xhunn/verseva-design-core.git#v0.1.0"Documented in the README
Quick starts (Tailwind v4/v3, no-build surfaces, fonts), 24 screenshots of the rendered
system, theming guide, hex-gate wiring, and the versioning discipline.
Known constraints
- Fonts are named, not shipped: load Archivo/Manrope/JetBrains Mono (variable weights) or
the system falls back to platform faces. - The board runs from a repo clone, not from
node_modules; brand themes pull from a
machine-local manifest and machines without one render the signature Baseline. - Next.js/Turbopack panics on symlinked
file:installs; install from git or a packed
tarball.