You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3e8da02
Browse filesBrowse the repository at this point in the historyBrowse files
Enable shadcn/no-raw-colors as an error for all of apps/web/src, including
components/ui (it had no findings there). 267 findings -> 0.
Status colors move onto the tokens the theme already declares, so they follow
custom themes and each light/dark pair collapses into one class:
- amber -> warning / warning-foreground / warning-surface
- emerald -> success / success-foreground
- sky, blue -> info / info-foreground
- red -> destructive / destructive-foreground
The Diagnostics I/O read/write series (sky/amber) and process category dots
use info/warning/success too, the nearest tokens, not status meanings.
One-offs go to the nearest existing token: the favorite model star (yellow)
uses warning, the artifact template sparkle badge (fuchsia) uses primary, the
"waiting for input" toast icon (indigo) uses info-foreground, the CLI auth
eyebrow (blue) uses primary, the provider driver option hover (zinc-50) uses
accent, and the quit overlay pill (neutral-700 + white) inverts with
foreground/background.
SVG strokes in ContextWindowMeter and DesktopUpdateStatusIcon use stroke
utilities with the existing tokens instead of inline color-mix().
No new tokens.
Exemption: Icons.tsx and JetBrainsIcons.tsx have the rule off. They hold
third-party marks that must keep their exact colors (brand logos, and now
also the macOS Screen Recording / Accessibility pane marks from the SnapShot
setup dialog and Codex's Computer Use mark from the work log, moved there
from their feature files for that reason).
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
0 commit comments