Theme token groups

A template owns its visual system as data. Token names are the author’s — there is no fixed vocabulary and nothing is required to exist, so a sparse theme is still a working theme. One token cannot back two utility names; declare both. Breakpoints are the template’s too: the kit declares none and resets none, so Tailwind’s own arrive untouched and this is where you add the rest.

group	compiles to	what belongs in it
colors	--tr-color-<name>, aliased to Tailwind’s --color-*	every colour the template uses; yields bg-<name>, text-<name> and border-<name>
fonts	--tr-font-<name>, aliased to --font-*, plus the @font-face/@import CSS any entry needs	font families; yields font-<name>. A bare CSS stack loads nothing; an entry (family + fallback + either files or href) also loads the face
type	--tr-text-<name>, aliased to --text-*	font sizes; yields text-<name>. A name here must not also be a colour — both compile to text-<name>
radii	--tr-radius-<name>, aliased to --radius-*	corner radii; yields rounded-<name>
shadows	--tr-shadow-<name>, aliased to --shadow-*	shadows; yields shadow-<name>
layout	--tr-<name>, with no Tailwind alias	layout values that have no utility namespace — read them with var(--tr-<name>)
breakpoints	--breakpoint-<name>, i.e. a <name>: variant prefix	the widths THIS template’s design swaps at. Optional — Tailwind’s own sm/md/lg/xl/2xl are already there and the kit adds none. A name that is a Tailwind state variant (hover, dark, …) is rejected
document	the document defaults	which of the template’s own tokens dress the page — font, color, background and fontSize, each naming a token declared above