You can do it that way but it’s not the easy path. I think the problem with the tool is that Figma makes it too easy to make polished interactive designs that look done. The easy path is just to skip the wireframe, so by the time the programmer gets involved, the designer and management has already fallen in love with what appears to be a final product.

If figma was built on top of HTML and CSS—and so couldn’t represent designs that HTML and CSS can’t, this might be less of an issue.

Granted it would still be a problem because there are always underlying technical and processes issues that should be uncovered before you leave the wireframe phase that have nothing to do with HTML and CSS.

You are right that tools don't solve problems, but they can cause them.

The problem here is that designers are limited by their tools. Figma can only do 10% of what CSS is capable of.

We can try to work around those issues with closer collaboration early on, but the truth is that most of the problems aren't universal. They are constructed

It works better in house for sure or with a good agency. There's a whole industry of fancy corporate design agencies that produce Figmas and developer-in-the-loop means going into lots of meetings with the consultancy managers and then waiting a week and a couple grand in hourly for them to produce something that needs to be fixed again.

But ignoring those fixable processes and hiring issues, there is plenty to be said about the new world of isolated islands of UI/UX designers, frontend, backend teams. I blame Javascript/React eating the world more than Figma. React/Vue opened up a whole hyper complex world of UI design and shit rolls downhill from UI->frontend->backend->users (mostly via performance/complexity).