Purpose: Consistent naming across design system components and tokens.
Referenced by: Component-type instructions, design system operations
Format: [type-prefix]-[number]
Prefixes:
Examples:
btn-001 = First button componentinp-002 = Second input field componentmdl-001 = First modal componentRules:
Format: [Type] [Descriptor] or just [Type]
Examples:
Button (generic)Navigation Button (specific)Primary Button (variant-focused)Icon Button (visual-focused)Rules:
Format: Lowercase, hyphenated
Purpose-Based:
primary - Main actionsecondary - Secondary actiondestructive - Delete/removesuccess - Positive confirmationwarning - Cautionnavigation - Navigation actionVisual-Based:
outlined - Border, no fillghost - Transparent backgroundsolid - Filled backgroundSize-Based:
small - Compactmedium - Defaultlarge - ProminentRules:
Standard States:
default - Normal statehover - Mouse overactive - Being clicked/pressedfocus - Keyboard focusdisabled - Cannot interactloading - Processingerror - Error statesuccess - Success statewarning - Warning stateRules:
Format: --{category}-{property}-{variant}
Color Tokens:
--color-primary-500
--color-gray-900
--color-success-600
--color-error-500
Typography Tokens:
--text-xs
--text-base
--text-4xl
--font-normal
--font-bold
Spacing Tokens:
--spacing-1
--spacing-4
--spacing-8
Component Tokens:
--button-padding-x
--input-border-color
--card-shadow
Rules:
Component Files:
button.md
navigation-button.md
input-field.md
Rules:
components/
design-tokens/
operations/
assessment/
templates/
Rules:
Consistency in naming makes the design system easier to navigate and maintain.