Skip to content

Codify the accent usage system (purple/green duotone) #130

Description

@zachdunn

The accent evolved to #c27eff (PR #127), but live prototyping showed hue shifts barely register at current usage density — ownability has to come from a usage system, not the hex. The terminal already implies one: purple = prompt/action ($, primary buttons, focus), green = success (>> ready lines, ok badges).

Write it down as DS guidance (tokens.css header comment + the Claude Design project's README/prompt docs), then audit surfaces for violations and for one or two places where the accent is allowed to be loud (a drenched moment on the landing page?). Related: .context/2026-07-13-impeccable-audit-and-agent-plan.md Phase 3 T3.4.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions