◆ Salesforce

Debug custom LWC in Flow

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 taskI need to fix the custom LWC component 'ProductSelector' within the 'NewOrderFlow' flow. The…+
I need to fix the custom LWC component 'ProductSelector' within the 'NewOrderFlow' flow. The component isn't displaying correctly on the second screen, 'ConfigureProducts'. Check the component’s controller for any errors preventing the product list from loading.
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 acceptThis custom LWC 'AccountDetailsCard' in the 'ClientOnboardingFlow' is causing a blank screen…+
This custom LWC 'AccountDetailsCard' in the 'ClientOnboardingFlow' is causing a blank screen for some users. Before I push it to production, help me find why it’s failing intermittently, especially for accounts with many contacts, and suggest a more robust way to handle data loading.
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 'DiscountCalculator' LWC in our sales quote flow is miscalculating for deals over $500,000,…+
The custom LWC 'DiscountCalculator' in the sales quote flow is showing incorrect totals for large deals, and the sales team is losing trust.
The 'DiscountCalculator' LWC in our sales quote flow is miscalculating for deals over $500,000, and the sales team is now manually double-checking everything. I just got an urgent call from Brenda in sales who had to apologize to a buyer. I can't tell if it's a data type issue, a governor limit, or something with the reactive properties. What's the most likely cause, and what's the fastest way to pinpoint it before Friday's executive review?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI keep building custom LWCs that work fine in testing but then fail or slow down when real data…+
My custom LWCs frequently hit governor limits or have performance issues when dealing with larger datasets.
I keep building custom LWCs that work fine in testing but then fail or slow down when real data volumes hit. It's costing me credibility with the sales team and delaying deployments. What habit should I change in my development process to consistently build more performant and scalable Lightning Web Components?
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.