◆ Figma

Import assets from other tools

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 taskBring the header logos, hero images, and SVG charts from the legacy design files into the…+
Bring the header logos, hero images, and SVG charts from the legacy design files into the current project and place them into the assets page. Make sure raster images remain at original resolution, SVGs are cleaned of inline styles, and rename files to match our tokens: brand-logo-primary, hero-2026-q3, chart-sales-svg. Confirm export settings so engineering can pull PNGs and optimized SVGs.
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 import everything, make the asset import easy for reviewers: highlight any images that…+
Before I import everything, make the asset import easy for reviewers: highlight any images that will scale poorly, flag vector assets with inline fills or fonts, list files whose names don't match our tokens, and group assets by use case so a developer can pick the right one without opening the design file.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI imported the SVG charts from the old files and now their colors render differently in this…+
Imported SVGs display with wrong colors
I imported the SVG charts from the old files and now their colors render differently in this file. The engineer assumes brand tokens will be used and the PM will think I broke them. I don't know whether the color shift came from embedded styles, color profiles, or mismatched fill tokens. What's the likely cause and the quickest way to normalize these SVGs to our current token set?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time we migrate work from legacy files, the team spends days cleaning SVGs and renaming…+
We repeatedly re-clean assets after migration
Every time we migrate work from legacy files, the team spends days cleaning SVGs and renaming assets instead of moving forward. I'm the person asked to fix it. Which three habits or checks around naming, token mapping, and a one-page import checklist will stop this recurring drain on time?
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.