{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/83d9696f15284643afdbae5f5b72d9b4\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/83d9696f15284643afdbae5f5b72d9b4-23a1b238703b4fdd.gif","duration":144.372,"title":"Design to Code Workflow with Claude Code","description":"This Loom explains how designers handle design porting using cloud code in a day to day workflow. The speaker contrasts prior reliance on Figma with the current industry norm where cursor is integrated with cloud code, pulling work for the Float page UX revamp branch. They describe using a Git repo for Studio Y, updating components via Nexus file structure and a global component library, and referencing specific components in prompts to prevent cloud code hallucination, including reducing vertical padding by 2px in step node tsx. After changes, the branch is pushed for review and merging by the dev lead, and they show an end to end, fully interactable, prototyped feature on main before it moves through the dev merge flow."}