◆ Salesforce

Define coding conventions for Salesforce development

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 coding standards document for the new junior developers, adding sections for Apex…+
Update the coding standards document for the new junior developers, adding sections for Apex trigger best practices and secure coding guidelines, making sure it's accessible from our internal wiki by end of day Friday.
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 finalize the new coding conventions, make sure they're practical for our current…+
Before we finalize the new coding conventions, make sure they're practical for our current team's skill level and don't introduce unnecessary overhead. Add examples for common scenarios and a quick reference guide, so developers can adopt them without slowing down.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentOur new lead just pushed a major feature branch, but the code quality is all over the place,…+
Our new lead developer just pushed a significant change without following any of our existing (loose) conventions, and I'm afraid of a ripple effect on our upcoming release.
Our new lead just pushed a major feature branch, but the code quality is all over the place, and it’s not following any of our team’s informal patterns. I’m worried about maintaining it and the impact on our release next month. What’s the best way to address this without making him feel undermined, and what's the immediate next step to prevent this from happening again?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternEvery release cycle, we spend too much time in code reviews arguing over formatting and basic…+
We consistently struggle with code reviews taking too long and finding basic style issues instead of functional bugs.
Every release cycle, we spend too much time in code reviews arguing over formatting and basic structure instead of real logic. This always delays our testing phase. What habit should we change as a team to enforce a consistent code style upfront, so reviews focus on actual functionality?
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.