naming-convention

The best way to structure naming conventions for design system components is using patterns like [category]/[name]/[variant]/[state]. For tokens, apply the {category}-{property}-{concept}-{variant}-{state} pattern to standardize assets, improve searchability, and reduce team miscommunication.

Organize design system files by applying the [type]-[name]-[variant].[ext] pattern. Use numbered pages with descriptive names and prefixes for sorting and grouping to ensure assets are predictable and easily discoverable by your team.

Set up automated linting for design token prefixes by defining specific pattern rules, such as {category}-{property}-{concept}-{variant}-{state}. Implement these automated linting checks to enforce consistent naming and discourage abbreviations across your design files.

Design system naming conventions discourage abbreviations to maintain clarity and predictable searchability. Using full descriptive names prevents confusion and miscommunication across teams, ensuring that components, tokens, and files are easily understood during team critiques.

Yes, this naming convention approach works for scaling new design system components by enforcing predictable patterns. Applying standardized rules to new components, tokens, and files enables consistent organization, supports automated linting, and facilitates collaboration as your design system grows.