TO
3.9K posts
I've been playing around with this new design-to-code tool called @paper for the last few weeks. I wasn't expecting the gap with Figma to be this big. I gave both tools the 2 exact same prompt, identical starting point: redesign a 404 error page. Figma gave me three options that were basically the same. It ignored half the prompt. Paper gave me three distinct designs with better copy and a split view layout that I really liked. The output is real HTML, CSS, and Tailwind. So I took Paper's winning design, connected Claude Code through the MCP, and built it directly into the codebase. It asked me questions about button logic and existing routes. It pulled from the current design system. The final result was almost 1:1 with what Paper designed. I even took it one step further and tested pulling a Storybook component library into both tools. Figma scattered variants across separate pages with no structure. Paper organized every size, color, and state in one file, exactly how you'd expect a component library to look. Shoutout to our amazing designer @ftosses for inspiring me to try paper :) I tested a full comparison video this week :)
