◆ Salesforce

Deploy project via SFDX

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 taskDeploy the 'Lead Conversion Automation' project to the production environment this evening, so…+
Deploy the 'Lead Conversion Automation' project to the production environment this evening, so the new sales process improvements are live for Monday morning.
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 acceptBefore we deploy the 'Service Cloud Enhancements' project to production, run a validation-only…+
Before we deploy the 'Service Cloud Enhancements' project to production, run a validation-only deployment to ensure all components are correctly packaged and there are no conflicts with existing metadata, so we avoid any surprises during the actual release.
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 deploy the new 'Customer Feedback Portal' project, which includes custom objects…+
I'm trying to deploy a new feature, but it keeps failing with vague errors, and the sales team is waiting.
I'm trying to deploy the new 'Customer Feedback Portal' project, which includes custom objects and flows, to the UAT sandbox for testing by the end of today. It keeps failing with a 'Missing dependency' error, but the logs aren't clear about what's actually missing. The sales team is waiting to test it. What's the best next move to diagnose this dependency issue quickly and get the project deployed?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently encounter deployment failures when moving projects between environments, usually…+
My deployments often fail due to unexpected dependencies or conflicts, causing delays.
I frequently encounter deployment failures when moving projects between environments, usually due to missing dependencies or conflicts with existing metadata. This often leads to urgent troubleshooting and delays for the business. What habit should I change to better anticipate and manage these deployment challenges, ensuring smoother and more reliable releases for the team?
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.