Skip to content

Consolidate hardcoded AI accent colors onto a theme token and resolve the hue mismatch #57

Description

@rsml

Found by the Phase 5 review sweep, deliberately not fixed there because either resolution changes visible colors and the sweep was bound to zero visual change.

Evidence

  • Roughly 40 instances of oklch(0.55_0.20_285) and 14 of oklch(0.50_0.22_285) are hardcoded in Tailwind class names across 15+ feature files (example client/features/reader/components/EndOfBookFlow.tsx:72,129).
  • client/index.css:38 defines --color-ai as oklch(0.55 0.20 260), hue 260, while the components hardcode hue 285. The 25 degree difference is visible.

Resolution needs a design decision first, pick the canonical accent (260 or 285), set the token to it, then sweep the literals onto the token. Verify with the same-build pixel-control methodology documented in e2e/README.md, since this intentionally changes pixels wherever the losing hue was used.

https://claude.ai/code/session_01FSkESkJTRpt3Ye2cM7c5n5

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions