◆ Figma

Use grid and layout guides

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 taskApply the 8-column grid and layout guides to the checkout screens and lock the grid so…+
Apply the 8-column grid and layout guides to the checkout screens and lock the grid so engineers can reference it. Before handing off, check the grid overlay on desktop, tablet, and mobile breakpoints assigned to Dana, and ensure that constraints on the header and primary CTA maintain alignment across sizes. Add a short note in the file explaining the grid logic.
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 enforce the global grid across pages, make reviewing layout easier for engineers:…+
Before I enforce the global grid across pages, make reviewing layout easier for engineers: surface which components will need new constraints, highlight any elements that currently ignore the layout (absolute positioned hero, floating chips), and recommend which breakpoints need manual tweaks. Suggest a single-sentence rationale for the grid rules for the handoff doc.
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 just applied the layout grid and at 768px the hero image overlaps the header. I need the most…+
I turned on the grid and now the hero overlaps at tablet width.
I just applied the layout grid and at 768px the hero image overlaps the header. I need the most likely cause and the fastest fix that won’t force a redesign: what constraint or layer change should I try first, and what short explanation do I give Marcus the front-end lead so he knows whether to patch CSS or wait for a design tweak?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release the team spends hours realigning components after I change grid rules. Where is…+
I waste time fixing alignment after every layout change across breakpoints.
Every release the team spends hours realigning components after I change grid rules. Where is my habit failing — am I not defining constraints, not documenting exceptions, or not reviewing key breakpoints — and what three changes to my workflow will cut cross-breakpoint rework and make handoffs predictable?
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.