◆ Salesforce

Define LWC element with ID attribute

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 new component for the sales dashboard that shows the top 5 open opportunities. Give it…+
Create a new component for the sales dashboard that shows the top 5 open opportunities. Give it a unique identifier so we can reference it easily.
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 acceptBuild a new custom component for the account page that displays related contacts. Make sure…+
Build a new custom component for the account page that displays related contacts. Make sure each contact card has a unique ID so we can click on it and open their full record directly.
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'm trying to add a custom button to the opportunity page, but it's not showing up in the right…+
I'm trying to add a new custom element to a page, and it's not behaving as expected.
I'm trying to add a custom button to the opportunity page, but it's not showing up in the right place, and I can't seem to target it with other components. The sales team needs this by end of day Friday. I'm afraid it's conflicting with something else. Did I give it the wrong kind of ID, or is there a standard way these elements should be named to avoid conflicts? What's the best next step to get this working correctly?
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 frequently running into problems where custom components on a page don't interact well, or…+
I keep having issues with custom components not interacting properly on pages.
I'm frequently running into problems where custom components on a page don't interact well, or I can't reliably update specific parts of them. This wastes time debugging and makes the user experience clunky. What habit should I change regarding how I define and assign IDs to these elements to ensure they are robust and easily manageable?
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.