Design Token Naming Generator — illustrative example

INPUT
Interface uses blue for primary actions and gray for secondary text; dark theme planned. No exact values or existing naming convention supplied.

RESULT
Semantic roles:
color.action.primary → theme-specific primary-action primitive
color.text.secondary → theme-specific secondary-text primitive

Theme values: unresolved until actual colors and contrast requirements are supplied.
These names describe use rather than the current color; review them against existing team conventions before adoption.

REVIEW
Design token names should describe a stable role rather than a temporary appearance. Separate primitive values from semantic uses and check consistency with the team's existing naming convention.

This is a teaching example, not a live execution record.