About this tool
Design a consistent variable and style naming scheme, generate a starter token set from it, and lint existing names against the rules.
A variable naming scheme is the set of rules that decide how design tokens are split into segments, how those segments are joined, and how words inside a segment are cased. This helper turns those three decisions into a written rule, renders a full starter token set in that scheme, and lints names you already have against it — flagging stray separators, mixed casing, units baked into names and duplicates. Useful for design system owners aligning a Figma file with the token names their codebase expects.
Open Figma Variable Naming Helper on AltFTool — it loads instantly in your browser.
Add your input to the workspace.
Adjust the options until the result looks right.
Copy or download the output and put it to work.
The scheme is output as plain sentences you can paste into the file description or a README.
Starter names cover both raw ramp steps and the role-based names components should reference.
Every flagged name comes with the corrected version under your chosen scheme.
Use a small number of ordered segments joined by a forward slash — for example color/background/canvas — because Figma renders each slash as a folder in the variables and styles panels. Keep the depth between two and five segments, and describe the role rather than the value so the name survives a palette change.
A primitive names a raw value in a ramp, such as color/teal/500 or space/400. A semantic token names the job that value does, such as color/action/primary/rest. Components should reference semantic tokens so a rebrand only edits the layer in between.
No. A token called spacing/16px has to be renamed the moment the value changes to 12px, and every reference breaks with it. Name the step or the role — spacing/400 or spacing/inset-tight — and let the value live in the variable.
No. It runs entirely in your browser on names you paste in, so nothing leaves the page. Apply the suggested names manually or through your own plugin or token pipeline.