Use symbols for repeated elements

Replace the repeated button icons in the UI kit with a Symbol instance. Select the master icon, convert it to a symbol named Button-Icon, swap the four existing icons to instances of Button-Icon, and then link the symbol so updating the master will update all screens before the developer handoff on Thursday.

Before I hand the UI kit to the product team, make the repeated elements easy to maintain. Surface where symbols are used by listing artboard names that reference each symbol, show the symbol’s overrides (color, scale), and flag symbols that contain raster effects so engineers know what might need flattening.

I converted the main navigation icon to a symbol and swapped instances across artboards, but on the mobile screen the icon lost its hover color override and snapped back to the master art. The product manager will test prototypes tomorrow. Why would that one instance revert, what do I tell the PM about prototype risk, and how do I restore the intended override quickly?

We repeatedly rebuild repeated assets instead of using symbols, which lets small changes cascade inconsistently and forces manual fixes during QA. That costs us engineering trust and adds two days to every sprint. What naming convention, workflow rule, and quick audit should we adopt so symbols are used from the start and stay reliable through handoff?