◆ Figma

Duplicate and iterate screens

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 taskDuplicate the onboarding screens from the current file into the working branch, create a…+
Duplicate the onboarding screens from the current file into the working branch, create a variation for the personalized headline and the price toggle, and rename each new frame with the pattern Onboard — Variant — Step number. Link the new frames into the prototype flow so QA can test both variants, and leave a pinned comment for Max in engineering to confirm the API placeholder.
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 spin another iteration, make this duplication frictionless: copy the hero, form, and…+
Before I spin another iteration, make this duplication frictionless: copy the hero, form, and confirmation frames into a single page called Experiments, keep components linked to the design system, and mark variants with a visible badge. Highlight where spacing or token overrides break component reuse so I can avoid duplicate fixes later.
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 copied three onboarding variants for a pricing test and the new frames ended up across three…+
I duplicated screens for an A/B test and now variants are scattered across pages.
I copied three onboarding variants for a pricing test and the new frames ended up across three different pages; the navigation prototype points to old frames. I don't know which links are safe to update without breaking the live demo. What's the safest quick approach to consolidate the variants and restore the prototype links before Wednesday's test?
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 duplicate screens for experiments and later spend days hunting versions,…+
We repeatedly waste time reconciling scattered screen copies.
Every sprint we duplicate screens for experiments and later spend days hunting versions, relinking prototypes, and reconciling spacing. Are we failing at naming, page structure, or variant discipline, and what single routine would prevent this from eating a full day each sprint?
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.