◆ Figma

Create wireframe layout

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 basic wireframe layout for the onboarding flow—two screens: welcome and…+
I need a basic wireframe layout for the onboarding flow—two screens: welcome and create-account—ready by Wednesday. Create a 360×800 mobile frame for each screen. On the welcome screen place a centered illustration, a headline, a one-line benefit statement, and two buttons: Create account and Log in. On the create-account screen include labeled fields for name, email, password, a show-password toggle, and a Continue button disabled until fields are valid. Keep everything in low-fidelity — gray boxes and placeholder text.
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 these wireframes to the PM and engineers, make them easy to evaluate: surface the…+
Before I hand these wireframes to the PM and engineers, make them easy to evaluate: surface the primary conversion path, label which fields are required, show the disabled state and an error example for the email field, and add a short note listing assumptions about validation and third-party auth. Highlight any places where flow detail is missing that would make engineers block on APIs.
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 sketched the onboarding wireframes and the PM says she needs field validation and edge cases…+
I sketched a wireframe but the PM is asking for validation rules
I sketched the onboarding wireframes and the PM says she needs field validation and edge cases before scoping. I don’t know the business rule for password strength or whether to allow social sign-on. I’m afraid engineers will build a lax flow or we’ll postpone a critical check. What’s the likely minimum validation to ask for now and how should I phrase the questions to the PM so we can move to estimate without stalling design?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross projects we hand over low-fi wireframes that omit validation, error states and empty…+
Wireframes keep missing the small validation and error cases and get reworked late
Across projects we hand over low-fi wireframes that omit validation, error states and empty states. That leads to weeks of rework when engineers implement and QA finds edge cases. What practical habits should I adopt in my wireframe process to catch the common missing items and cut handoff back-and-forth by half? Give three checks to include on every wireframe before review.
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.