Style chunks covering in semantics

[Pi0up]

Hi,

Evary little pieces of a component style must be attached to primtives via semantics, never directly to primitives. This practice provide an easier way to manage styles and usage scopes accross many components as once. PrimeOne have a limited application of that pratice, many tokens are ok and some are not, this "some" require the designer to always refer to various collections to check and update values which is longer than having plain tokens in one collection.
ie. The border color of a component is always linked to the primitive one. border/color/.. must be added in Semantic Color Sheme collection under Primary Secondary etc.
Are those defects will be adressed in next release ?

Regards,

[onursenture]

Hi @Pi0up,

Best practices in design systems are not always universally “best” for every system. In large ecosystems like the Prime libraries, which have a very broad component and feature set, some of these practices need to be applied with a bit of flexibility.

For example, you mentioned that component borders are always linked directly to primitives, but that is not always the case. We also use semantic-level tokens such as content.border.color and form.field.border.color. These help keep the system functional while maintaining the level of complexity that we consider our sweet spot.

At the moment, we are not planning a major architectural change. However, we regularly review and evaluate feedback, so thank you for sharing your thoughts.