The utility names we took without the framework

A utility layer regenerated with a framework’s naming convention, a year after deciding not to adopt the framework.

@layer utilities {
  .p-4  { padding: var(--space-m); }
  .gap-2 { gap: var(--space-xs); }
  .flex { display: flex; }
}

/* generated from the token file, named to match a
   convention three of three people already knew. */

The point was discoverability rather than the names themselves — a developer who has used the framework can guess our class names, which was the fluency argument the 2025 evaluation was actually about. The coupling is real and mild: if their convention changes in a major, ours either diverges or follows something we do not use.