Claude Design produces much better UI than I get out of Claude Code on its own, but the two do not know about each other. Different product, own projects, own chats, own files, no API. Everything I designed there, I copied into the repo by hand. I managed to solve it. Free, open source, MIT: an MCP server that lets Claude Code brief the designer, wait for the reply, read what it said, screenshot the rendered page so it can judge the result, and pull the files straight into your working tree. What makes it useful rather than a toy is that it can attach your actual codebase to the design project, so it designs against your real components instead of inventing new ones, and it can push files back up, for example new components into a design system. Three implementation notes, in case you are building similar bridges: Native dialogs are a wall. “Link local code” browses with window.showDirectoryPicker() , an OS dialog no automation can touch. The way through is not to drive it but to replace it: read the folder in Node and hand the entries to the page. Guard destructive tools by name, not by id. delete_project demands the project’s exact current name and refuses the UUID. An agent will happily carry a UUID over from the wrong step, while a name has to be looked up and matched on purpose. Same reason GitHub makes you type the repo name. Sessions, not tokens. No API, so it drives a real browser. The seed step copies only claude.ai cookies out of a Chrome profile you already use, and there is a login command for when the session expires. It installs as a Claude Code plugin and ships a skill, so in practice you just say what you want designed. Link in the first comment. submitted by /u/Intrepid-Ad4494
Originally posted by u/Intrepid-Ad4494 on r/ClaudeCode