◆ Salesforce

Create dynamic LWC 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
See the prompt↓All Salesforce tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskOn the 'Opportunity Detail' page, if the 'Stage' is 'Negotiation', display a component that…+
On the 'Opportunity Detail' page, if the 'Stage' is 'Negotiation', display a component that shows the 'Legal Review Status'. If the 'Stage' is 'Closed Won', show a component for 'Onboarding Checklist'.
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 acceptFor our new product launch, I need a flexible way to display different support forms on the…+
For our new product launch, I need a flexible way to display different support forms on the 'Case Detail' page based on the 'Product Family' field. If it's 'Product A', show Form A; if 'Product B', show Form B. It needs to be easy to add new forms as products are released.
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 just asked for a new 'Competitor Analysis' component to appear on opportunity…+
The sales team needs a new component to appear on opportunities only for specific product types, but I don't want to hardcode it.
The sales team just asked for a new 'Competitor Analysis' component to appear on opportunity records, but only when the 'Product Type' is 'Enterprise Software'. I can add it, but I'm worried that if they introduce new product types next quarter, I'll have to modify the code again. What's the best approach to make this component appear dynamically based on the product type without hardcoding, so it's future-proof?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI find myself constantly writing conditional rendering logic directly into components or page…+
I frequently hardcode conditional logic for displaying components, leading to maintenance headaches with new business rules.
I find myself constantly writing conditional rendering logic directly into components or page layouts to show or hide elements based on field values. This becomes a nightmare to maintain when business rules change or new products are introduced, requiring me to redeploy. What habit should I change in how I approach displaying components to make them dynamically adaptable to evolving business requirements without constant code changes?
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.