Create and apply styles

Create a base color and text style set for the dashboard: add Primary Blue 320, Secondary Gray 80, Body / Regular 16px Inter, and Heading / Bold 24px Inter. Apply them across the dashboard frames so colors and fonts are linked, and leave a comment for Priya telling her where to change the primary color if the marketing team requests an update.

Before I hand this file to the brand reviewer, make styles usable: extract repeated fills and type into named styles, replace local overrides with those styles where appropriate, and produce a short list of three inconsistent tokens the brand team will want changed.

Designers pushed a dashboard with Primary Blue in five slightly different hexes and body text set locally. The brand lead will review tomorrow. I don't know whether converting to styles will change spacing or break instances. Should I normalize the colors into one Primary Blue and create text styles now, or freeze and ask designers to update after brand sign-off? What's the least risky route to get consistent visuals for the review?

Over several releases we keep redoing colors, typography, and spacing because styles were not established early. That eats design time and confuses engineering. Are we failing to lock tokens upfront, or failing to enforce them in component creation, and what single rule change would stop repeated style churn?