◆ Figma

Export design assets

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 taskI need the final PNG and SVG assets for the mobile app screens and icon set ready for…+
I need the final PNG and SVG assets for the mobile app screens and icon set ready for implementation. Export every screen at 1x and 2x, name files exactly like the component IDs the engineering team uses, and put them in the shared build folder by Friday 5pm. Before exporting, check that every symbol is detached where developers expect vector assets and that text layers are outlined for the icons.
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 export, make it easy for engineers to pick up the assets: surface the pixel sizes and…+
Before I export, make it easy for engineers to pick up the assets: surface the pixel sizes and intended scale factor next to each artboard, make exported file names follow our repo convention, and flag any layers that are still using effects or masks that would break in code.
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 just tried to export the icons for Android and several came out flattened instead of SVG.…+
I clicked export and some icons came out rasterized.
I just tried to export the icons for Android and several came out flattened instead of SVG. Developers on the Android team will break if they get raster icons for different densities. I do not know whether those layers were converted to bitmaps or if an effect forced rasterization. Do you think the source components have non-vector effects or were they accidentally flattened when grouped? What is the fastest check and fix so I can re-export by the end of the day?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release I lose time re-exporting assets because file names, export settings, or vector…+
I keep re-exporting after engineers report missing or wrongly named assets.
Every release I lose time re-exporting assets because file names, export settings, or vector treatments are wrong. I want a habit that prevents these last-minute fixes and avoids back-and-forth with Marco in Android. Which naming, layer-check, and pre-export review routine should I adopt so exports are right first time and take under 30 minutes?
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.