Developer handoff: Toggle interface states in web view

I tend to iterate on a single ‘view’ by duplicating artboards and working out the various states and user experiences. I then wind up with a ton of artboards in various states of accuracy. My instinct is to consolidate the designs to a single, final view with hidden layers at the top of the layer tree representing various states of the views (tooltips, open dialogs, modals, etc).

But within the web view you can’t change the layer properties back to visible, and you can’t just browse the layer tree.

So my question is what is the best practice for handing these states off to developers without having tons of one-off views that are likely to become stale?