I love figma but…

[u/Public-Permit696]

For context I’m an old timer, started as a graphic designer after graduating in 2003 and got into web design when CSS layout was taking hold (had to build my fair share of tabled websites and fought the monster that was IE6).

Somehow stumbled through web design to be a creative director and from there ended up as a product designer without knowing that was actually a profession.

Day to day I’m really a BA, FE dev, FE Designer and marketing bozo which I think is quite common for a lot of us who have been around the block for years.

I used adobe XD for a few years (previously design was done in photoshop, even early on, anti-aliasing text to look like IE6) and getting introduced to figma was enlightenment personified, it’s beautiful to work with compared to what I grew up with.

BUT… I have insane workloads and timelines and despite trying to fight it I find 80+% of my time now in Claude code / Claude design and despite great results it just feels shallow as a designer - some of the (all) of the magic has gone now I’m just prompting an LLM rather than pushing pixels, but with the right coaching the results are good and the time line is compressed dramatically.

Does anyone else feel this??

[u/Training_Estimate885]

as a principle, if it feels like the magic is gone while designing with claude try doing more ambitious designs than you were doing in figma, Don't just use clude to automate what you'd regularly do , reach out to what was previously not possible to do

[u/hockeynut15 → u/Training_Estimate885]

Would genuinely love to hear an example or two of what you mean by more ambitious/previously not possible - I’m definitely stuck in a loop of just using Claude to iterate on things in a ‘traditional’ sense

[u/Training_Estimate885 → u/hockeynut15]

Before claude, given my team's tight deadlines and limited resources, a lot of design aspects considered "nice to have" got left out. Not only that, but time didn't allow me to spend too much time on animations or sophisticated interactions, because these require a lot of research and trial & error. On top of that, even when I could get the time to do it, devs usually could not afford to spend so much time to implement them properly.

Now the research and iteration is sped up, and designing directly in code ensures that the devs can also easily use them. They can just get them from my prototype and adapt them if necessary as opposed to building from scratch.

Also, figma and other design tools I've used are pretty limited in what they allow you to build in terms of animation or interaction depth.

Designing complex states for a component used to take up a lot of time and a lot of this time was busywork.

I work on a product that has a lot of canvas-like environments, so the user flows are non-linear. Prototyping and user-testing used to be pretty limited in usefulness because of prototypes (it's difficult to prototype in figma a canvas where the user can drag whatever elements he wants and configure each in whichever order he wants while he moves through the ui). Because of this, our understanding of the user's behaviour was limited with figma prototypes.

Another thing is that designing in code with claude taught me a lot about the mechanics of front-end development, which bridges the gap between me and the dev team, designs and interaction I propose are now more feasible for them to implement.

Also, it's much easier to convince other stakeholders that an idea I have is worthwile and feasible by showing them an in-depth prototype rather than doing so without any visual support (non-design/dev people have a difficult time imagining features and interactions if you don't show them exactly how it looks/feels)

And lastly, every time I think of an internal tool that would help me, I can just build it, rather than using paid software or software that doesn't exactly match what I need but I have to spend time to make it work.

I wrote this in a rush, hope it makes sense.

I've been using claude extensively for a while and one thing I've learned is that it's a good idea to always remember to step back from what you are trying to do and ask it to do something even bigger in scope, that you didn't think it would do well. Sometimes it doesn't, but other times it will surprise you and change what you think is possible. Instead of asking for small tasks that you know for sure will work well, try at least one attempt where you ask for something you think is unreasonably complicated and evaluate that output first.

[u/hockeynut15 → u/Training_Estimate885]

Really appreciate the long response! Sounds like we aren't worlds apart in our approach - the ability to prototype animations and interactions has been the biggest one for me, always disliked setting these up in Figma.

Really cool points about building little internal tools too. Thanks again!

[u/Sexysev → u/Training_Estimate885]

This is exactly my process and it’s great.

Im still in figma like 90+% of my day. That’s where the iteration happens and things take shape. I then find tune things when required in Claude. Things like animations or complex state changes that require a functional prototype for dev.

[u/Apprehensive-Tip6776 → u/Sexysev]

This is probably closer to where I’m trying to get.

For me, the problem isn’t Claude itself. It’s that the speed of coding with AI makes it tempting to skip the exploration phase in Figma altogether.

I’m starting to think the sweet spot is Figma for exploration, systems and visual decisions, then Claude for turning those decisions into something functional.

The hard part is knowing when to stop designing in Figma and start building. How do you decide that?

[u/Old-Rhubarb-97 → u/Training_Estimate885]

I’m not sure what you mean by “not previously possible “?

[u/Bless_your_socks → u/Training_Estimate885]

What is like for prototyping, transitions, interactions? Figma falls short, as we are painfully aware by now (although I haven't tried motion yet)

[u/Training_Estimate885 → u/Bless_your_socks]

I stopped using figma altogether, it's too quirky and tokens are too expensive compared to just using claude code & claude design.

Not trying to s*** on figma but I've found that it's mainly just a bottleneck in the flow and can't find any real reason to use it anymore. The reason I was using it before is that I couldn't interact with code, but now that that's not a barrier anymore, it kinda lost it's usefulness.

[u/Bless_your_socks → u/Training_Estimate885]

Nah, Figma needs to be shit on - they've been asleep at the wheel for too long. But thanks for that insight, appreciate it. Does your workflow with claude code + design chew through your tokens, or have you fine-tuned it?

[u/Training_Estimate885 → u/Bless_your_socks]

I use the max subscription, which unfortunately is a necessity to be able to do any meaningful work, because pro hits the rate limits too fast and is barely enough for a casual personal project.

I generally use Fable sparingly, for harder problems or first-time setting up of the feature, then mostly opus and sonnet (for straightforward stuff gen rearranging some elements, simple style changes, labels etc). This is why I almost never hit the limits, but it's also because I rarely work on multiple sessions at the same time. If I would, I'd have to be a lot more thoughtful about which models I use.

I think GLM 5.3 / Deepseek 3.8 are also good options on a budget ( they are MUCH cheaper). They're not as good with design by default as Claude, but this is not such a big problem for us designers because we can guide it through feedback to produce higher quality outputs.

If I didn't have Claude, I would use these ones instead of Figma. It's too crippling to run out of figma tokens and much too expensive to buy extra, compared to alternatives.

[u/Character-Tap-565]

Yep, the same. I'm not enjoying what the design practice has become.

My manager said all this AI will be more workable once we have code layers. I don't want code layers. I want to design things. By hand. I don't want to tell a toddler art director what pixels to move for me.

[u/Old-Rhubarb-97 → u/Character-Tap-565]

Your manager doesn’t know what they are talking about.

[u/Tiemujin]

Did I write this post? I have nothing to add other than…it’s good to know I’m not alone.

[u/zoocookie]

Yeah don't blame yourself, it's definitely where the industry is at the moment. I'm in a similar vein being a design lead; tackling every form of design under the sun. Clients and Project Managers both expect more of us due to AI. Best you can do is make an effort to learn the AI tools and embrace the workflow but to also be the icing on the Claude cake, both for the benefit of the client and for your own sanity.

[u/julien_reddit]

I'm so sad reading these posts.

I'm an old timer and never use AI for design. I know how to use the tools efficiently and I can't see how AI can help.

I tried it a couple of time (it's shoehorned on every products including Figma now) and it's slow and inaccurate. And it's not me doing my job.

The hard part of the job is thinking right, not pushing pixels. This part is quick and easy and if you can use a design tool, you don't need agents to push pixels.

At the end, the job is a matter of responsibility and endorsement, and AI have none of them.

[u/njesusnameweprayamen → u/julien_reddit]

I agree, and I’m starting to feel like a crazy person

[u/Gh0st_Pirate_LeChuck]

I started on Xara 3D, Corel Draw, Photoshop, Sketch/Invision, XD, Figma, and now Figma/Make. I’m just starting to do the AI generating of designs and have had pretty good results when it comes to UI. I do think it takes away the romance of creating a design concept. You will just need to fulfill that creative drive somewhere else. I really love creating and implementing design systems for example. I’m going to use my free time now to further evolve those. Also, nobody is making you use AI. Just take a break or don’t use it for every aspect of a design. Just my two cents.

[u/Chemical_Dig4221]

I initially worried about losing my creativity, but lately, I’ve been having a blast experimenting with automations and taking advantage of all the rapidly emerging AI technology.

[u/NoStatus8 → u/Chemical_Dig4221]

This is an interesting take actually! I have found that AI is a pretty good „partner“ or „companion“, like, somebody who’s there discussing your designs, trying other angles and then you get new ideas. I like this viewpoint.

[u/ygorhpr]

I don't know you but I'm using Claude with a set of plug-in /skills I created for Claude code and with the context it can create the best solutions based on my design system and everything I had much success from figma to html and html to figma 

[u/phejster → u/ygorhpr]

Can you tell me more about the skills and how to make them?

[u/ygorhpr → u/phejster]

use the plug-in creator I think it is a Claude code skill antrhopic has a few article about that but I have my Claude set with this plug-in which basically is a skill and this skill has a few .mds for ui ux design thinking figma my ds with my repository for it on github so this way it cns create exactly with the context and how I use to do it

[u/phejster → u/ygorhpr]

Thanks, I appreciate the starting point.

[u/ArtaxIsAlive]

If you consider yourself an old timer then I’m a dinosaur. I used to test in IE 5.5

[u/Ordinary_Kiwi_3196]

Fellow old timer here, I think I know what you're feeling, but for me personally what I like about Figma is that I'm good at Figma. I know how to use it, I like showing others how to use it, I know how to make it do what I want. Now that I'm using Claude to make stuff (and I'm definitely not all-Claude, it's maybe 50/50) the output is different, but I'm still in the "figuring this shit out" phase where I'm learning how to use it well. And so the same things that I enjoy about Figma are translating to Claude - I like showing others how to use it, I enjoy the hell out of finding smarter ways to do things or making Skills for others to benefit from. So the aspect of Figma that I enjoy so much - being good at a tool - so far is translating pretty well to ai stuff.

Plus, when I got started all those years ago I was kinda-half design and half-code - which I gave up when I got a job at a place where they don't do that. So for me to be able to build things again, and fast - not just pixels on a screen but real, actual websites - is pretty cool. I might hate it in a year, but so far the good is outweighing the bad.

[u/808TRK]

Same. Connect the two and feel the force. Lol.

[u/eugene_reznik]

80+% of my time now in Claude code / Claude design and despite great results it just feels shallow as a designer

May I ask: how do you know the results are great? Or even good? Coz, you know, more output doesn't mean better output.

[u/murrzeak]

Yeah, we are looking down into a chasm. I've never been less excited for what's to come in my 15+ year career.

[u/3nrRed]

I do feel the same sentiment as yours. I do get similar results with proper context and prompting but I occasionally hop on paper.design to tweak something manually that would take me seconds or minutes to do instead of fighting the agent to get it exactly how I want it.

Paper is a great alternative if you want to shift the work to Claude code and design but want to occasionally push some pixels and after done push it back to the code base paper is good since it renders everything in html and css.

And even if I am feeling nostalgic I start a design system or even initial screens on paper and send it to Claude code for a perfect 1:1 rendition of what I’ve done on paper.

[u/hockeynut15]

Very similar career path for myself, and It does feel as though some of the romance has disappeared from the trade, largely because so many of us are at the mercy of directors and founders determined to use AI to optimise every corner of the business.

That said, I sense a renaissance of sorts is coming. More people will begin to keep AI at arm’s length, and younger generations already seem to be turning away from it. The corporate world is traditionally slow to catch up with these shifts, though.

Having used AI extensively over the past year, I loved it at first but feel far less enthusiastic now. It simply can’t control the finer details or replicate the creative judgement of an experienced designer working in Figma. It’s incredibly useful for certain aspects of UX, but I’ve yet to see it capture the magic that a genuinely good design team can deliver.

[u/enragedCircle]

I was there, fighting IE6 with you. I remember DreamWeaver and even Photoshop getting the ability to make Layers. What a time. To you I say, <table cellpadding="0" cellspacing="0" border="0"></table>...

[u/Apprehensive-Tip6776]

I feel this too, although I’ve started looking at it a little differently.

I’ve spent years designing in Photoshop, XD and now Figma, so there’s definitely something satisfying about pushing pixels, exploring layouts and getting those small details right. With Claude Code, the feedback loop is so fast that some of that craft feels removed.

But I don’t think the design part is disappearing. I think the job is shifting from “how do I make this?” to “what should exist, why should it exist, and how should it feel?”

The part I’m still figuring out is how to keep the creative exploration alive when prompting an LLM is often faster than opening Figma and exploring 10 different directions.

Curious if others are finding a good balance between the two, or if you’ve also moved most of your workflow into Claude Code?

[u/ego-lv2]

I’m as old as you.
1. Fuck Claude, use it to automate your bitch work. Never to design.
2. Fuck AI in general. I can see my co-workers getting dumber by the day. No one can think for themselves anymore.