Design system naming

What it does

Generates and critiques naming for design system components, tokens, and variants, with a consistent rule and rationale.

When to use

• Starting a new design system or component library
• When naming has become inconsistent across a system
• Before a design-to-dev handoff where naming matters

The skill

I'm working on a design system and need consistent naming. Here's what I have so far:

[paste existing component names, token names, or naming patterns]

For each group I describe, do the following:

1. Audit what I have. Point out inconsistencies, abbreviations that break pattern, or names that collide with HTML or common framework conventions.
2. Suggest a naming convention. Give me a clear rule I can follow, e.g. [category]-[variant]-[state].
3. Apply it. Rename anything that doesn't fit.
4. Flag edge cases. What gets complicated as the convention scales?

The system is being built in: [Figma / Tailwind / CSS custom properties / etc.] Who uses it: [designers only / designers and engineers / engineers only]