Ever hand over a clean design concept to be built, only to watch the implementation turn into an unrecognizable mess of misaligned spacings and broken hierarchies?
I ran into this exact friction point recently when trying to sync up visual assets with layout builds. The root cause wasn't lack of effort—it was a broken translation layer between visual spacing tokens and actual layout rules. When spacing values are picked at random instead of tied to a strict mathematical scale, the final build always suffers from layout drift.
The fix is locking down strict design tokens early so that every spacing and sizing decision maps cleanly to a predictable rule.
How do you handle visual handoffs? Do you rely on rigid design tokens to keep things aligned, or do you find yourself constantly fixing layout discrepancies during implementation?
Top comments (3)
Layout drift usually happens because constraints are too loose in Figma long before a developer touches the code. I started using a Figma plugin called DS Sync specifically to catch this, as its unwired value detection flags every single hardcoded spacing property and forces you to map it to a proper token before syncing the PR. It completely kills the guesswork during handoff. Are you enforcing your mathematical scales natively through Figma variables now, or relying on a build step to catch the outliers?
Haha, love the detailed breakdown. To answer your question: I try to keep it native in Figma as much as possible to stop the guesswork early, but a build-step safety net never hurts.
How do you usually structure your scales?