The basic rules should be documented in the style guide, design system, and/or libraries. What would be interesting is to bridge the gap between the Invision Sp

The basic rules should be documented in the style guide, design system, and/or libraries. What would be interesting is to bridge the gap between the Invision Specs and what you expect. Indeed, I ran a survey on 8 devs, and I've been monitoring how they typically use it over the years (Invision, Zeplin, basic screenshot hosting...). Some Devs won't use the specs at all, sometimes delivering something off. Others, love it since it will reduce the back and forth during audits. You're right, specs will only be usefull to provide the dimensions and colors. However, this part is automated on the UX side, it prevents us from writing it down, which would be a waste of time: Mockups always change, we'd have to manually update the said specs so many times... This wouldn't scale well.