◆ Figma

Create new design file

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 a new design file for the mobile product we’ll show investors on Thursday. Create a…+
I need a new design file for the mobile product we’ll show investors on Thursday. Create a fresh file named Mobile Investor Demo — include an assets page, a components page, and a notes page. Populate the assets page with the brand colors I pasted (DeepBlue #0A3F66, Coral #FF6B5B, Slate #F4F6F8), and add the logo I uploaded. On the components page create a button component with primary, secondary, and disabled states, and a text style set for H1, H2, body and caption. Leave an editable notes page for version and author information.
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 start extending this file for the team, make the new file easy to pick up: copy the…+
Before I start extending this file for the team, make the new file easy to pick up: copy the brand colors to an assets swatch, create a component for primary CTA with the filled and outline states, add a reusable text style named ‘Investor H1’ set to 28/34, and add a short usage note at the top telling engineers which font weights to load. Flag any missing assets or inconsistent color values that would slow handoff.
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 duplicated last quarter’s app file into Mobile Investor Demo and kept the old messy layers.…+
I just duplicated an old project file into this new file
I duplicated last quarter’s app file into Mobile Investor Demo and kept the old messy layers. I’m worried I copied deprecated components and wrong color tokens and the engineers will grab the wrong assets. I can’t tell which components are live or which text styles map to tokens. What’s the most likely places the team will trip, and what quick sweep should I do now to make the file safe to hand off for Friday’s build?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery time I spin up a demo or feature file I copy from an existing file and end up with…+
I keep creating new files from older projects and accumulating hidden tech debt
Every time I spin up a demo or feature file I copy from an existing file and end up with duplicate components, inconsistent tokens, and version confusion. It costs me hours later cleaning and costs engineers time. What three habits should I change when creating a new file so future handoffs are clean and predictable? Give concrete steps I can follow the next four times I make a file.
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.