I broadly that this sounds like a people problem rather than a tooling problem, but I would add: >If you have a team of developers and they're not able to deli

I broadly that this sounds like a people problem rather than a tooling problem, but I would add: >If you have a team of developers and they're not able to deliver to a specification, the problem is with the developers, not the tools you're using. Or the problem lies in the designers providing the specification, which is also a situation I've seen a few times. A good design specification isn't just providing a view of the overall layout, it's also providing the pieces that went into that design: the visual components, the guidelines used for layouts, a list of colours and distances used, etc. Simply providing a "pixel perfect" version will not get you good results, because that's essentially a lossy translation of the designer's intent. To implement that intent, you need information then just, for example, how big each button needs to be, you need to know how big a button can be, how small it can shrink to, what should happen with oversized or undersized text, how it will be positioned in its containers etc. Partly that's because intent is often a clearer way to communicate things than results, but mainly it's because there's no such thing as a pixel-perfect render target. Browser sizes can change, phones can be rotated, and people will insist on all sorts of different resolutions. It's only by describing intent (this element should fill the space, this point should be equidistant between these two points, etc) that you can adequately support all these situations. That said, I broadly agree with you that this sounds more like a people problem than a technology problem.