◆ Figma

Create icon set

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 taskWe need a coherent icon set for the product release: 48 icons covering navigation, actions, and…+
We need a coherent icon set for the product release: 48 icons covering navigation, actions, and status. Produce filled and outline styles, 24px grid, consistent stroke weight and corner radii, and export-ready slices for SVG and PDF. Include naming that matches the app taxonomy like Home, Search, Save, Error, and Active and put them in a single icon page for handoff.
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 publish the icon set, make it approval-friendly: surface any icons that deviate in…+
Before I publish the icon set, make it approval-friendly: surface any icons that deviate in stroke, list icons that duplicate metaphors, flag ambiguous symbols, and reorder so the most used app actions appear first. Also add a short usage note about when to use filled versus outline.
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 handed the icon set to engineering and they flagged inconsistent stroke weights and…+
Design criticized for inconsistent stroke weights during handoff
I just handed the icon set to engineering and they flagged inconsistent stroke weights and mismatched optical centers. The product manager expects a single source of truth and the release is two weeks away. I don't know if the problem is in vector boolean operations, exported SVG precision, or my grid alignment. Which issue is likely and what step-by-step fix makes the set ship-ready today?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery project forks the core icons—some teams add icons, others tweak strokes—and we lose…+
Each project ends up with slightly different icons
Every project forks the core icons—some teams add icons, others tweak strokes—and we lose consistency and time reconciling them during QA. I'm the design lead and need a daily habit to stop this drift. What governance, naming conventions, and lightweight checks should I enforce so the icon set stays unified across teams?
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.