◆ Figma

Create and edit vector shapes

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
See the prompt↓All Figma tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskCreate and refine the primary app icon as a vector shape set that scales cleanly. Start from…+
Create and refine the primary app icon as a vector shape set that scales cleanly. Start from the rough sketch on page three, convert it to boolean shapes with clean corner radii, ensure strokes are outlined so scaling doesn’t change weight, create 24px, 48px, and 96px export frames, and save as AppIcon-Vectors for the iOS build by Friday evening.
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 finalize these vectors for engineering and marketing, make them production-ready:…+
Before I finalize these vectors for engineering and marketing, make them production-ready: simplify overlapping paths, remove unnecessary nodes, check corner radius consistency, and flatten compound shapes that might render differently in the build. Point out any shapes that will rasterize poorly at small sizes and recommend an alternate simplified form for 24px.
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 outlined strokes to keep weight consistent but at 24px the icon looks blurry in the…+
I converted strokes to outlines and now the small-size icon blurs
I outlined strokes to keep weight consistent but at 24px the icon looks blurry in the simulator. I’m not sure whether I should simplify details, snap to pixel grid, or keep a stroke at small sizes. What’s the usual cause of this blur, what quick experiments should I run to confirm the fix, and which result should I hand to the iOS engineer to avoid extra rework?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross multiple launches our icons look great at 96px but fail at 16–24px, causing extra…+
I repeatedly over-detail icons and they fail at small sizes
Across multiple launches our icons look great at 96px but fail at 16–24px, causing extra design-engineering iterations. What habit should I adopt when creating icons so they work across scales, and what concrete process (like a mandatory small-size pass or a two-variant rule) will stop us from shipping illegible icons?
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.