Naming contract

Names align to Tailwind v4's theme namespaces. This is free for other frameworks — they are ordinary custom properties — and means most of them can be exposed as Tailwind utilities through an alias block, without any framework taking a dependency on Tailwind.

Most, not all. Three of the namespaces below are Jig's own and have no utility behind them in Tailwind v4 — the Utility column says which. Aliasing one is accepted silently, emits the custom property, and generates no rule, so the class lands on the element and does nothing. That is the same silent failure this file warns about under Optional: Tailwind utility classes, reached from the other direction: there the alias is missing, here the alias is present and the utility does not exist.

--duration-* and --ease-* had one row between them and only one half of it works, which is why they are separated here.

Reading a no token from a class. Use Tailwind's custom-property value form, which needs no alias and keeps the semantic name: max-w-(--measure-prose), duration-(--duration-fast), outline-(--focus-ring-width). That satisfies H-47 — the value is still the token — it simply does not route through @theme. The same form covers any token a mode file adds that has no namespace at all, such as the --grid-* values.

Verified by compiling one alias per namespace against tailwindcss@4.3.3 and reading the output. Probe each namespace with a *distinct* token name if you re-check this: text-*, border-*, outline-* and max-w-* each read more than one namespace, so a shared suffix makes a colour alias look like proof that four other namespaces work.

Rules

1. 1.
   Semantic names only at the point of use. --color-text-strong, not --color-neutral-900, in component code. Primitives exist to build semantics, not to be consumed directly.
2. 2.
   No component-scoped tokens. --button-bg belongs in the component, referencing --color-brand.
3. 3.
   A value that cannot be expressed as a token is a missing token, not an exception (H-47).