The type step the design system calls text-sm is 13px with a 16px line height. Tailwind's built-in text-sm is 14px. The token cannot be used for that step, so feature code writes the pixel value by hand: text-[13px] appears 58 times across 21 files in src/components, part of 109 arbitrary pixel type sizes.
The primitives never worked around it. text-[13px] appears zero times in src/components/ui, where text-sm is used 61 times. One step is spelled two ways depending on which layer the code sits in, and the primitives are likely a pixel larger than the design intends wherever that step applies.
The project has already done this for a neighbouring step. index.css:53-55 defines --text-xxs: 10px with --text-xxs--line-height: 16px and the comment "Figma's text-xxs step, below Tailwind's built-in scale". The mechanism is the same here, except this one overrides a built-in rather than adding below it.
Proposed change. Set --text-sm: 13px and --text-sm--line-height: 16px in the @theme inline block, then replace text-[13px] with text-sm at the call sites. Where a call site pairs it with leading-4, that becomes redundant and goes too.
Verify before doing any of it. The evidence so far is a single text layer in one frame. Redefining the token moves all 296 text-sm uses from 14px to 13px, primitives included, so a button label, an input value and a table cell should be checked in Figma first. If any of those are 14px, the token cannot simply be redefined and the 13px step needs its own name.
Scope is the web UI only, no API change, and no work on the Admin UI. Text at this step changes size across the app.
The type step the design system calls text-sm is 13px with a 16px line height. Tailwind's built-in
text-smis 14px. The token cannot be used for that step, so feature code writes the pixel value by hand:text-[13px]appears 58 times across 21 files insrc/components, part of 109 arbitrary pixel type sizes.The primitives never worked around it.
text-[13px]appears zero times insrc/components/ui, wheretext-smis used 61 times. One step is spelled two ways depending on which layer the code sits in, and the primitives are likely a pixel larger than the design intends wherever that step applies.The project has already done this for a neighbouring step.
index.css:53-55defines--text-xxs: 10pxwith--text-xxs--line-height: 16pxand the comment "Figma'stext-xxsstep, below Tailwind's built-in scale". The mechanism is the same here, except this one overrides a built-in rather than adding below it.Proposed change. Set
--text-sm: 13pxand--text-sm--line-height: 16pxin the@theme inlineblock, then replacetext-[13px]withtext-smat the call sites. Where a call site pairs it withleading-4, that becomes redundant and goes too.Verify before doing any of it. The evidence so far is a single text layer in one frame. Redefining the token moves all 296
text-smuses from 14px to 13px, primitives included, so a button label, an input value and a table cell should be checked in Figma first. If any of those are 14px, the token cannot simply be redefined and the 13px step needs its own name.Scope is the web UI only, no API change, and no work on the Admin UI. Text at this step changes size across the app.