◆ Salesforce

Make lightning-button use full width

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 taskMake the 'Submit Order' lightning-button on the 'New Order Entry' form use the full width of…+
Make the 'Submit Order' lightning-button on the 'New Order Entry' form use the full width of its container.
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 get this 'New Order Entry' form to the sales team, make the 'Submit Order' button more…+
Before I get this 'New Order Entry' form to the sales team, make the 'Submit Order' button more prominent. Not just full width, but also ensure it's visually distinct and clearly indicates its primary action, making it easy for them to find and click quickly.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe sales team is frustrated because the 'Submit Order' button on the 'New Order Entry' form is…+
The sales team is complaining that the 'Submit Order' button is hard to find on the new order form.
The sales team is frustrated because the 'Submit Order' button on the 'New Order Entry' form is blending in, and they're missing it. I tried making it full width, but it still doesn't stand out. I'm afraid this is slowing down their order processing. What's the best next step to make this button unmistakably visible and intuitive to click, without cluttering the form?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep implementing UI changes that are technically correct, like making a button full width,…+
I often implement UI changes that are functionally correct but don't fully address user experience needs.
I keep implementing UI changes that are technically correct, like making a button full width, but then users still struggle with usability. This leads to rework and user frustration. What habit should I change to consistently consider the broader user experience and visual hierarchy when making UI adjustments, ensuring elements like critical buttons are not just present but intuitively discoverable and effective?
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 Salesforce'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.