Back to stack guides

Intent

Keep utility-first styling coherent without arbitrary-value drift, unreadable class duplication, or premature wrapper components.

Checks

  • Map recurring semantic colors, spacing, radii, and type roles to shared tokens.
  • Keep responsive behavior near the component and verify class ordering remains readable.
  • Extract repeated component structure, not one-off class lists.

Warnings

  • Frequent arbitrary values and duplicated state selectors indicate a missing token or primitive.

Exceptions

  • A truly unique fixed-format element may require one explicit arbitrary constraint.