◆ Salesforce

Test LWC standard modal components

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 taskI'm working on the new client onboarding flow. Put the standard modal component for 'Confirm…+
I'm working on the new client onboarding flow. Put the standard modal component for 'Confirm Shipping Address' on the page, so it pops up when the user clicks 'Submit Order'.
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 this new onboarding flow live, I need to make sure the 'Confirm Shipping Address'…+
Before I push this new onboarding flow live, I need to make sure the 'Confirm Shipping Address' modal is clear and doesn't confuse users. Check that the buttons are intuitive, the text is concise, and it works well on a mobile phone.
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 implemented the 'Confirm Shipping Address' modal in the new onboarding flow. During a…+
I just implemented the 'Confirm Shipping Address' modal, but a user test showed confusion about where to click next.
I just implemented the 'Confirm Shipping Address' modal in the new onboarding flow. During a quick user test, Sarah from marketing couldn't figure out how to proceed after reviewing the address; she just stared at it. I'm worried this will block new customers. What's the likely issue with the modal's interaction, and what's the quickest way to make it obvious for users to confirm or edit?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternUsers often get stuck or confused when interacting with standard modal components across…+
Users frequently get stuck or confused by standard modal components in our flows.
Users often get stuck or confused when interacting with standard modal components across different flows, leading to support tickets and dropped tasks. I find myself constantly tweaking modal text or button placement after launch. What habit can I change in how I design or test these components to make them more intuitive from the start?
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.