◆ Figma

Add overlays and modals

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 taskAdd the account-settings modal and link it to the profile avatar so Marco in support can test…+
Add the account-settings modal and link it to the profile avatar so Marco in support can test the password flow Monday. The modal must trap focus, allow closing with ESC and the Close icon, and preserve scroll position underneath. Verify the Save button becomes enabled only when changes are made and call out any copy that needs legal review.
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 this to Marco, make the modal reviewer-friendly: make the close affordances…+
Before I send this to Marco, make the modal reviewer-friendly: make the close affordances visible, show the disabled and enabled Save states, surface where focus will land when opened, and highlight any inputs with validation rules so a QA tester won’t miss flaky behavior.
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 linked the profile avatar to the settings modal, but pressing ESC leaves it open. Support and…+
The modal opens but ESC doesn’t close it.
I linked the profile avatar to the settings modal, but pressing ESC leaves it open. Support and QA will try keyboard shortcuts first; I’m worried it’s a focus trap misconfiguration or that the modal instance isn’t the active layer. I can’t see if the close action is attached to the correct component. What check should I run now to fix this before Marco tests tomorrow?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross releases we ship modals that later fail accessibility and keyboard tests, forcing…+
Modals routinely fail accessibility checks late in the cycle.
Across releases we ship modals that later fail accessibility and keyboard tests, forcing last-minute patches. I need a single habit to stop this. What naming, component rules, and a short accessibility preflight will catch focus, ESC, and ARIA issues before QA discovers them?
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.