◆ Figma

Create component states

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 taskCreate hover, focused, disabled, and loading states for the form input component used on Sign…+
Create hover, focused, disabled, and loading states for the form input component used on Sign Up and Settings. Add keyboard focus ring and a subtle shake for invalid. Link the states to the existing input component as variants and ensure the default instance on Sign Up uses the focused state when autofill is expected. Deliver by Wednesday end of day and call out any spacing or token conflicts.
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 add states to the input, make approving the change easy for product and accessibility…+
Before I add states to the input, make approving the change easy for product and accessibility reviewers. Show contrast ratios for each state, surface how the focus ring will affect layout on small screens, list potential form validation transitions that could feel jarring, and flag any tokens that will need updating so engineers can implement CSS variables consistently.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentProduct asked for an invalid-state shake on the email input and I created that animation as a…+
Product asked for an invalid shake but I don’t know how it reads with screen readers
Product asked for an invalid-state shake on the email input and I created that animation as a variant, but I don’t know whether the shake will confuse screen reader users or fail automated tests. What’s the likely accessibility risk here, what quick tests should I run, and what’s the least-change alternative that keeps the UX signal without harming a11y?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternWe keep adding visual states in isolated files and only discover accessibility or spacing…+
We repeatedly patch states ad hoc and accessibility fails later
We keep adding visual states in isolated files and only discover accessibility or spacing regressions during QA, which costs two-week rebuilds. Is the root cause inconsistent token usage, missing review gates, or designers working in forks? Recommend one governance change, one tooling check, and one team habit that will prevent these regressions going forward.
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.