◆ Figma

Use boolean operations

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 taskI need the icon set combined into single vector shapes so handoff to engineering is cleaner.…+
I need the icon set combined into single vector shapes so handoff to engineering is cleaner. Merge the overlapping bell, dot and ring into one path for production, keeping the visual silhouette exactly as on the artboard. Do this for the three notification states on Frame Notifications-Active, Notifications-Idle, Notifications-Muted and check there are no hidden stray points before exporting the 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 send these to engineering, make the boolean results obvious to a reviewer: put the…+
Before I send these to engineering, make the boolean results obvious to a reviewer: put the merged icon on the left and the original layers on the right, label which operation was used (union, subtract, intersect) and flag any compound paths that still contain invisible fills. Call out where that union changed stroke widths or rounded corners so the developer knows to expect visual shifts.
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 merged the bell and ring with Union on the main notification icon and the silhouette is off —…+
I just ran a union and the icon looks slightly thicker than before
I merged the bell and ring with Union on the main notification icon and the silhouette is off — the stroke appears thicker and corners softened. I am showing this to the design engineer, the product manager, and Sam in frontend. I do not know whether this is a boolean artifact, stroke treatment, or an export setting. What is the most likely cause and the simplest fix so the SVG matches the original pixels?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery sprint we fix dozens of small shape differences after boolean merges — accidental extra…+
I keep fixing icons after boolean ops break them in handoff
Every sprint we fix dozens of small shape differences after boolean merges — accidental extra points, altered corner radii, invisible fills that break exports. I am the lead designer and it wastes implementation time. Which habit should I change in my workflow to stop this recurring rework and what one tooling check should I add before handing assets to engineering?
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.