◆ Figma

Create interactions and triggers

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 interaction logic wired for the onboarding checklist so the PM can test flows…+
I need the interaction logic wired for the onboarding checklist so the PM can test flows tomorrow. Make the welcome screen’s Get Started button open the checklist panel, progress ticks update when a task completes, and the Skip link jump to Home. Confirm keyboard and tap triggers work and note any missing microcopy before I hand this to Kiran at 9am Friday.
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 hand this to Kiran, make the interactions obvious to a reviewer: surface which tap or…+
Before I hand this to Kiran, make the interactions obvious to a reviewer: surface which tap or swipe triggers each state, show hover and pressed visuals for CTA buttons, flag where a timing delay will feel slow, and call out any interactions that rely on unimplemented components so the PM isn’t surprised.
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 clicked Complete on the checklist item and the progress bar stayed the same. The…+
I prototyped a task on the checklist but progress didn’t tick.
I just clicked Complete on the checklist item and the progress bar stayed the same. The engineer Sam and PM Kiran are waiting; I’m worried it’s an invisible state binding or that I wired the wrong layer. I can’t tell if the problem is missing trigger assignment or a typo in the component name. What’s the fastest diagnosis and fix so I can hand this off by lunch?
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 I end up redoing basic triggers like tap-to-open panels and back navigation, which…+
I keep rebuilding simple interactions at the end of sprints.
Every sprint I end up redoing basic triggers like tap-to-open panels and back navigation, which eats two days and irritates engineers. Help me pick a habit to change: what small standards, naming convention, and preflight checklist will prevent this recurring waste so I can stop firefighting the week before release?
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.