◆ Figma

Create and edit gradients

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 taskAdjust the primary CTA background to a horizontal gradient that reads left to right from…+
Adjust the primary CTA background to a horizontal gradient that reads left to right from #0067FF to #00B39F. Update the Button-Primary master so the gradient angle, stops and opacity are identical across desktop, tablet and mobile variants, and verify the gradient renders the same in an exported 2x PNG.
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 push the new button styles to components, make the gradient review-friendly: put a…+
Before I push the new button styles to components, make the gradient review-friendly: put a swatch with the exact hex stops and percents above the component, show the button at the three sizes used in product, and call out any places where contrast with white text drops below AA on smaller buttons so reviewers can approve or request an alternate color pair.
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 updated the CTA from a flat color to a two-stop horizontal gradient and the 2x PNG export…+
The gradient looks banded after export
I updated the CTA from a flat color to a two-stop horizontal gradient and the 2x PNG export looks banded on the staging page. The engineers (Hannah) and QA will see this; I don’t know if the issue is the color space, low bit-depth export, or poor stop placement. What is the likely cause and the quickest change I can make in the file to reduce banding for web delivery?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternAcross several releases our gradients look different in production than in design — banding,…+
We keep redoing gradients because they render inconsistently in builds
Across several releases our gradients look different in production than in design — banding, shifted stops, and inconsistent angles on mobile. I’m the design lead and this creates needless pixel meetings. What habit should our team adopt when creating and approving gradients, and what export or handoff rule will stop these mismatches?
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.