Open Source · MIT · SwiftUI · Web
Signet
**One seal, stamped on every CVER app.**
Every CVER app had independently grown the same color taxonomy and just drifted on the hex values. Signet collapses that drift into one source of truth — a SwiftUI package for native macOS apps and a small web package for the site — so the whole family renders as one. The aesthetic will follow the times; the seal stays.
How it works
1.
Import
Native apps add the Signet Swift package; the site pulls @cvernet/signet from npm. One dependency line replaces the palette, tokens, and chrome each app used to carry its own drifting copy of.
2.
Theme
A CVERTheme is injected through the environment, so a single role taxonomy — ground, deep, accent, highlight, text, border, plus positive/warning/danger — drives every surface. The public API keeps a brand-stable CVER* prefix even though the package is named Signet.
3.
Render
Shared components — buttons, banners, gates, frosted cards, and the borderless liquid-glass window chrome — render identically across snapsift, clioil, reepub, andross, and the rest, while the web package keeps the wordmark, arrows, and squircle corners in step on cver.net.
What's inside
One source of truth
Color roles, a real radius and spacing ladder, and the house wordmark live in one package — no more three drifted copies of the same hex values across apps.
Glass only on chrome
Frosted liquid-glass surfaces are reserved for window chrome and panels; content stays opaque and legible. The borderless glass window is opt-in, not forced on every view.
Brand-stable API
The aesthetic will change with the times, but the public API keeps a CVER* prefix. If the package is ever renamed in a future design era, app code changes one import line, not every call site.
Native and web
A SwiftUI package for the native macOS apps and a small @cvernet/signet web package — arrows, squircle corners, the locale banner — keep the family identity consistent from the app window to the website.
The family identity, factored out
Free and open source under MIT. Signet is internal infrastructure that CVER ships in the open — add the Swift package to a native app or @cvernet/signet to a web project, and inherit the same palette, tokens, and chrome the rest of the family already uses.