◆ Salesforce

Interact with browser clipboard from LWC

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 a button in my `AccountDetail` Lightning Web Component that, when clicked, copies the…+
Create a button in my `AccountDetail` Lightning Web Component that, when clicked, copies the Account's 'Phone' field value to the user's clipboard.
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 acceptI'm building a new `ProductConfigurator` Lightning Web Component where users need to copy…+
I'm building a new `ProductConfigurator` Lightning Web Component where users need to copy complex configuration strings. Make sure the copy functionality is robust – it should give clear visual feedback that the copy was successful or failed, and handle cases where the string might be very long. Think about the user experience for our sales engineers who will use this all day.
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 'Copy Case ID' button in our `CaseViewer` Lightning Web Component is intermittently failing…+
Users are reporting that the 'Copy ID' button in the `CaseViewer` component sometimes doesn't work, especially on older browsers.
The 'Copy Case ID' button in our `CaseViewer` Lightning Web Component is intermittently failing for support agents, particularly those on older browser versions or specific mobile devices. They're getting frustrated because they have to manually type IDs, which slows down their workflow. I'm afraid this is impacting our resolution times, but I can't replicate it consistently. What's the most common pitfall when implementing clipboard interactions across different browsers, and what debugging steps should I take first to pinpoint the issue?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI'm constantly troubleshooting issues with clipboard interactions in my Lightning Web…+
I frequently get reports of clipboard interaction features in LWC not working reliably across all user environments.
I'm constantly troubleshooting issues with clipboard interactions in my Lightning Web Components – they work for me, but not always for users on different browsers or devices. This leads to user frustration and wasted time. What habit should I change when implementing or testing clipboard features to ensure they are consistently reliable for everyone?
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.