We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.
Find solutions, get advice, help others.
Zhhs snis sjaiw w isw nwjs w wksj ensjvd whhsbs bsjss. Sbaja a akajs ansvs anajs
I love the MCP project but am having a really hard time getting good results from it, every time I asking Claude Code or Cursor to style my UI component like the provided link it’d not even close, it was 85%-90% wrong, sometimes really wrong. Making it mostly unusable. Lots of experience with LLM coding, I know what I’m asking for it with-in their capability. I also recently tried Figma Make where I imported the exact some component, using the exact same prompt and it completely nailed. Figma Make using Claude Sonnet got all the colors right, the fonts sizes, added the exact stroke and rounded corners, it even added roll-over state and correctly guessed my design intent, really amazing! But when I do the same with Claude Code and Figma MCP but it completely fails, adding styles to the wrong components, getting all the fonts wrong, colors are all over the place, etc. I have some theories as to why but would love some feedback and help Theories 1. Tailwind vs traditional CSS - My first t
Hi, I have a question about a variable/component I created. I’ve set up a condition where, when the toggle or switch is turned on, the dropdown menu becomes enabled, and when the toggle or switch is turned off, the dropdown menu becomes disabled. However, I noticed that when I turn the toggle off, the selected item in the dropdown resets to its default value. Why is this happening? Before [Condition Switch is OFF] After Switch to Active After [Condition Switch is ON]
I use Figma in view only mode for work and for no reason now when I hover over a property variable the actual value of the variable doesn’t show anymore. I’ve only seen one other forum post talk about this from 9 months ago and the figma rep said it was fixed in an update. I restarted my laptop and installed figma desktop, but the problem persists. Does anyone know if there is any fix to this.
I was going to praise how neat the new Annotation feature is, when I realized the content is only visible to Dev Mode accounts. Are you serious? I understand you want to limit creating annotations to certain seat types, but viewing annotations should be a viewer-level feature. Come on Figma, there are better ways to convince your users to pay for a subscription. This is such a crooked move.
I have some buttons that have a hover effect and in the prototype there is slight movement of the content. I checked the position of the content to be the same in both instances (default and hovered) in regards to the margins and in between items I applied a “while hovering” interaction with instant animation This also seems to happen in between separate screens of a prototype for text in a header component that doesn’t have animation applied or any other interaction. Anyone has any idea?
We’re experiencing an issue with the #get_image tool in MCP. While it appears to retrieve the image successfully, the image does not render correctly in the actual implementation. This issue did not occur in the early stages of using MCP. Has there been any known issue or update related to this?
How can I fix the problem where some parts of the image are corrupted when exporting the image to png?
Very low performance speed in Figma Make when the thread reaches large sizes (currently 230+ iterations). All actions in the chat area occur with a significant delay (typing, scrolling, etc.), making it impossible to work. However, the prototype itself works well within FM. Has anyone encountered this? What could be the cause? Could it be related to the power of the laptop?
Olá a todos! 🙌 Estou a criar uma app chamada NutriGlow, voltada para o bem-estar, alimentação e rotina saudável, e preciso de ajuda para criar os ecrãs no Figma com base no design e fluxo que já defini. Já tenho: Um design visual pensado Um ficheiro de Figma com várias páginas feitas O fluxo completo da app (registo → formulário → home → semanas → receitas → estratégias → perfil) Uma estrutura clara e organizada, só preciso de ajuda a montar os ecrãs no Figma com consistência A ideia da app é esta:🔐 O utilizador só pode aceder ao registo depois de pagar 🧾 Depois preenche um formulário com peso, altura, objetivo e fotos atuais 🏡 A seguir entra numa home com acesso a várias secções: Semanas (com 4 semanas de planos e receitas) Lista de compras (criada a partir dos ingredientes das receitas, com caixas de check) Estratégias alimentares A, B, C… Notificações diárias sobre copos de água, exercício, sono, etc. Perfil com evolução semanal do peso Tudo está pensado para ser ligado a Bravo
I have an icon library that I am organizing, and I thought the new grid Auto-layout feature would help organize the icon sizes. Set the grid on the Component Set to use a 2x7 (2 columns, 7 rows) layout. Then, I select all of the variants and drag the top-left selected variant into the top-left cell on the grid. All of the variants nest themselves in the grid cells magically as expected. But what is unexpected is that the property names are blown away and reset to Figma’s default naming convention while the property values stay intact.
APIs, guides, plugins, and more.
Find a virtual event that speaks to you.
Find answers, learn more.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.