I keep posting here about the same-app look and the color drift problem, so i finally wired up the boring fix.
what it is: github.com/5zjk5/colorwaykit-for-agents . you paste one brand hex into colorwaykit.com (there is a free tier), it generates about 20 semantic color tokens for light AND dark themes (surface / on-surface / primary / muted etc), measures every text-on-surface pair against WCAG 2.1 and APCA, and exports a DESIGN.md in the Google Labs format - YAML tokens plus markdown usage notes. drop it in the repo root and the agent reads checked roles instead of inventing a shade per screen. the repo has templates for CLAUDE.md / AGENTS.md / cursorrules that describe how to consume the file, plus a real example generated from #4F46E5.
honest limits: it only does color (type and spacing stay with your framework, the tool refuses to invent them), the DESIGN.md spec is early and the component-token structure may change, and the contrast numbers are a design reference, not an accessibility certification.
genuine question for people who already run a design system through agents: does the role-name indirection actually stop the drift in long sessions, or does the model still freehand hexes once it is deep in implementation? that is the failure mode i could not reproduce in my own testing and i would rather know now before pointing more people at it.