HACKER Q&A
📣 linchien

How do you handle the gaps between design, product, and engineering?


I’m a frontend developer and I often get stuck in the handoff gaps. Designs change after delivery, specs don’t cover everything, and important context slips through. By the time I sort it out, I’ve spent more time reconciling than coding.

I’m not a native English speaker, so apologies if parts of this post read a bit clumsy.

I’ve tried AI coding tools like Cursor, Claude Code, and Codex. They speed things up, but they don’t fix the real problem. Without full context, the generated UI rarely lands cleanly — layouts feel off, styles don’t match, and it takes a lot of patching. The actual waste isn’t writing code, it’s trying to keep intent and changes aligned.

Do you see the same? What has worked for your team to keep context intact across product, design, and engineering?


  👤 jason_plasmic Accepted Answer ✓
Most design tools like Figma come with some sort of dev handoff tool that produces pixel-perfect HTML/CSS (though you might need some tweaks for responsiveness). Have you tried feeding that to the LLM as a starting point?

I also work on Plasmic (https://plasmic.app) a no-code editor that aims to fix this problem by eliminating the dev handoff, though it does take some organizational buy-in to work.