◆ Salesforce

Use JavaScript frameworks in 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 taskUpdate the 'Opportunity Stage' to 'Closed Won' for the 'Acme Corp Q4 Renewal' opportunity.…+
Update the 'Opportunity Stage' to 'Closed Won' for the 'Acme Corp Q4 Renewal' opportunity. Then, create a new 'Contract' record linked to it, setting the 'Start Date' to January 1, 2024, and the 'End Date' to December 31, 2024.
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 component for the sales team to quickly log client interactions. Before I…+
I'm building a new component for the sales team to quickly log client interactions. Before I finalize it, make sure the JavaScript framework I'm using handles data updates efficiently, especially for frequently changing fields like 'Next Steps' and 'Meeting Outcome', so the reps don't see old data or experience lag.
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 pushing a new component for the 'Client 360' view, showing open tasks. It keeps failing on…+
I'm trying to display a list of open tasks for a specific account, but the component keeps throwing errors about an unsupported JavaScript feature.
I'm pushing a new component for the 'Client 360' view, showing open tasks. It keeps failing on deployment, saying 'unsupported JavaScript feature'. I used a common framework method for data binding, but it seems to be breaking. The sales VP needs this live by Friday for the board meeting. I can't tell if it's my code or a platform limitation. What's the likely diagnosis here, and what's the fastest way to get this working without rewriting everything?
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 running into issues when I try to use modern JavaScript features or frameworks…+
I keep getting stuck when integrating new front-end features, struggling with compatibility.
I'm constantly running into issues when I try to use modern JavaScript features or frameworks within the platform's components. It feels like I'm always fighting against the system, leading to delays and frustration. What habit should I change to better anticipate and navigate these compatibility challenges, so I can build more robust and future-proof solutions?
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.