Re: [community-group] Consider adding standardized extensions (#269)

Hi @TzviPM!

I'd love for you to give https://github.com/amzn/style-dictionary/discussions/1479 a read and to share your feedback. It's a proposal for a not-standard-yet data format that could augment design tokens with information relevant to tool makers. Some of that format is concerned with more accurate typing of design tokens.

My goal with presenting an opt-in format outside of DTCG is to allow people to try it out, provide feedback, break away from it freely, and to see what ends up providing value to the community a few years down the line, before knocking on DTCG's door with a more formal request.

I've been facing the same issue you're describing, with both Tailwind and PandaCSS. I've been wanting to have a formal way to tell that a token has a specific type, without writing a tailor-made Style Dictionary format / Terrazzo plugin for every company I work with based on how they name their tokens.

Token Listing could be a first community response to this, where end users of design token tools provide a single annotation/extension key, or a single config function; where the listing file can then carry that information other to any current and future tool that wants to exploit it; and where tool makers aren't too concerned with stability and can trust that the format is worth supporting.

I have a PoC you could try over at https://github.com/terrazzoapp/terrazzo/pull/553 if you're interested, though without support in the Tailwind plugin (and without PandaCSS support either).

-- 
GitHub Notification of comment by Sidnioulz
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/269#issuecomment-3361992481 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 2 October 2025 16:01:27 UTC