◆ Figma

Design responsive components

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 responsive button and card components that behave predictably across phone, tablet, and…+
I need responsive button and card components that behave predictably across phone, tablet, and desktop breakpoints for our checkout flow. Build the variants so the label truncates with an ellipsis, tap targets are at least 44px, spacing compresses at tablet, and the primary button expands to full width on mobile. Before handing these to engineering, check states, token usage, and that auto-layout keeps paddings consistent.
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 to engineering, make it obvious what will break on resize. Surface the min…+
Before I hand these to engineering, make it obvious what will break on resize. Surface the min and max widths, show how text wraps, call out any fixed pixel values, and add a quick demo frame that cycles phone/tablet/desktop so a PM or engineer can approve without guessing.
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 moved the desktop card variant into the phone frame to test responsiveness and now icons and…+
I just swapped a desktop card into the mobile frame and everything overlapped
I moved the desktop card variant into the phone frame to test responsiveness and now icons and text overlap. The engineers expect components that resize without manual overrides and the PM will blame 'inconsistent tokens'. I don't know which constraints I broke or whether the issue is auto-layout, fixed widths, or a badly nested group. What's the most likely cause and the fastest fix to make this a reliable mobile variant?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross multiple releases we recreate responsive rules for cards and buttons and waste time…+
We keep rebuilding the same responsive constraints from scratch
Across multiple releases we recreate responsive rules for cards and buttons and waste time fixing spacing on each new component. I own the component library and want a habit that prevents this recurring cleanup. Where should I standardize tokens, naming, and utility frames so designers stop rebuilding constraints and engineers receive predictable components?
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.