the scale lived in @theme as --text-heading-*, --text-paragraph-* and --text-monospace-*, so it generated text-heading-3, text-paragraph-small and so on. tailwind-merge classes anything shaped like that as a colour, so inside a tv() whose variants set text colours it dropped the size as soon as a colour followed — which, in those definitions, is always. $lib/tv.ts existed only to re-register the twelve names as font sizes, and every tv() in the app had to import from there rather than from tailwind-variants to pick that up. naming them typography-* sidesteps the collision instead of patching it: the classes match no tailwind-merge group at all, so nothing can read them as colours and the shim is gone. they're @utility blocks rather than theme tokens now, since --text-* is precisely the namespace that spells its utilities text-*. font-size comes first in each block on purpose. tailwind sorts a custom utility into the bucket of its first declared property, which keeps typography-* ahead of every font-weight, leading-* and tracking-* utility in the sheet, so the call sites pairing typography-heading-4 with leading-8 font-normal still resolve the way they did. this does give up size-against-size merging: two typography-* classes in one string no longer collapse, so a size passed in through class= sits next to the component's own and the stylesheet order picks the winner. nothing does that today — Typography takes a variant prop for it — and one classGroups entry brings the merging back if it ever comes up. Signed-off-by: eti <eti@eti.tf>