Front-end developers grab brand colours for CSS variables. Marketers match CTA buttons to decks. Students learn hex notation. Pair with Image Effects when adjusting photos toward a palette, and with QR and print workflows where contrast matters for scans.

Colour appearance shifts by display calibration — pickers report values, not perceptual guarantees on every monitor. For accessibility, check contrast ratios with dedicated auditors beyond a simple pick.

Name tokens by role such as color-primary and store hex in the design system, not in chat folklore. Check contrast for body text before shipping colourful marketing blocks. Soft-proof brand colours on the devices your customers use when the brand is strict. When handing off, include contrast ratios for primary text-on-colour pairs next to the hex.

Store tokens with semantic names and contrast notes so engineering does not inherit mysterious hex soup. When a rebrand lands, replace tokens deliberately rather than hunting hard-coded shades across repositories.

Export a small token JSON beside Figma so engineers do not re-type hex from screenshots. Screenshot colour pickers introduce rounding drift that accumulates into off-brand interfaces after a few sprints.

Pick once, tokenise, then reuse. Ad-hoc hex values across CSS modules create brand drift that no amount of marketing complaints can reverse without a cleanup project. For charts, verify series colours under greyscale and colour-blind simulations before calling the palette done. Record light and dark theme pairs together so night mode does not inherit accidental low-contrast leftovers from a daytime mock. Ship tokens through pull request review the same way you review copy so a late palette change cannot land unnoticed on a Friday deploy.