◆ Figma

Fix Figma performance issues

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCan you help me get the performance back on this Figma file? It's really dragging, especially…+
Can you help me get the performance back on this Figma file? It's really dragging, especially when I try to move components around. I need to present this to the client by Friday, and I can't have it lagging like this.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I share this Figma file with engineering, can you optimize it for performance? I'm…+
Before I share this Figma file with engineering, can you optimize it for performance? I'm worried about load times and general responsiveness, especially for the larger artboards. Let's make sure it's smooth for them to inspect and use.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe client just asked for a significant new section to be added to the design, but this Figma…+
The client just asked for a major design iteration, but the Figma file is already huge and slow.
The client just asked for a significant new section to be added to the design, but this Figma file is already so large it's constantly freezing. I'm afraid if I add more, it will crash, and I'll miss the demo next week. I can't tell them the file is too big. What's the best way to scope this without admitting the technical debt?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep ending up with massive, slow Figma files that make me dread the final stages of a…+
My Figma files always get too big and slow down as projects progress.
I keep ending up with massive, slow Figma files that make me dread the final stages of a project. It always impacts my ability to iterate quickly and meet deadlines. What habit should I change to keep my design files performant from the start, so I'm not scrambling at the end?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Figma's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.