Ask HN: How do you keep AI coding agents in sync with a changing Figma file?

2 points·rjvidentia··3 comments

I keep running into this: hand a Figma file to Claude Code/Cursor, get a good first implementation, then the design changes and the agent has no memory of what changed or why. Curious if others have hit this and what you're doing about it, if anything.

View on HN

try this free plugin: figma.com/community/plugin/1681329593603309826

workflow:

1. open the file where your variables and components live, run the plugin, hit scan.

2. expert your Figma make into html, they still don't support link import

3. then in your working file drop the html, pick which system to bind to, import.

buttons/inputs/cards come in as instances of your variables, saves life of work

I've experienced this with Claude Code a couple of times. Did you try hash every node/frame of the design. And when the hash changes, that count the state "dirty". Fetch only the diff to Claude Code/Cursor. Or use Figma webhook (FILE_UPDATE event) to trigger diffs automatically. The context in Claude Code/Cursor will then updated without fetching a whole design and still able to track what's changed.

1、Before assigning a task, let the AI know that the Figma design has been updated. 2、From an engineering perspective, use Figma Webhooks to proactively notify your server when there are design updates. The server can then automatically update the corresponding components.

Reply on news.ycombinator.com