They are not skins of one thing. Different palettes, different type rules, different jobs. Answer what you are building before you link a stylesheet, because a token-perfect artifact built on the wrong system looks deliberate.
| What you are building | System | What you link |
|---|---|---|
| Staff reading data in a browser | Dashboards | design.greenvilletriumph.club/tokens.css |
| A member or a guest using a screen | Screens | design.greenvilletriumph.club/screens/tokens.css |
| Anything printed, exported to PDF, or handed over | design.greenvilletriumph.club/print/tokens.css |
Staff reading data in a browser. Scan rates, revenue, inventory, prospect boards.
tokens.css · components.css · agents.md · starter.html
Graphite canvas, one Fabiola hero, Inter headings, mono on every label and number.
screens/tokens.css · pattern.css · components.css · field.js
Two grounds only, navy and fog, with one continuous weave running the page.
print/tokens.css · pattern.css · logos.css
Upstate Fog paper, navy weave bands, Fabiola once. Graphic, never app chrome.
/tokens.css, /components.css, /fonts/, /vendor/, /images/, and the three starters keep their URLs, because roughly forty live projects link them at load time. Changes are additive only: never rename a token, never remove a component class.
Each system folder is self contained, with its own fonts and images. Anything that renders behind office TLS inspection or gets exported to PDF has to self host, so take the whole folder rather than a stylesheet URL.
Sean's own site runs on a separate brand, palette, and repo at design.seantippen.com. It is named here only so nobody reaches for a Triumph sheet on a personal page.
