Real-world experiments with Figma to code: 2 different approaches and what actually works, where it falls short.

The Miners Blog is dedicated to cryptocurrency mining and blockchain technology, offering insights into mining hardware, software, and profitability analysis. Developers and enthusiasts can stay informed about the latest trends and developments in the crypto mining space, learning about mining strategies, hardware configurations, and industry news. Whether it's Bitcoin, Ethereum, or other cryptocurrencies, the Miners Blog provides resources for those interested in mining technologies.

The Miners

Two developers ran real-world experiments using Figma's MCP with Claude Code to convert Figma designs into code. Key findings: the tool is highly literal and does exactly what you ask — no more. Specificity in prompts is critical; vague requests yield inconsistent results. Visual translation from Figma to code is accurate, but structural best practices (file separation, responsiveness, component organization) must be explicitly requested. Applying changes to an existing codebase works better than greenfield generation because Claude has structural context to follow. A major practical blocker is Figma's MCP quota on the free tier (~6 requests/month), which severely limits experimentation. Design library mapping is also a current weak point.

Figma MCP Builds Exactly What You Ask – Nothing More

My experiment: applying design changes to an existing project

Quaresma’s experiments: starting from scratch