◆ Figma

Create color palettes

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 taskCreate a color palette for the new feature release that includes primary, secondary, success,…+
Create a color palette for the new feature release that includes primary, secondary, success, warning, error, and three neutral scales. Start from the brand tokens in Brand Colors v1, ensure accessible contrast for body text and buttons at normal and large sizes, add usage notes for backgrounds versus interactive elements, and publish the palette to Shared Assets by Monday so engineers can implement it in the feature branch.
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 publish the palette, make it approval-ready: surface the contrast ratios for each…+
Before I publish the palette, make it approval-ready: surface the contrast ratios for each token against white and the darkest neutral, point out any colors that fail WCAG AA for body text, show where color is currently used in components that will change, and flag any hues that could make product copy hard to read. Highlight anything that would make a reviewer hesitate to accept the palette.
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 swapped the success token to a greener shade but the PM insists the old teal aligns better…+
Designers picked a greener success color but PM wants the old teal for continuity
I swapped the success token to a greener shade but the PM insists the old teal aligns better with existing analytics dashboards. I’m not sure whether to keep the new color for visual distinctiveness or revert for continuity. What are the trade-offs in terms of user recognition and engineering cost, and what’s the least disruptive path given we are one sprint from release?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery cycle we end up arguing over minor hue changes that then ripple into engineering work and…+
We repeatedly debate small color shifts late in release cycles
Every cycle we end up arguing over minor hue changes that then ripple into engineering work and QA. It wastes time and erodes trust. What practice should I adopt to minimize late-stage color decisions? Recommend a rule or cadence for color freezes, decision owners, and a small acceptance checklist so palette changes don't derail releases.
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.