◆ Figma

Design app 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
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 polished app screens for the core user flow by next Tuesday for the beta build. Design…+
I need polished app screens for the core user flow by next Tuesday for the beta build. Design five mobile screens: Home feed, Item detail, Create post, Notifications, and Profile. Use the Product Design System tokens for color and text, include real copy for headlines and at least one microcopy example (empty state on Notifications), and create interaction states for primary buttons and a modal confirmation for deleting a post. Prepare these screens in a single file where layers are tidy and components are used rather than flattened frames.
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 final screens to engineering, make them easy to implement: ensure all components…+
Before I hand final screens to engineering, make them easy to implement: ensure all components are instances from the system, expose layout constraints for responsive behavior, annotate padding and type sizes, include image assets in the assets page, and add a short spec sheet listing API endpoints needed for feed, create, and notifications. Flag any screens that use custom behavior not covered by the system.
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 delivered five final screens and engineers report missing image sizes and unclear spacing…+
Engineers say assets don’t match the spec in the mock
I delivered five final screens and engineers report missing image sizes and unclear spacing rules; they can’t map components to endpoints. I’m worried the release will slip if I don’t fix it now. Which two fixes will most reduce their blockers this afternoon, and how should I communicate the changes so they can continue work while I update the files?
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 adding specs, annotating screens, and answering the same implementation…+
Each release I redo specs and annotate screens ad hoc and engineers get conflicting notes
Every sprint I end up adding specs, annotating screens, and answering the same implementation questions one-off. That slows releases and frustrates engineers. What three small practices could I make routine so handoffs are consistent, reduce follow-up questions, and cut the number of clarification messages the engineering lead sends me each sprint? Be concrete about what to include in the file and what to say in the handoff message.
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.