Skip to content

chore: Figma cue/indigo does not match CuePointType.defaultPalette slot 5 #783

Description

@one-soft-engineer

Found while building the Figma design for #782. Not caused by it, and deliberately left untouched there.

What

The Figma design-system file (NhH2957iKQ8b581x3gI3Wk) and CuePointType.defaultPalette disagree on one of the eight cue colors.

Slot Figma variable Figma value Code value Match
5 cue/indigo #6155F5 (blue-violet) #4ECDC4 (teal) no

The other seven slots match exactly.

Why it matters

The rendered Figma screens (318:1228) already show teal in that slot, so the screens agree with the app — it is the named variable that drifts. Anyone binding a new node to cue/indigo on the assumption that it is the fifth palette color will get a blue-violet that does not exist in the app. The variable name is also wrong for the code value: indigo describes #6155F5, not a teal.

Options

  1. Change the Figma variable to #4ECDC4 and rename it cue/teal. Makes Figma follow the shipped app. Requires first auditing which nodes currently bind cue/indigo — some may want the blue-violet for a non-cue purpose.
  2. Change the code so slot 5 is #6155F5. Rejected on sight: it silently repaints every existing document that uses that cue type, and there is no migration story for a palette value.
  3. Add cue/teal alongside and leave cue/indigo for whatever else uses it. Safest if the audit in (1) turns up real consumers.

Option 1 is the likely answer, gated on the audit.

Acceptance criteria

  • The set of nodes binding cue/indigo is enumerated.
  • Either the variable resolves to #4ECDC4 under a name that matches, or cue/indigo is documented as intentionally not a cue-palette color.
  • Figma and CuePointType.defaultPalette agree on all eight slots.

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

    area:uiSwiftUI viewschoreInfra / process / tooling workp2Nice to have

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions